Introduction

Let's try to figure out what's going to be best for Web2.0+ accessibility in terms of ATRC involvement 2008.

Question: Will Becky and/or Pete be on Dojo A11y for 2008? This will help us guestimate work required etc.

• Dojo DHTML Accessibility
  • Firefox 3 support -- bring ARIA support up to date
    • Live regions
    • Drag N Drop
    • active descendant
    • Tree grids
    • dojox
  • Dojo Community work: put a11y requirements into Dojo patch review process
  • Automated A11y testing
  • Spreading support into other Toolkits
• Other toolkits, support developers, community building
  • JQuery
  • Scriptaculous
  • Prototype
  • Cross-toolkit code
  • Tutorials and documentation
  • Monitor xtech list
• Browsers, support developers
  • Opera
  • AT developers
  • File bugs in Firefox
  • Any others
• Standardization & future efforts
  • Role & property extensibility
  • Diagram accessibility
  • HTML 5 harmony
  • Feedback on ARIA specs

Fluid involvement

The Fluid Project is an open source community dedicated to improving the user experience of other open source projects.

Fluid builds accessible, rich user interface components that can be reused across web applications. Fluid also provides design guidance and accessibility support for user interface designers and developers within open source communities. Our work is freely available under the Educational Community and Creative Commons licenses.

Fluid components are more than widgets. They encapsulate larger-scale activities and workflows, providing improved ways to navigate, locate, and manage files and content within a web application.

Note: the 2007 Dojo a11y work (Simon and David) is/was funded by the Mozilla Foundation and IBM Faculty Awards through Fluid.

* What are the options for the best real collaboration here?
 * Fluid helps with design and implementation of cross-platform utility.
 * Fluid as a team takes on an aspect of pushing ARIA
 * Fluid donates staff
  * to push Fluid-ARIA requirements as they come up.
  * to push an aspect of ARIA.
 * Fluid takes on coordination of ATRC ARIA pushing
 * Fluid has no role.

How can Fluid Help with DHTML Accessibility?

* One of Fluid's current goals: More choice in accessible DHTML toolkits
* Summary: Fluid wants to contribute making DHTML more accessible and usable as a whole
* Help provide a community for DHTML accessibility
  * Collaborating on development:
   * Cross-toolkit keyboard handling, focus management, ARIA support, etc.
   * Bug fixing
  * Contributing usability advice to toolkit developers:
   * Bug and enhancement reporting
   * Sharing usability evaluations, testing process, and knowledge

[David here, I like the community infrastructure support aspect. If Fluid could assist in connecting people... perhaps using the Fluid teleconferencing know-how. I also really like the usability aspect and think that could be an arm of Fluid... reaching out to useability folks and spreading accessibility that way. Usability people should be or become accessibility experts IMO.]