Find 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#drupal-accessibility on IRC
In case we're interested in taking this into IRC, I registered #drupal-accessibility on freenode to chat around coding and accessibility issues and extensions in Drupal.
I'm going to set up logging on it this weekend.
Read moreAnybody out there who can help with JQuery to make Drupal 7 accessible?
Mike Gifford (mgifford) and Everett Zufelt are addressing a major accessibility issue for the administration interface of Drupal 7. If they had help from someone with JQuery skills, they could make significant progress. If you think you can help, check out http://drupal.org/node/467296.
Read moreFilter h1, h2, and h3 tags from allowed html in comments
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?
Suggested change to Find Content form
The 'Find Content' form has a prominent place in Drupal 7. However, the form poses accessibility challenges. The filter form is composed of radio buttons and dropdowns that visually correspond for sighted users but there is no indication they correspond for screen-reader users.
I've proposed a change to the Find Content filter form. I'm seeking feedback here and in issue #551034. I believe the change is a win-win for accessibility and usability.
Here is a screenshot of the proposed form:
Read moreD7 Accessibility Taskforce Meeting Agenda & Working Page (August 24, 2009)
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>
D7 Accessibility Taskforce Meeting Summary (August 10, 2009)
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>
First Glance Accessibility Evaluation of the d7ux Administration Theme
This morning I took a first look at the d7ux administration theme "Seven" from the perspective of a screen-reader user. Overall I found the theme enjoyable, but there is more work to be done to ensure that the theme is truly accessible.
You can read my blog post about the accessibility of Seven at http://openconcept.ca/blog/everett/first_glance_accessibility_evaluation...
Read moreD7 Accessibility Taskforce Meeting Summary (July 27, 2009)
On Monday, July 27, we had the first of three planned Drupal 7 accessibility taskforce conference calls. The goal of the call was for those interested in Drupal 7 accessibility to be introduced to each other, and to develop consensus on several fundamental issues surrounding Drupal 7 accessibility
Present on the Call
- Mike Gifford
- Everett Zufelt
- Katherine Lynch
- Brandon Bowersox
- William Lawrence
- Kathy Kahl
- Ann McMeekin
- Valeria Brigatti
- Owen Barton
Apologies
Read moreg.d.o CAPTCHA is poorly accessible
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.
Read more