Accessibility Information for Core Gecko Developers

  1. HTML Accessibility

    Dynamic web content is not accessible because it uses vanilla <div>s and <span>s combined with JavaScript rather than declarative markup to describe the behavior of custom widgets such as menus and tree views. These widgets are often not even keyboard focusable, and assistive technologies do not understand these widgets. This document shows several interactive desktop-style widgets that are accessible by keyboards and assistive technologies, and outlines a plan being developed by IBM, Mozilla, and the WAI Protocols and Formats Working Group (PFWG) to address the issue of DHTML accessibility.

  2. Mozilla Accessibility Architecture

    This document explains how we implement the cross-platform accessibility layer in Mozilla. It contains a class hierararchy and an explanation of the accessibility cache.

  3. Unix Accessibility Project

    This document describes the SUN accessibility project.

Join the Mozilla Accessibility Community

Live Chat

Both end users and developers are invited for discussion on the live IRC channel at irc.mozilla.org/#accessibility. Since this is a worldwide effort, there is always a good chance to find someone to chat with there, day or night.

Newsgroup and Mailing List

We have two discussion lists, which can be read via a newsgroup reader, as a mailing list or via Google groups.

Purpose Newsgroup Mailing list Google group
Developer discussion mozilla.dev.accessibility subscribe/unsubscribe Google group
End user support mozilla.support.accessibility subscribe/unsubscribe Google group