Ticket #11013 (closed PLIP: wontfix)
ARIA Landmark Roles for accessibility
Reported by: | cjohansen | Owned by: | cjohansen |
---|---|---|---|
Priority: | n/a | Milestone: | 4.x |
Component: | User Experience and Interface | Version: | |
Keywords: | ARIA, accessibility | Cc: | rmattb, plip-advisories@… |
Description (last modified by cjohansen) (diff)
Proposer: Christian Vinten-Johansen (cjohansen)
Seconder: None as yet
Motivation
Plone has a long tradition of supporting an accessible user interface. However, recent best practices and standards in accessible design changed without corresponding implementation in Plone. Most notable is the development and rapid adoption by browsers and screen reader vendors of the Web Accessibility Initiative-Accessible Rich Internet Application WAI-ARIA recommendation. This PLIP aims to update the Plone user interface to conformance with WAI-ARIA Landmark Roles specifications. Modifications are limited to adding role attributes to container elements of the template markup, e.g., <div class="content" role=”main”>
Assumptions
The ARIA specification includes modules for element roles, state, and keyboard control. This proposal is limited, as an initial phase, to implementing the ARIA Landmark Role Attribute Module.
Proposal & Implementation
The jARIA plugin for the jQuery JavaScript library provides support for ARIA document landmark roles and states. The goal of this project is to implement ARIA landmark roles. Future projects will focus on implementing ARIA states for dynamic content, such as live search.
Deliverables
What code and documentation needs to be produced? Standard items:
- Functional tests
- Documentation
Risks
What are the risks of implementing this proposal? Risks are very low. Implementing the document landmark roles involves addition of a role attribute to container elements of the template markup. Older browsers cannot interpret the role attribute, but the usual behavior in those cases is simply to ignore the undefined attribute.
What incompatibilities can it cause? The new sectioning elements in HTML5 have some overlap with ARIA landmark roles, but in most of of cases there is no equivalent for the ARIA landmark roles. In the case where some section elements overlap with ARIA, the redundancy is harmless.
Participants
Who is signed up to do the work? Matt Barkau, RMattB Christian Johansen, cjohansen (Real names and usernames, please)
Progress
Is any of the work done already?
- jARIA plugin for the jQuery JavaScript library mentioned above.
- https://dev.plone.org/plone/ticket/9298 and https://dev.plone.org/plone/ticket/9325
- http://plone.uservoice.com/forums/20503-plone-improvement-ideas/suggestions/230240-improve-accessibility-and-add-an-high-contrast-css?ref=title
Should there be a proof of concept? There are several implementations of ARIA in CMS, e.g., Drupal and Alfresco
Change History
comment:4 Changed 6 years ago by cjohansen
- Summary changed from ARIA Landmark Roles for accessibiltiy to ARIA Landmark Roles for accessibility
comment:5 Changed 6 years ago by spliter
Do we really need to add one more JS library? Is it possible to enable ARIA roles by updating the markup instead of involving more JS?
comment:6 Changed 6 years ago by robgietema
Adding this using Javascript doesn't seem the right way to implement this, I'd rather see changes in the markup. I'm in favor of adding the role attribute since it is also valid xhtml. The other attributes (like state and property) are not part of the xhtml specification so adding them to the default theme doesn't seem right. A better solution would be to opt-in to these attributes by creating a "Enable WAI-ARIA" setting per site and change the templates to check if this setting is available and add the attributes if it is.
comment:8 Changed 5 years ago by cjohansen
- Milestone changed from 4.1 to 4.x
Changing milestone to 4.x. So sorry, resources had to be redirected to other short-term needs.
comment:9 Changed 5 years ago by rossp
- Status changed from new to closed
- Resolution set to wontfix
PLEASE READ THIS AND RE-OPEN VALID PLIPS!
As we launch the new PLIP process we'd like to see which PLIPs:
- are still appropriate/needed
- still have owners/proposers/champions
- still have available implementers
If this PLIP should still be considered for future releases of Plone please do re-open this ticket and assign an appropriate milestone. If it should be considered for the next release of Plone, use the 4.2 milestone. Also be sure to update the PLIP description, requester, owner, etc. and include a comment detailing recent progress and new plans. We will use all these details in the new continuous PLIP process.