Platform/2009-Accessibility-Goals

What is this?

Mozilla users deserve first class accessibility. This is a list of accessibility goals to prioritize, estimate, and assign resources to.

Legend:

• [#] - The number of person days estimated for this issue.
• [p#] - Priority, lower is higher.

Gecko

• Bugfixing of course
  • Expand automated test coverage [100]
  • Regression fixes [100]
  • Triage [20]
  • Manual testing [20]
• New work:
  • WAI-ARIA 1.0 completeness
    • additional events [30]
    • additional semantics [15]
    • spec changes [20]
    • normative changes as other browsers implement ARIA [10]
  • HTML 5 (need to update tracker bug 389237)
    • drag and drop [4]
    • <canvas> [0-20]
    • <video> [?] Need report from Silvia.
    • SVG
      • focus, keyboard navigation (bug 409404) [10]
    • MathML [20]
  • Mac OS X
    • performance tracker bug 454202 [20]
    • architecture bug 342989 [20]
    • improvements tracker 336306 [50]
  • Mobile
    • TODO [?]
  • Performance testing and profiling
    • Windows [?]
    • Linux [5]
      • run valgrind-like tools and analyze places to optimize.
    • Mac [10]
      • Shark, Spin Control, Instruments, MallocDebug
• Architecture/Code refactoring
  • Perf optimization [30]
    • Why? slow == unusable, unusable == inaccessible
  • We will redesign "as we go" [30]

Community Collaboration

• Standards
  • W3C WAI-ARIA user agent implementor guide
    • edits [15]
    • meetings [15]
      • Note: this group is being formed soon to make sure that implementations don't delta too much. This is vital for DHTML a11y to work in any practical sense.
• Evangelism
  • Cultivate patch contributors
    • To provide our users with a good web experience we need a larger team. The proven way to do this is via a combination
      • Foundation mini grants [2]
      • responsiveness to questions on #accessibility [20]
      • Pursue resources from companies that benefit from FF's accessibility [2]
  • Work with Assistive Tech folks (NVDA, Orca, FS etc)
    • bug triage [10]
• Labs
  • We need to be part of the early discussions in labs projects, so that more informed technical decisions can be made. In this way we might help with things like the Bespin/canvas a11y issues. [5]

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?
  • Bespin, canvas a11y?
• How do the high level Mozilla values and goals prioritize our work and focus, in accessibility? How can we be most effective?
• <video>
  • follow-on implementation of ideas explored in Silvia Pfeiffer's work
• SVG, MathML
• <canvas>
• Firebug Accessibility
  • Accessibility support of FB itself
  • Accessiblity testing support
• xforms -- priority?