On Tue, Jul 15, 2008 at 12:10 AM, Cynthia Shelly <[EMAIL PROTECTED]> wrote: > Interesting... > My experience has been that HTML 4.01 can be made accessible if it is > carefully coded. WCAG 2.0 has many >techniques for this, including for > scripted and styled content. While it is true than many (possibly most) > DHTML >applications have accessibility issues, I do not believe that this is > the fault of the standard so much as the >authors. Do you have examples of > things that cannot be made accessible in HTML 4.01?
I agree in principle (though not with WCAG 2.0, but I don't want to start a thread about WCAG 2.0 and accessibility). I guess rather than writing out a list, I can simply cite the ARIA spec [1] as it basically lists some of things that are missing for accessibility in HTML4.01. Fortunately, ARIA has found a home in HTML5 but, from a standardization perspective, that's years away from completion. Widgets, we assume/hope, we package HTML5 applications in the future but we are standardizing, for better or for worsts, on HTML4.01. [1] http://www.w3.org/TR/wai-aria/ -- Marcos Caceres http://datadriven.com.au
