Accessibility/Planning: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(21 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Misc ==
== brainstorm ==


* Requested an intern for summer 2011


== Trips ==
* More brown bags
 
* HTML braille API
* Marco to Toronto: Nov 15th
** emscripten liblouis?
* Alexander to Toronto: Nov 8th
* Create extensible ARIA semantic system.
* New contractor to Toronto: Nov 8th?
* More accessible games
 
* [[Accessibility/2012CorePicture|Core Picture]]
== Projects ==
* [https://bugzilla.mozilla.org/show_bug.cgi?id=624628 Accessibility project Identity/Face]
 
* A11y enabled on mac in Q1/Q2
=== deXPCOM work ===
* mathml
 
* music/chemical other specific languages
*Rework native objects (follow AccEvent and nsAccEvent)
* aural css
**add native interfaces for every XPCOM interface
* alt input (IndieUI)
***nsIAccessNode -> nsAccessNode
* other print impairments... or LD
***nsIAccessible, nsIAccessibleValue, nsIAccessibleHyperLink -> nsAccessible
* Detect system high contrast/invert (windows), and apply color filters in Firefox (talk to UX about possible UI).
***nsIAccessibleTable -> TableAccessible
* Addon ideas:
***nsIAccessibleText, nsIAccessibleEdtiableText, nsIAccessibleHyperText -> nsHyperTextAccessible
** No-background no-CSS-colors pref in Mobile
***nsIAccessibleDocument -> nsDocAccessible
** Remove viewport no-zoom in mobile
***nsIAccessibleImage -> nsHTMLImageAccessible, nsXULImageAccessible
** Color filters UI in mobile and desktop
***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 ===
[Alexander to describe the work here]
 
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)
 
====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]

Latest revision as of 18:50, 30 September 2014

brainstorm

  • More brown bags
  • HTML braille API
    • emscripten liblouis?
  • Create extensible ARIA semantic system.
  • More accessible games
  • Core Picture
  • Accessibility project Identity/Face
  • A11y enabled on mac in Q1/Q2
  • mathml
  • music/chemical other specific languages
  • aural css
  • alt input (IndieUI)
  • other print impairments... or LD
  • Detect system high contrast/invert (windows), and apply color filters in Firefox (talk to UX about possible UI).
  • Addon ideas:
    • No-background no-CSS-colors pref in Mobile
    • Remove viewport no-zoom in mobile
    • Color filters UI in mobile and desktop
Retrieved from "https://wiki.mozilla.org/index.php?title=Accessibility/Planning&oldid=1020133"