Accessibility

Should Drupal be using the aria-label property on any form fields?

So far our FAPI accessibility efforts have focused on making sure there is always a Label attribute. We make sure the Label is connected to the form element by ID. And we allow module developers to choose the location of their label (before, after, hidden off-screen, etc.)

Hi folks.
I was wondering something.
Last night, when I had someone visit my website wich you all may review at:
http://keithnet.dyndns.org
I was told seriously that the font is not optimal for people with low vision.
As I have committed myself to insureing my site is optimized for low vision users as well as screen reader users, hear is what I need to know.
It should be noted that I'm using Druapl Core without modification, I.e. No eextra themes, etc.
What I'm using is the default Draupl core layout as designed after an installation witht he bartic theme.

Hi.

I have received this email from a coworker mailing list. I think it must be considered in order to avoid similar problems.

<

blockquote>
Hi,

Hello folks.
First of all, I do not know if you folks can even help me out, so I thought I'd ask here.
I don't have money to higher a full-time web designer, but I need as much assistance as I can get in designing accessible websites with Drupal7.x.
Everything from incorperating same page links, to tips that range from visually compeling stuff as well.
I'm also concerned with Drupal7 as far as how well W3C designs regardless of the HTMl standard in use passes the validation processes.
Any help would be much appreciated!

This wikipage aims to provide a list of Drupal websites with a certified accessiblity statement.

European Union

Accreditation body list: EuraCert

India

Accreditation body list: National Informatics Centre

http://web.guidelines.gov.in/compliance.php

The Design Initiative has three main goals - build a new core theme, build a new collaboration site for designers, and community outreach. The new core theme initiative is well under way and we're tantalizingly close to design.drupal.org becoming a reality. What we need to do now is step up a gear and start thinking about outreach.

Hi, I posted an issue in the OpenLayers queue to improve the accessibility of maps in Drupal. OpenLayers is widely used by governmental organisations and so it is useful to have a look at the acessibility.

We need to start thinking and talking about what approaches we're going to take in Drupal 8 with regards to design for mobile.

My own opinion is that we should probably be looking really closely at responsive design and how we might apply or adapt the patterns emerging in that field. The idea of "one web" and a unified design and user experience independent of device appeals to me. I don't want an impoverished mobile experience, so please don't assume what I want to see or do just because I'm on a tablet or handset.

Just learned about this new book in progress by Sarah Horton & Whitney Quesenbery:

http://rosenfeldmedia.com/books/web-accessibility/

Any experience how Drupal is able to meet this requirement for text parts in another language then the node language:
"3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA)" http://www.w3.org/TR/WCAG20/#meaning-other-lang-id

The recommended solution is to use the lang-attribute.

I want to validate a site built with Drupal 7 (with RDFa enabled), using a Genesis's HTML5 sub-theme & with lots of WAI-ARIA added for accessibility.

Looks like with - http://validator.nu - we can do HTML5 & ARIA.

But really not sure how to also evaluate for the RDFa as well.

The W3C doesn't seem to like it either although it can to XHTML & RDFA apparently - http://validator.w3.org

Some guidance on validation would be appreciated. I have heard that someones is maintaining a custom schema for HTML5 & RDFA, but not sure how to use it.

One of the sessions at the 26th Annual International Technology & Persons with Disabilities Conference was about Drupal.

Unfortunately, it doesn't look like they recorded the session (CSUN, Accessibility, and Drupal) but there's an interesting white paper. Is anybody here involved with this project?

Hi folks --

At Drupalcon I mentioned we are doing a full-scale usability and accessibility of our redesigned website (under development at http://www.drupal-dev.naric.com/drupal-7.0/) Attached is brief, preliminary review of our development site. The Paciello Group reviewed three templates and a handful of pages for us. I'm still going through and making changes based on their recommendations. Some are more challenging for me than others. CSS I can fix. PHP, not so much. For example:
-Accessibility of the Feedback module
-"more" link in the aggregator feed (needs context)

I am trying to sort through the most accessible way of structuring the navigation links and skip-links on a page. Consider a page with top-nav/header, content, and bottom-nav/footer. Since we can move things around with CSS, there are a a few ways of structuring the source order:

I have lurked for a little while, and this is my first post to this group. I have met some of you in person or virtually in other contexts, and appreciate your contributions to Drupal accessibility. In learning Drupal 7, myself, I have encountered some problems as a blind developer for which I have not yet found solutions (though I have done much reading of Drupal books and web articles). I hope some of you may have helpful thoughts on the following issues, divided into Blocks and Views; Content Types and Forms; and Status and Error Messages.

Proposed Agenda

1. Drupal 8 accessibility gate: Discuss our standards and process for 8 so we can finalize and propose to Dries. See http://groups.drupal.org/node/133034 .
2. Drupal 8 battle plans: Brief sharing of your personal battle plan, and strategizing together. If you put your personal battle plan in writing in advance, please share a link to it here.
3. Google Summer of Code: We are invited to submit accessibility project ideas, due before April 8. See http://groups.drupal.org/node/138009 .

Use Cases: How is the Accessible Helper module useful or intended to be useful?

These lists should translate to feature requests in the issue queue if they are not already part of the functionality

I dusted off the Drupal 7 version of the Accessible Helper module. Its been ages so I needed to get it working against Drupal 7.0.

Here is the release url: http://drupal.org/node/1094010
And the project is at: http://drupal.org/project/accessible

Accessible_Help Module

I was impressed to see the number of people at DrupalCon this year with a visible disability. I didn't get to speak with hardly any of them, but I do think it's worth while to look at measures that have been made to make our events more accessible. I'm hoping that London is able to learn from & improve the experiences of people attending. I don't know what feedback #DrupalChi was collecting from attenders, but...

BoF at DrupalCon Chicago 2011 3/10/2011 11:00am

Attendees:

Everett Zufelt (via Skype)
Mike Gifford
Jessica Chaiken
Kathy Kahl
Dan Mouyard
Jennifer Hodgdon
John Barclay
Brandon Bowersox

Topics

The group agreed on three topics for the BoF:

1. Gates and guidelines for D8
2. What we missed in D7 to fix for D8
3. Empowering themers and developers with documentation