Accessibility

This is an attempt to overcome the impasse over at Accessibility improvements for vertical tabs.

As I have already stated elsewhere the general problem with regard to accessibility and usability is that one size doesn't fit all.

So we should make some of the accessibility improvements more configurable. One way which even allows for configuration on an individual user level is a separate theme for accessibility settings.

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.

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

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

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.

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.

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:

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!

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).