Ticket #9325 (closed PLIP: invalid)
Add ARIA accessibility support for Plone
Reported by: | cjohansen | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 4.0 |
Component: | Unknown | Version: | |
Keywords: | accessibility | Cc: | plip-advisories@… |
Description
ARIA (Accessible Rich Internet Applications) is a W3C specification is designed to make dynamic Web content, Web applications and custom user interface controls accessible to people with disabilities ( http://www.w3.org/TR/2008/WD-wai-aria-20080204/). Functionality afforded by these technologies is not available to some people, particularly those who depend on screen readers and those who cannot use a mouse. ARIA addresses these challenges by defining new ways for functionality to be provided through APIs to assistive technology.
It is proposed to add ARIA support to Plone using the jARIA plugin for the jquery javascript library. New ARIA functionality can be tested with a screen reader (best done by disabled users), and by viewing new attributes and markup structures with FireBug.
Change History
comment:2 Changed 7 years ago by pupq
(Jut a small note that, whenever we talk about AJAXy/RIA things in class, there's always a few people asking about the accessibility of it.)
comment:3 in reply to: ↑ 1 Changed 7 years ago by esteele
Replying to MatthewWilkes:
Hi,
This doesn't seem to be a PLIP, it looks more like a feature request. Please follow the instructions on http://plone.org/news/proposals-for-plone-4-solicited and rewrite this using the template if you are willing to take the lead on this.
Matt
Just a point about this one. Christian does intend to own it. I'll work with him to get this flushed out a bit further.
comment:5 follow-up: ↓ 11 Changed 7 years ago by hannosch
One thing that is crucial to figure out for such support is how to automatically test it. Usually only a small proportion of our developers will actually know the ARIA standard, so they need to get some automated feedback about breaking things if they change some templates or JS in incompatible ways.
comment:6 Changed 7 years ago by erikrose
Clearing Owner field of 4.0 PLIPs so we can use it to mean "implementor". (Many of these owners were automatically assigned from choosing a Component that had a default owner.)
comment:7 Changed 7 years ago by alecm
This sounds like a great idea, but, as Hanno says, it really hinges on testability. If we don't have a reliable automated way to ensure AJAX accessibility is maintained, it's not likely to last very long.
comment:8 Changed 7 years ago by alecm
Additionally, this PLIP needs to be significantly more detailed and properly formatted.
comment:10 Changed 7 years ago by alecm
You can use this template as a guide to properly formatting your PLIP.
comment:11 in reply to: ↑ 5 Changed 7 years ago by esteele
Replying to hannosch:
One thing that is crucial to figure out for such support is how to automatically test it. Usually only a small proportion of our developers will actually know the ARIA standard, so they need to get some automated feedback about breaking things if they change some templates or JS in incompatible ways.
Is this something we could do using the Selenium test runner worked on at the 2009 Baarn Sprint?
Hi,
This doesn't seem to be a PLIP, it looks more like a feature request. Please follow the instructions on http://plone.org/news/proposals-for-plone-4-solicited and rewrite this using the template if you are willing to take the lead on this.
Matt