All you WCAG nuts this is the place for you: how to make Drupal more accessible. Hints, tips, discussion and patch proposals.
Brainstorming for an accessibility proposal
I think that it would be an excellent idea for there to be at least one accessibility based project proposed for GSOC. Clearly the benefit being that Drupal's accessibility is enhanced, and a student who may be interested in accessibility is given the opportunity to improve their skills through the mentorship of individuals who have experience in the field.
Read moreLimitation of Drupal Development Mode for "Low Vision" Users
If a web designer is one of the 20% of Americans who cannot read the normal font sizes of Drupal black drop down administrative menues at the top of each pate, his/her only current solution appears to be changing the Zoom in the browser--typically to 150% or larger. However if that is done, some of the menues extend beyond the bottom of the screen. If the user mouses to the scroll bar to scroll down to see the whole drop down menu, the menu disappears. The cursor must be on the black menu somewhere in order to keep the menu visiable.
Read moreTools for Choosing Accessible Colors
At last night's Austin Drupal meetup, I promised to post the links to the tools I demonstrated for testing color schemes for sufficient contrast. I plan to share more about these in the Accessibility portion of Drupal documentation, but for now, here are the places to find the tools:
Read moreAccessibility at DrupalCon SF 2010
I've proposed a presentation called 'Accessible Site-Building in Drupal' for DrupalCon SF 2010:
http://sf2010.drupal.org/conference/sessions/accessible-site-building-dr...
Are you attending DrupalCon? Please vote to support this presentation!
Has anyone else proposed an accessibility topic for the conference? I would welcome joining forces and also strategizing for some BoF and other conversations.
-Brandon
Read moreWeb Accessibility (W4A) Conference April 26-27, Raleigh, North Carolina
The Alliance for Technology Access & Drupal
Are any Drupal community members also members of The Alliance for Technology Access?
I'd like to contact people regarding disability issues,
web access, and activism for the disabled.
Thanks for your interest.
==============
The Alliance for Technology Access
http://ataccess.org/
Web Access
http://ataccess.org/rresources/webaccess.html
Wiki to Create Drupal Accessibility Statements
Following the discussion thread on this topic, the following are a proposed list of Accessibility pages that should be featured on Drupal.org to ensure that there is clarity about Drupal's Accessibility & a statement of commitment to the future. Please feel free to review & modify this wiki.
A version of this has been posted to Drupal.org
Generic introduction with statements of commitment and links to more - drupal.org/accessibility
@Mike and everyone, I don't have content to link to yet — at least not that I know of — but I would like to propose this as a start on the general approach and tone of our accessibility statement.
Drupal Supports Accessibility
As an inclusive community, we are committed to making sure that Drupal is an accessible tool for building websites and that Drupal helps you create websites that are themselves accessible.
Starting with Drupal 7, we have committed to ensuring that all features of Drupal core conform with two sets of guidelines from the Worldwide Web Consortium (W3C):
- Web Content Accessibility Guidelines (WCAG) 2.0
- Authoring Tool Accessibility Guidelines (ATAG) 2.0
Whenever possible, we also update the previous version of Drupal core, Drupal 6, to enhance its accessibility.
Read moreTime for a new Accessibility Groups Manager?
I'm not really sure what power the groups manager has been given (if any), but this group's current web manager vigo hasn't contributed (as far as I can remember) to the discussions in the last year.
This is now a much more active group than it was when it was first started. I think that there are a number of folks here have contributed to the discussions and to fostering a community around improving Drupal's accessibility.
Read moreCreating a Drupal Accessibility Statement
I've been looking at what we've done here on Accessibility - http://drupal.org/node/394094 - it's a good intro, particularly for Drupal developers on accessibility. However, it isn't written in a manner that's general, or strong enough to be meaningful to others at this point. I thought it was worth while thinking about (and later drafting in a wiki) an accessibility statement.
I'm not sure we're in the position where we can get Drupal developers to sign onto something as strong as what TypoLight claims:
Read moreTYPOlight does not treat accessibility as just an additional feature and generates accessible XHTML strict output that meets the W3C/WAI requirements in the front end and the back end. The system degrades gracefully if JavaScript is not available or not enabled.
Screen reader only legend tags
There are is a Firefox browser bug where some properties don't work for legend tags (Read about it http://stackoverflow.com/questions/1097369/hide-html-form-legend-using-css that linked to http://marc.baffl.co.uk/bugs.php#legend ).
So, the drupal 7 element-invisible from http://drupal.org/node/473396
with the css defination of
.element-invisible {
height: 0;
overflow: hidden;
position: absolute;
}
does not work. The position element and height 0 take no effect and the element still appears visually.
Some notes after an accessibility review on a site
In random order, rough, wrote as making changes. Most interesting is the aria-required and adding the h2's to status messages, etc.
If using beauty tips, beware of using non-100% opacity due to those with visibility issues.
Add h2's around messages and role alert.
<ul>
<li role="alert"><h2>
<span class="status-message-box status-status"> </span> Your password and further instructions have been sent to your e-mail address.
</h2></li>
</ul>
D7 Accessibility Update: 2 weeks left
3 more patches have been committed this last week, but others are stuck with disagreement about how to approach accessibility or simply need review.
3 more committed:
- #386462: Skip navigation in all core themes
- #540282: Accessibility improvements for the toolbar
- #622136: User filter accessibility
Needs Help:
Read more"Meta Accessibility" - How to Make Accessibility Features Known to the User
What if your site is perfectly accessible but no one knows about it?
This question came up while working on Accessibility improvements for vertical tabs , together with some first thoughts on this issue.
Read moreD7 Accessibility Update: 3 weeks left
The focus of the Drupal 7 code slush has now shifted to Accessibility, Usability and Performance. Dries and webchick are prioritizing many patches that the 'Accessibility Task Force' had focused on. Yay!
Read moreThe Accessible Content Module and the Accessible module
You all might remember an earlier post I made about the QUAIL accessibility library and its potential for checking content for accessibility. Well, now you can download the fruits of that labor!
There's a readme file in there that outlines how to download and setup the module. It comes packaged with the quail lib for now, but if it goes to drupal.org I'll remove it and require folks to download it from it's own site on code.google.com.
Read moreGarland heading patch needs review for D7
An important accessibility patch needs your help: Garland: Use appropriate header-tags following the W3C.
Please take a look and review this page. @mgifford, @JeffBurnz and many others have contributed.
It's simple to review this one: just start with Drupal 7 head and apply the patch (direct link below).
Read moreDrag-n-drop accessibility strategies
I'm worried our strategy is lacking to solve Drag and Drop for table rows not accessible to screen-reader users. This issue is flagged as critical for Drupal 7 and it's very important for accessibility of many admin screens in Drupal core and contrib.
Not accessible or usable
So far the patches in the issue queue allow users to choose to disable the javascript drag-n-drop and instead keep the weight and parent fields available.
Read moreMore use of "media" attribute for providing device dependent CSS
By using CSS's "media" attribute we could provide customized CSS for different end user devices (browsers, screen readers, Braille devices, etc.) without interfering with other devices' style sheets.
media=
" { all | aural | braille | embossed | handheld | print | projection | screen | tty | tv } "
(see http://reference.sitepoint.com/html/style/media for details) Read more
Keyboard Navigation - Resources & Best Practices
Last updated by mgifford on Tue, 2011-05-03 19:39
Following the suggestion at Accessibility improvements for vertical tabs here's a page to collect some of the scattered information on keyboard navigation.
Read moreFind a Better Name for "skip-navigation" Class
We need to come up with a good name for a CSS class, but I don't want this discussion to clutter up the issue queue. (Let's reserve the queue for presenting and discussing patches that fix functional or programmatic problems.) So I'm posting this item to see if we can develop an idea that is better than the ones we've already come up with.
Read more