Accessibility/Planning

Q3 goals:

1. Provide accessibility support for existing and new HTML5 input controls
2. Reduce the a11y performance hit by at least 50% for tools that require only limited accessibility support.
3. Improve/fix life cycle management of our (node and frame based) accessible objects.

Notes/Measuring:

1. Mochitest coverage + Marco screen reader testing. Controls added in the last two weeks will not be officially measured. A nice to have here is helping drive accessible drag and drop.
2. This goal will include general accessibility performance work. But more specifically we want to know when our more expensive accessibility support is not required. Filtering this support should be doable in this quarter if we can detect accessibility support requirements at run-time. Tools that don't require full accessibility include: tablet pc, anti-spyware, and some add-ons.
3. This goal is really about core accessibility work that Alexander is planning to work on. We can create a meta bug for this work. Scoping this goal is tricky.

Misc: Wondering/worrying about our mobile accessibility story.