Last updated September 23, 2010.
These issues are important both for end users (for example, site visitors who use screen readers) and for people building Drupal sites that have to meet the accessibility requirements set by governments and other organizations. If you can help with any of these issues, please pitch in. If you want to look at non-core issues, there is a list of contributed modules and their accessibility issues too.
Relevant tag: accessibility
For more general discussions about Drupal accessibility, see the Accessibility Group and related Documentation.
Critical Issues
These issues are critical and must be fixed prior to the release of D7.
- #896364: Screen reader users and some keyboard only users need a clear, quick way to disable the overlay
- #716612: Overlay is not accessible to screen reader users
Critical Enhancements (not technically critical issues)
These issues are critical to the accessibility of D7, but will not prevent D7 from being released if they are not fixed.
- #558928: Form element labeling is inconsistent, inflexible and bad for accessibility
- #467296: Accessibility improvements for vertical tabs
Headings and Structural Enhancements
- #169912: Garland: Use appropriate header-tags following the W3C
- #514008: Allow <h2> ... <h?> in filtered html text format
- #113853: Garland accessibility: HTML order for screenreader optimisation
Purpose and Context Enhancements
- #513940: Installation task progress is not determinable non-visually need some help with preinstallation translation function st()
- #521852: Local tasks lack semantic markup to indicate an active task
- #545196: Include more contextual information in page title
- #541612: Sortable table header links lack accessible purpose and context
Colors, Contrast & Images
- #213689: Themes: avoid clashes with system colors
- #795268: Shortcut "Edit shortcuts" link has insufficient color contrast ratio
- #906738: Status report need identifying icons (WCAG 2.0)
- #740756: Ensuring Proper Color Contrast for Seven
- #447816: WCAG violation: Relying on a color by itself to indicate a field validation error
ARIA (Accessible Rich Internet Application) Enhancements
- #515262: Autocomplete requires ARIA for screen-reader users - is currently not functional for screen-reader users
- #513946: Enhance installation progress by adding an ARIA live region
- #521904: Add ARIA live region to password strength and match containers
- #890288: Improve Overlay accessibility for ARIA compliant user agents
- #414190: Add WAI-ARIA landmark roles to Garland
Form Enhancements
All of these issues have been postponed and all should now be resolved by #558928: Form element labeling is inconsistent, inflexible and bad for accessibility which is fixed!
- #522772: Improve radio and checkbox title and labeling features for accessibility
- #504962: Provide accessible labels (was "Use fieldset and legend") for compound form elements
- #501444: Administer > Modules pages make improper use of form labels
- #405360: Use aria-describedby to link form elements with form element descriptions
- #368759: All labels should require a for attributepointing to a unique id
Labels & Fieldsets
- #882694: Add missing form element titles for accessibility
- #885946: Image file upload lacks labels
- #883816: Label missing for checkbox in menu's overview table
- #885616: Labels missing from a number of locale admin forms
- #883816: Label missing for checkbox in menu's overview table
- #851174: Update options checkbox doesn't include labels
- #504962: Provide accessible labels (was "Use fieldset and legend") for compound form elements
Things that could still use some love
- #567192: Clean up Javascript implementation of Expanding simpletest groups
- #920076: With the drag/drop when switching between 'drag mode' & 'manual mode' the order should follow
- #325533: Allow <current>#fragment as a menu path
- #123103: Retain #anchors during path alias -> normal path saving
- #890284: Unauthenticated users cannot disable Overlay
- #849926: links wrapped in .contextual-links-wrapper divs are not accessible at all via keyboard alone also problems with screen readers
- #827906: Adds #title and #title_display to the weight columns of all tabledrag elements in core