Accessibility/Planning: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 1: Line 1:
== Currently drafted Q2 Goals ==
== Currently drafted Q2 Goals ==
* Text. Finish work for accessible text interfaces to include only cached text usage.
[[Accessibility/Planning/Goals]]
* E10S. Adjust accessibility implementation plan to fit electrolysis desktop work.
* Mobile. Mobile accessibility: work with product management to complete  functional requirements and priorities. Bonus: initial implementation of Talkback behaviour.
* Remove 75% of existing XPCOMery from the accessibility module.
* Make all implemented HTML5 inputs accessible. Bonus: implement canvas a11y proposal.


== Projects ==
== Projects ==

Revision as of 16:07, 31 March 2011

Currently drafted Q2 Goals

Accessibility/Planning/Goals

Projects

deXPCOM work

  • Rework native objects (follow AccEvent and nsAccEvent)
    • add native interfaces for every XPCOM interface
      • nsIAccessNode -> nsAccessNode
      • nsIAccessible, nsIAccessibleValue, nsIAccessibleHyperLink -> nsAccessible
      • nsIAccessibleTable -> TableAccessible
      • nsIAccessibleText, nsIAccessibleEdtiableText, nsIAccessibleHyperText -> nsHyperTextAccessible
      • nsIAccessibleDocument -> nsDocAccessible
      • nsIAccessibleImage -> nsHTMLImageAccessible, nsXULImageAccessible
      • nsIAccessibleApplication -> nsApplicationAccessible
    • get rid all QueryInterface calls for accessible objects
  • Rework XPCOM code
    • add XPCOM wrappers for native objects
    • add cache for XPCOM wrappers
    • unify methods of XPCOM interfaces (name convention)
  • Get rid platform specific wrap classes
    • ??

DOMi

Contract planned

not organized ideas (for now)

new features

  • provide js console for viewers, it can shared between left and right panel and placed under panels, output area should be presented as well, it can be turned on/off by menu or button placed at the bottom of domi. It's similar to option of context menu on accessible tree viewer.
  • add an ability to inspect several objects the same time, each object viewer can be hosted in own tab, context menus so that you can easy inspect related objects and switch between them
  • add an ability to inspect any property of accessible interfaces (new tabs in accessible properties viewer)
  • add 'find node by click' for accessible tree view
  • add custom filters for watched events by target
  • add ability to filter handled event list by values in tree columns of event list

bugs

  • fix blinking (it's buggy, sometimes shows wrong area and sometimes blinking artifacts are left, for accessible objects nsIAccessible::getBounds should be used).

small enhancements

  • conext menu item on accessible events viewer to register event listeners (should switch to 'event watch' tab, find event in the list, enable event listener and focus event listener area)

Documentation

[todo]

Speech input

[HTML Speech Incubator Group]

TTS from content

[HTML Speech Incubator Group] [humph]