Mozilla Accessibility Team Planning Meeting

We looked at what we should be doing and there were a few themes. FF OS is helping drive some evolution and we discussed at what layers the solution should sit. JSAT currently uses both nsIAccessible* and DOM - how will this balance shift.

Web Evolution

• IndieUI
  • Fills actions gap on the mobile space.
  • User context (perhaps less interesting)
• Web Components
• WebIDL nsAccessible
  • Testing
  • Standardize for something like acid test

We talked about how things move from accessibility only to web native and how this might relate to our focus.

Gecko

• Stability
  • bugs
    • ARIA
    • HTML5
  • perf
    • creating the whole tree
    • Mac
• Enhancements
• IA2
• Text Interface

Visibility of Accessibility

• blogs
• metric: leadership talking points
• education
  • simplify

Miscellaneous

• UIA - Metro

Actions

• File bugs for gaps that JSAT encounters. (eeejay etc)
• Chase down TextInterface hacker. (davidb)
• Chase down IndieUI content hacker. (davidb)
• Follow up in 1:1's (all)
• A followup team meeting in a few weeks. (marco)