Accessibility

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.

There is currently an open issue in the d.o issue queue Add colouring (and description) to password checker (#331893). The issue hasn't received much attention lately and I am curious what thoughts there are from usability and accessibility folks on the proposed patch in comment #36.

This patch essentially tests the password strength and displays a growing colored bar which changes colors depending on password strength. The patch also displays text to represent the strength of the password.

The semantic structure of a discussion can be ruined if a comment includes code for headings that are at a higher level than the title of each comment. In discussions in Drupal, the title of the page is an <h1>, key regions are headed with <h2>s (which sometimes do not appear on screen but are available to screen readers to define regions that are obvious on visual inspection), and each comment begins with an h3. So if any heading is added within a comment, it should be no higher than an <h4>, right?

Present on the call

• Mike Gifford
• Everett Zufelt
• Brandon Bowersox
• Valeria Brigatti
• Rob Russell
• Jeff Burns

One week to Code Freeze

On the call we discussed the fact that there is only one week remaining until code freeze. Because of this certain issues need to be prioritized. Some of the current issues in the queue will be able to be fixed after code freeze, others unfortunately will not be fixed for the Drupal 7 release.

Autocomplete

I posted this awhile back on the Nice Menus issue queue with no response. Wondering if perhaps I am doing something wrong on the accessibility testing front (using WAVE to check site)....or if someone else has experienced this issue as well:

Next Conference Call

Monday August 24
11:00am Eastern Time (U.S.) (-05:00 UTC)

If you want to participate please e-mail
everett@openconcept.ca

Agenda

Please feel free to add agenda items.

• Discuss solutions to outstanding problems listed in Everett's blog article Update to the State of Drupal 7 Accessibility.

Participants

<

ul>

On Monday, August 10, we had the second of three planned Drupal 7 accessibility taskforce conference calls. The goal of this call was to discuss open accessibility issues, and to brainstorm and build consensus on appropriate solutions.

Present on the Call

<

ul>

The other day I posted to the accessibility group on g.d.o and was asked to solve a CAPTCHA. As a screen-reader user, posting in an accessibility forum, I was quite surprised.

Now, I was made a little less frustrated when I noticed that the CAPTCHA included an audio alternative. However, the audio is sufficiently unclear that it was a challenge for me to solve on the first attempt, and I cannot imagine the challenge it would be for someone who is hearing impaired.

In short, audio / visual CAPTCHAs, even when used together, are a poor accessibility practice.