Accessibility/SummaryPost1.9
From MozillaWiki
Accessibility features & fixes still needed for Firefox
Ordered by importance
Try for Firefox 3.1/3.5
- Text attribute support in IAccessible2 & ATK (bug 345759)
- Impact: IE parity, usability for screen reader users
- Difficulty: high
- Estimate: 1.5-2 months
- Key navigation with plugins
- Sub-items:
- Key swallowing
- Tab navigation
- Accessibility features & fixes still needed for Firefox (bug 348279, bug 330411, bug 430412, bug 93149, bug 78414)
- Impact: 508 compliance, usability
- Difficulty: extremely high (4 kinds of plugins supported, deals with core focus code, controversal approaches, need to cooperate with external vendors)
- Estimate: 4 months
- Sub-items:
- Accessible relations
- Sub-items:
- Relation cache: bug 381599
- Support multiple relations: bug 345780
- aria-owns relationship not fully supported (menubars, etc.): bug 374722
- Impact: Web 2.0 accessibility, important for ARIA support
- Difficulty: high
- Estimate: 1 month
- Sub-items:
- Tree and tree grid API fixes:
- Harmonize tree and treegrid support for XUL and ARIA: bug 367905 and bug 427956
- Impact: usability of trees and treegrids across platforms -- these are arguably the most important widgets, because they can't be done in HTML but are very useful for apps like mail and calendar
- Difficulty: high (tree grids are really complicated, JS tree grids can do anything, there is new API ground here, need to work with AT vendors to support changes)
- Estimate: 1.5 months
- Correct selection events for HTML, XUL and ARIA
- Fix and refactoring bug: bug 414302
- Impact: better support for tabs in NVDA and support for multiple selection across ATs
- Difficulty: low to medium -- it's a big fix but most of the code is already there in the bug, as well as a definition of the expected behavior.
- Estimate: .5 months
- Ongoing general fixes for ATK, ARIA, IA2, XUL UI, key nav, performance, leak issues, crashes, etc., including the approximately 10 new legitimate bugs that are filed each week.
- Ongoing fixes as HTML 5 features are added:
- Difficulty: medium
- Impact: 508 compliance, ability to access basic kinds of content
- Estimate: total out of 2009 work, 2 months
The following may wait until after 3.1
- Math accessibility
- Difficulty: high (need to work with standards groups & AT vendors, API design is unclear)
- Note: HTML WG is looking at ways of allowing MathML inside text/html. That would lead to increase usage.
- Impact: 508 compliance, ability to access diagrams and custom widgets, Web 2.0 accessibility
- Estimate: 2-3 months
- SVG and role extensibility
- Difficulty: extremely high (need to work with standards groups & AT vendors, API design is unclear, keyboard navigation is always difficult in Gecko)
- Note: HTML WG is looking at ways of allowing SVG inside text/html, which would lead to increased usage.
- Note: Opera already implements SVG keyboard navigation, so we should look at what they have done
- Impact: 508 compliance, ability to access diagrams and custom widgets, Web 2.0 accessibility
- Estimate: ARIA work - 2 months, Keyboard navigation work - need to scope work .. wild guess is 2 months. Total estimate, 4 months.
- OS X accessibility
- Note: this may be done via an API bridge, in which case the work can be moved out to Mozilla grants. The strategy is still unclear. If a bridge is used, then most of the work will be testing and guiding the grants & AT porting
- Difficulty: extremely high -- need to work with closed source screen reader from Apple. Complete mapping of nsIAccessible to Apple's NSAccessibility is unclear. No way to get our bugs in Voice Over prioritized
- Impact: 508 compliance on OS X, usability on OS X, industry play of first accessible cross platform app development (HTML, JS and XUL)
- Estimate: 6-12 months
