Proposed Mozilla accessibility strategy

I’ve written and published a new proposed high-level strategy for Mozilla-related accessibility efforts. Note that this is not a detailed roadmap for future work, and not a firm commitment to fund or perform such work. Rather it is intended to provide a context within within which we can make overall decisions about where we should concentrate funding and effort. This is especially important because our resources are very much finite, and we will need to make decisions about what we should do and what we should leave undone or leave to others to do.

This is very much a work in progress, and I’ll be revising this over time to reflect changed circumstances and priorities. I’ve reviewed the document with a number of people involved in Mozilla accessibility efforts, and would be happy to consider further revisions based on public comments.

Finally, note that this document supplements and (to some extent) supercedes my previous posts from 2006 and 2007 on making choice and innovation accessible to all and a proposed vision and strategy for Mozilla accessibility.

4 thoughts on “Proposed Mozilla accessibility strategy

  1. David Baron

    The document currently says: “Making applications accessible should be a core task of Internet and web developers, as important as improving performance and usability in general.”

    I think it is also worth emphasizing that the technologies of the Web should be designed so this is as little work as possible. When standard semantic markup can provide the information needed for accessibility, they should be used by assistive technology, rather than making authors have to write something else that means the same thing.

    The goal should be to make as much information as possible accessible to as many people as possible, not to criticize or demonize authors for their prioritization decisions.

  2. Pingback: Last week in the “Accessible” module, April 20, 2009 « Marco’s accessibility blog

  3. hecker Post author

    Scott: This is better addressed in the mozilla.dev.accessibility newsgroup (and I’ll forward your comment there). As noted, the strategy is a living document, and if there’s a consensus that UUAG compliance should be called out in the strategy then we can change it accordingly.

Comments are closed.