Platform/2009-Accessibility-Goals: Difference between revisions
< Platform
Jump to navigation
Jump to search
DavidBolter (talk | contribs) |
DavidBolter (talk | contribs) m (→Gecko) |
||
| Line 11: | Line 11: | ||
* Code refactoring | * Code refactoring | ||
** Maybe best to do in small iterations, as we go. | ** Maybe best to do in small iterations, as we go. | ||
* Get Mac accessibility to point where | * Get Mac accessibility to point where it is included in default builds. | ||
** Is lazy instantiation easy on Mac? | ** Is lazy instantiation easy on Mac? | ||
Revision as of 21:41, 11 February 2009
What is this?
Let's try and capture on this page the work and goals we have for 2009.
Gecko
- Bugfixing of course.
- WAI-ARIA 1.0 completeness
- HTML 5 related accessibility
- Performance testing and profiling
- Code refactoring
- Maybe best to do in small iterations, as we go.
- Get Mac accessibility to point where it is included in default builds.
- Is lazy instantiation easy on Mac?
Community and Outreach
- W3C work: WAI-ARIA user agent implementor
- Evangelism
- mothering #accessibility
- work with Assistive Tech folks (NVDA, Orca, FS etc)
- help triage GNOME FF bugs
- Cultivate patch contributors
Rough Notes, Ideas, Questions
- What is the current state of the art for mozilla perf testing? Do we have boxes doing this on cron jobs?
- How shall we organize the work?
- Assist Foundation with grants/giving?
- Provide domain expertise to other groups? Mobile? Labs?
- How do the high level Mozilla values and goals prioritize our work and focus, in accessibility? How can we be most effective?
- SVG, MathML, video ...