Last updated June 16, 2012.
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 in the Site Building Guide, Theming Guide and Developer Guide.
Critical/Major Issues
These issues may be critical and should be fixed prior to the release of D8.
- #1493324: Inline form errors for accessibility and UX - Colors, Contrast & Images (UX)
- #890288: Improve Overlay accessibility by using modal dialogs - Overlay & ARIA
- #827906: Adds #title and #title_display to the weight columns of all tabledrag elements in core - Form Enhancements
- #742344: Allow forms to set custom validation error messages on required fields - Form Enhancements (UX)
- #1493324: Inline form errors for accessibility and UX - Form Enhancements (UX)
- #1272870: No semantics for nested comments / bad for screen-readers - Semantics
- #1101600: Users need to be able to select from list when adding menu items to a menu - Menus (UX)
- #1333292: Screen-reader users receive no info about file upload status / success - File Upload Notice (UX)
Critical Enhancements (not technically critical issues)
These issues are critical to the accessibility of D8, but will not prevent D8 from being released if they are not fixed.
- #919336: When selecting a new formatter or editing settings focus context is lost
- #1158426: Generalized CSS Classes for Focus, Invisible & Hidden - Accessibility Enhancement - Focus, Invisible & Hidden
Headings, Structural Enhancements & Semantics
- #514008: Allow HTML headings in default Filtered HTML text format
- #1315616: A definition list for the poll results
Purpose and Context Enhancements
Theming, Colors, Contrast & Images
- #213689: Themes: avoid clashes with system colors
- #999338: theme_image() alt attribute cannot be passed in $variables['attributes']
- #134359: Warn users about contrast problems when using the color module
- #717708: Document how to set logo in theme with proper alt tags
- #1270598: Decide on appropriate alt text for default logo
- #1269166: PRE tags have unreadable small font-size
- #856352: Undefined & inconsistent use of background colors
- #331893: Add colouring (and description) to password checker
WAI-ARIA (Accessible Rich Internet Application) Enhancements
- #414190: Add WAI-ARIA landmark roles to Garland
- #1272990: Make tabledrag warning message show when row weights are enabled, and add WAI-ARIA live region
- #1183042: Regression: Add WAI-ARIA roles to Core blocks
- #819724: Improve tabledrag accessibility for screen-reader users with WAI-ARIA
Form Enhancements
- #504962: Provide accessible labels (was "Use fieldset and legend") for compound form elements - Labels & Fieldsets
- #405360: Use aria-describedby to link form elements with form element descriptions - ARIA
- #882666: Core form descriptions shouldn't use a label when not associated with a form
- #607752: Highlight vertical tabs when they have elements with errors
- #851164: Tableselect: "select all rows in this table" header checkbox causing accessibility problems
- #934280: Allow #title_display = 'attribute' to be used with all native form fields
- #933004: Require #title for all form elements
- #736604: book module now without clearfix & better markup + accessibility love
- #1174938: Natively support the HTML5 #required FAPI property
Other Stuff (Zoom)
- #698976: Fix toolbar height with CSS and make text zoom usable
- #922696: New methods, standards for describing core themes on themes admin page (was Theme screenshots do not have adequate alt text...)
- #973998: Add color options for foreground text where background colors can be altered
- #717708: Document how to set logo in theme with proper alt tags
- #867830: "unpublished" status of rendered entities is not accessible
- #1175830: Update to jQuery UI 1.10 so that Drupal dialogs can be tested for accessibility
Multilingual Accessibility
- #1165476: if t() string has no translation, text should have lang="en" & dir="ltr"
- #1344078: Local image input filter in core
- #784672: Allow text field to enforce a specific text format
- #1368410: When viewing a node in another language as interface language, comment form should have correct language
- #1164682: Switch language links need language identifier
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
- #1096124: Compose tips tables need better use of id's & summary elements
- #963598: Users who cannot drag and drop require clear anchor text to find Dashboard Administration page
- #1182522: Use <menu> and contextmenu attribute for contextual links
- #1320126: Move Toolbar mark up into the "page bottom" region
- #325533: Allow <current>#fragment as a menu path
- #1349722: Who's new & Who's online blocks have empty headings
- #1361102: Expose visually-hidden visibility for Field's Label in Manage Display
- #1060700: Text in new topic and new post links does not describe its purpose
- #1136680: theme_more_link should have more context
- #1328770: Allow "skip to main content" visibility to be toggled
- #998302: 'Skip to main content' link links to region, not content
- #314385: Make position of #description configurable
- #817176: UI Pattern suggestion for better accessibility of table drag implementation
- #1106344: Taxonomy term reference field headers always should be rendered with a HTML header (invisible or not)
- #1328970: element-invisible class does not work properly in Chrome and Safari for inline elements