Talk:ARIA: Accessible Rich Internet Applications/Relationship to HTML FAQ
From MDC
[edit] GJR Review 17 september 2007
minor editorial and orthographic changes logged in page's history; the following is a proposed substantial change which i have not effected to the document until it is reviewed by Aaronlev
PURPOSE:
- balance the yin and yang of the first paragraph under the heading: "What is ARIA and how does it allow for accessible JavaScript widgets?"
CURRENT:
- ARIA seeks to make accessibility possible for such JavaScript widgets. After all, accessibility should not hold web authors back from innovating, let alone adding some of the basic widgets that are well-known yet conspicuously missing from HTML 4 today. It's not that JavaScript is bad for accessibility, as some have said, but that there is no mechanism to describe what the script is visually portraying to a user.
SUGGESTED:
- ARIA seeks to make accessibility possible for such JavaScript widgets. After all, accessibility should not hold web authors back from innovating, let alone adding some of the basic widgets that are well-known, yet conspicuously missing, from HTML 4 today. Likewise, accessibility need not lag behind such innovations. The problem is not that JavaScript is bad for accessibility, as some have claimed, but that there is no native mechanism to describe what the script is visually portraying to a user.
RATIONALE:
- gives balance to point, hence makes your argument stronger; not only developers being held back, but PWDs being denied innovation
- adding the word "natively" to the last sentence is the key to answering the question, why is ARIA needed?