Web Accessibility Issues in the Dojo Toolkit

Excerpt from the Dojo Book:

Now that user interface components are being created via scripted HTML elements such as div and span

Why should they be relying on such poor elements such as div and span is what I’d like to know.

Most of the time we happen to be able to achieve a reasonable level of accessibility through sensible use of a elements. I’m not saying it solves every problem, splits the sea and saves the chosen people, mind you, but (repeat) most of the time, and until a time when ARIA generalises, some anchors provide er... anchors (duh!) into the interface so that AT users can manage to use it.

Many RIA interfaces I’ve seen use divs and span and never a single a or button element. That’s poor.

By the way I’m not throwing the stone at Dojo in particular, especially considering the sheer volume of ARIA-oriented code they’ve injected in version 0.9.


Who are you?
Your post

This form accepts SPIP shortcuts [->url] {{bold}} {italic} <quote> <code> and the HTML code <q> <del> <ins>. To create paragraphs, simply leave blank lines.

Hypertext link

(If your message refers to an article published on the web or to a page providing further information, please enter the title of the page and its URL below).