wcag

Overview: I propose to increase the accessibility of important Drupal interfaces for people with various impairments. Specifically, I want to modify Drupal 7's core themes, the WYSIWYG module's TinyMCE configuration options, and View's interface and output to be more accessible.

Anybody going?

Paper submissions - deadline today...

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?

Hi,

I'm a multimedia developer (I can do a bit of everything but always have to learn more to complete a task), I have experience in developing HTML, CSS, Javascript, Actionscript 2 moving to 3 now and a very brief understanding of PHP.

I've recently started learning how to implement Drupal as I have undertaken the development of a website for a public body that requires a CMS and they legally need the site to comply to WCAG Double A standards for site users but not contributors or adminstrators.

So I was reading Practical Accessibility Tips with WCAG 2.0

Always Use Explicit Labels is in 7 core now and has been backported ot 6.

The use the tabindex attribute is also quite scarce. Think it only shows up in the user.module as an attribute added to the form:

Right now we're indicating Required Fields using:

I would really like to understand this issue better - http://drupal.org/node/58941

As Webchick says "If 1/50th of the people complaining that this isn't fixed yet actually put some energy into reading the copious documentation cross-linked here and creating said patch, this probably would've made it into Drupal 4.7."

So, I'd like some other opinions about the difference between:

I followed up on a bug report about accessibility issues and radio buttons. Created the patch and had it approved by the test bot and others that reviewed the code.

However I'm requesting support from the accessibility community to see if we can't bring it into Drupal 7 core.

Form labels for radio & checkbox(s) are not properly done with Drupal at the moment and don't follow WCAG 2.0 Guidelines.

We've been discussing the need for unique strings of text for unique links in the new WCAG 2.0 standards. But Cliff brought up that there are some SEO issues involved in this as well. So how do we get more meaningful links coming from our list/view pages so that instead of having 100 links pointing to your page say "Read more" and we have more using a related string, like "Accessible Themes for Drupal".

In a recent WCAG 2.0 presentation I was attending it was stressed that websites should not be using the same text to link to different URL's. So, with a generic Drupal blog when the teaser node produces 10 or so "Read more", "Add new comment" or "Send to friend" links, each going to unique URLs for the corresponding post it becomes very difficult for screen readers to navigate.

In an accessibility blog post I wrote about quick accessibility enhancements, I described an easy way to make the Read more link more descriptive. I believe it's also got some both SEO & click through advantages too.