Accessibility and Drupal
To make your site accessible...
- Select good themes or develop your own. Starting with a good theme is the fastest way to an accessible Drupal site.
- Drupal Theme Accessibility Guide
- The Eleven Most Accessible Drupal 6 Themes...evaluated with XHTML, CSS, WAVE and FAE Evaluators (off-site link).
- D-theme breaks down Drupal themes by passing: US 508, Wave, WCAG A, WCAG AA, and WCAG AAA (off-site link).
- Pick accessible contributed modules. Accessibility Issues in Contributed Modules
- Identify accessibility issues, communicate them, submit patches, test patches, and/or lobby for patches.
- Train authors and provide them with good authoring tools.
- Validate and Test Content
- Apply fixes others have developed:
- Accessible Date Inputs on Forms A fairly well described process for theming date inputs. Audience is themers and coders.
- Contributed Modules to Help with Accessibility
- Make sure that a difference in color is not the only way you convey meaningful information — such as whether or not an entry is valid.
- When you select color schemes, make sure there is enough contrast between text or meaningful images and background for people with less than perfect vision to see the text and images clearly.
Consider Contrast When Pairing Colors
To appreciate the importance of selecting color pairs (foreground and background) carefully, consider these points:
- According to Vischeck, roughly 1 in 20 people have some sort of color vision deficiency.
- Only about 52 percent of the people who have tried this self test for color blindness have been able to correctly identify all six numbers.
If you take the self test for color blindness, you might better understand the problems a poor choice of colors can create for people who cannot see all colors well. Even if you get every answer in that test correct, you will probably have to look carefully to see at least one or two of the numbers. If so, you will be experiencing how difficult reading is when the foreground color — the color used for the text — has too little contrast against the background color — the color used for everything else.
What is sufficient color contrast?
As part of its Web Content Accessibility Guidelines (WCAG 2.0), the Worldwide Web Consortium (W3C) has established guidelines for sufficient color contrast. Briefly stated, they are:
- For large text, such as headings:
- A color contrast ratio of at least 3:1 normally provides enough contrast.
- A color contrast ratio of at least 4.5:1 is necessary when you must have enhanced contrast.
- For regular text:
- A color contrast ratio of at least 4.5:1 normally provides enough contrast.
- A color contrast ratio of at least 7:1 is necessary when you must have enhanced contrast.
When would I need enhanced contrast?
Use the guidelines for enhanced contrast when these or similar conditions exist:
- A heading needs extra emphasis — for example, because the information is urgent.
- Other text is finer or smaller than normal.
- The information is likely to be used with poor lighting or high glare.
- People with poor vision are a significant portion of your audience.
How can I measure color contrast?
Fortunately, there are a number of free tools you can use to check the contrast of color pairs in your Web pages. One is the Paciello Group's free Colour Contrast Analyser, which is available in both a Windows version and a Mac version. When you use this tool:
- Be sure to set it to measure the luminosity difference. (It also gives values for color difference, the algorithm that was used under WCAG 1.0.)
- Be aware that it will say that some color pairs fail when their contrast ratio is acceptable under WCAG 2.0. So be sure to read the contrast ratio, not just whether the label is "Pass" or "Fail." (The tool is adjusted for contrast ratios that appeared in an earlier draft of WCAG 2.0.)
To learn more about these issues, go to WCAG 2.0 Guideline 1.4 and scroll down to 1.4.3 Contrast (Minimum) and 1.4.6 Contrast (Enhanced). There you can also find tips on meeting each guideline and more explanations to help you understand each guideline.
Drupal accessibility resources
- Contributed Modules to Help with Accessibility
- Drupal Group on Accessibility
- Video and Slideshow from Drupalcon Szeged 2008
Drupal 7 accessibility notes
Although Drupal 7 hasn't been released yet, there are a number of changes in core which will greatly assist with accessibility. Drupal 7 will see improvement in the Forms API (FAPI), but will also come with a standardized way to make descriptive text visible to screen readers and invisible to sighted people. To implement this in your templates you can just wrap elements with the CSS class="element-invisible". To implement within a module you can use this code snippet:
<?php
l(t('Read more...<span class="element-invisible"> about %title</span>', array('%title' => $node->title)), 'node/' . $node->nid, array('html' => TRUE));
?>an alternative implementation is:
<?php
$link['title'] = '<span class="icon"></span>' . $item['link']['title'];
$link['attributes'] = array('id' => 'toolbar-link-' . $id, 'class' => array('to-overlay'));
if (!empty($item['link']['description'])) {
$link['title'] .='<span class="element-invisible">' . $item['link']['description'] . '</span>';
$link['attributes']['title'] = $item['link']['description'];
}
?>About web accessibility
- W3C Validation (basic requirement!)
- Dive Into Accessibility
- Paciello Group
- W4A - W3C Web Accessibility Conference - ("Web for Anyone")
Techniques and best Practices for HTML, digital media, JavaScript
- i CITA HTML Best Practices has HTML and Javascript best practices with examples categorized by navigation, text equivalents, scripting, and style.
- Accessible Digital Media by WGBH Boston has fairly concise best practices with excellent examples categorize by images, forms, tables, digital publications, interactivity, graphs, math, and multimedia.
- iCITA ARIA Examples has examples of ARIA widgets and roles such as grids, menu bar, slider, tooltip, and tree.
- WAI-ARIA Best Practices outlines how Rich Internet Application such as drop down menus, sortable grids, live content, etc. can be more accessible through ARIA tagging.
- Research-Based Web Design and Usability Guidelines from the U.S. Department of Health and Human Services has long and detailed best practices categorized by page layout, navigation, scrolling and paging, headings, titles, and labels, links, text appearance, lists, widgets, graphics and multimedia, writing, content organization and more.
- Quick Reference on WCAG 2.0 Requirements is actually quite long but fairly detailed.
Standards
- Illinois Information Technology Accessibility Act (IITAA) Web Accessibility Standards
- Section 508 Information Technology Accessibility Standards
- W3C Web Content Accessibility Guidelines (WCAG) 1.0
- W3C Web Content Accessibility Guidelines (WCAG) 2.0
Tools for evaluating accessibility
- http://fae.cita.uiuc.edu/ Functional Accessibility Evaluator
- http://wave.webaim.org/ WAVE for evaluating accessibility
- Bobby – an automated checking program for compliance with Section 508
- Usablenet.com LIFT
Programming tools for accessibility
- ARIA Accessible Rich Internet Applications (Making Ajax and Related Technologies Accessible)
- AxsJAX - Access-Enabling AJAX
Screen readers
- www.tiresias.org – a site with information on many assistive devices for vision impaired users
- Wikipedia screen reader capabilities
- Wikipedia list of screen readers
- JAWS
- Window-Eyes
- Hal
- Narrator (free in Microsoft Windows)
- ZoomText from Ai Squared
- Fangs - the screen reader emulator (Firefox extension)
- NVDA (NonVisual Desktop Access) - is a free and open source screen reader for the Microsoft Windows
- Guidelines for Accessible and Usable Web Sites: Observing Users Who Work With Screen Readers
- Web Anywhere
