Accessibility/GoalStaging

Current topic: Q4 Accessibility Goals

As per group discussion: MarcoZ, surkov, davidb

• DHTML performance
  • Event handling
    • Code reorganization
    • Crashers
    • Implementation of throttling/delayed computation/smarter caching
• Fix keyboard support for HTML5 contentEditable
  • Add accessibility support for HTML controls inside of a contentEditable
• Polish table/grid/treegrid/etc (all major issues known at this point). For example, we shouldn't die trying to be in time to implement row/column add/remove notifications since they are not used by AT currently AFAIK. But on the another hand we need to fix some selection issues for crazy tables that might be seen in a wild.

Consider:

• Get an agreement on ATK text interface means. Do not plan to implement anything because it's big area we need to plunge into and we won't be in time. Also these discussions might take a significant amount of time.

Drop:

Painful to drop, but we have to be realistic.

• text offsets problems as per ATK text interface. However text change events should be addressed in our performance goal where it's possible (event coalescing).
• Text attributes implementation. We do a decent job, but are not complete.
• HTML 5 canvas. Shadow tree impl? Are there enough cases of html 5 canvas use where this work is justifiable over our other priorities?

Ongoing:

• W3C work
• Open A11y (IA2, ATK feedback)
• regressions
• triage