Evaluate D7 accessibility against WCAG 2.0

+1 Yes, we should certainly review the new site for WCAG 2.0. In the future we should include WCAG compliance in the specifications when we contract out any work.

Congratulations on getting this launched. It represents a lot of hard work. If there's any time or budget left for revisions and follow-up, meeting WCAG 2.0 should be high on the list.

Hi Everett, thanks for posting this. We are committed to making the Drupal.org site accessible. We're filing issues in the redesign queue for now. I recommend adding a specific tag like 'drupal.org redesign accessibility' so there a queue we can work on.

Kieran

1st, the design looks so much better visually. Other than the having major headings like Download & Extend where I would expect to find the project heading (I already know I I'm in the project section), I've been very happy with how it looks, works & indeed how the migration happened. But that's only in my experience looking at and using the code.

We do need to look at a better system for evaluating core (at this point for D8), as well as Drupal association websites to ensure that we can have the widest participation possible in this great community. I would like to see RFP's for design include an accessibility element to them. I've got no idea how the design/theming was done, but it's a good practice and it should be addressed like we want usability testing to be done.

There's a wiki we're working on here to look at defining what the best practices are:
http://groups.drupal.org/node/94484

At some point we'll have to do the jump to D7 which will help considerably. However, there's lots we can do with D6.

Preliminary QA results for Accessibility using Wave:

1) Sitewide: Drupal Logo to Have Alt text
2) Getstarted: Alt tag not provided for the Books image. The Books image is the only content with the hyperlink.
3) Member Directory, Drupal Core, Individual Module Page, Dashboard Page, Search Result Page, Security Overview Page: Form Label Missing: Search Box
4) Logged in User Node Page:

• alt text missing in Content: this we will have no control on, this is Body content
• Comment reply link: Problematic link text
• Comment Form: Orphaned Field Label

5) Member Directory Page: Orphaned Form Label: Mailing List, not associated with any form type for the Username Label above the search box on the right side bar
6) Mail lists: Orphaned Form Label: Mailing List, not associated with any form type for Mail lists select Label

All accessibility issues should be tagged 'drupal.org redesign' and 'accessibility,' putting them in this listing, http://drupal.org/project/issues/search?text=&projects=&assigned=&submitted=&participant=&status[]=Open&issue_tags_op=and&issue_tags=drupal.org+redesign,+accessibility.

For the specific points from #5:

1) The Drupal logo is regular text, using CSS to replace with a background image, <div id="site-name"><a href="http://drupal.org" title="Drupal">Drupal</a></div>. As far as I know, this is fully accessible.
2) Confirmed the image under Books at http://drupal.org/start is missing an alt attribute. Needs an issue filed.
3, 5 & 6) Can probably start each as one issue, everything needs URLs and specific details.
4) Probably not a whole lot to do here. The comment link text and form are direct from Drupal core. Knowing specifics would help.

Specific Accessibility issues filed.

With reference to #5:

2) Get started Issue filed at http://drupal.org/node/958692
6) Mailing Lists Issue filed at http://drupal.org/node/958694
5) Member Directory Issue filed at http://drupal.org/node/958696
3) Form label for Search Box on Module Issue block at http://drupal.org/node/958700 and
Member directory: User search Form Label missing at: http://drupal.org/node/958696#comment-3650220
Search Page Form Label missing at: http://drupal.org/node/958704

Will detail 4) further.

Thanks! Glad to see these issues being identified & hopefully soon fixed.

The Main Colours that fail while using the Juicy Studio toolbar's Colour Contrast Analyser on Drupal.org HOME PAGE are at: http://drupal.org/node/946344#comment-3654420

Closing this issue down, as part of closing down the Redesign project, and looks like there's already duplicate issues.

Just renaming to avoid confusion.