Category Archives: Front-end code
WYSIWYG editor spec – images
Adding images in an easy and accessible way is a vital part of a modern WYSIWYG editor, and one of the things the almost all of the implementations I've come across get wrong. There are several levels of implementation, from adding images from other locations, to creating and choosing from a library of images and other assets. Internet Apps Roadmap – Questions
The Roadmap for Accessible Rich Internet Applications (ARIA)
outlines the technologies to map controls, AJAX live regions, and events to accessibility APIs, including custom controls used for Rich Internet Applications.This post just draws attention to things I (and Iperhaps other people) could do with some further explanation on.
Image replacement and Voiceover
There was a question on the Voiceover list recently about links just being read out as ‘link’ on a particular site: freeverse. It turned out to be due to an image replacement technique. WYSIWYG editors spec – adding structural code
With a WYSIWYG interface, there has to be an area that appears as it will when published, which means to change bits within it, you need one or more toolbars. This is an exploration of what those toolbars should do. Identifying text-only nodes with CSS
Floating ideas onto the CSS working group can be a frustrating experience, possibly almost as frustrating as seeing the same questions come up every few months! I take a look at why it would be useful to be able to identify text nodes. WYSIWYG editors spec – Importing CSS
The second building block of a modern WYSIWYG editor is how the styles are defined and added. Styles should be applied by class to standard HTML, but what kind of import methods would be best, and how would they surface in the interface? WYSIWYG editor spec – allowed HTML
Starting from the building blocks, what should an editor allow? Most of the browser based editors allow people to edit the source HTML. To make sure the code stays valid, the editor will have to filter what gets saved, so what HTML should it allow? WYSIWYG editor spec – Overview
This is the overview that outlines the accessibility guidelines that affect a "What You See Is What You Get" editor (WYSIWYG) editor, and do a top-line evaluation of an editor so that you know what to look for. Setting the scene for a set of posts specifying accessible WYSIWYG editors. Accessible WYSIWYG editors part 1 – The problem
There is an elephant in the corner type of problem in the accessibilty world, that of WYSIWYG editors. In the first of a three part series, I outline this problem. The later posts will define what a solution would be, and see if it exists yet. Good use of “Web 2.0” technologies
Things on the web move so fast these days that there is a backlash against what people perceive as “Web 2.0” sites before most of the internet population even know what they are. (Even taking the narrow view of AJAX and tagging).
So it’s good to see a use that …