Accessibility

Hello, this issue is not Drupal-specific, please excuse if it is misplaced. Today my wife met a programmer who has suffered a right hemisphere stroke resulting in permanent paralysis of his left arm. He expressed difficulty he was having vocationally due to his injury. Does anyone know of assistive hardware (or other resources) that I could point this person to? Thanks! -NP

Many people are familiar with the concept of "maintainers" of certain Drupal components or modules.

But does our community have any way to recognize the "architects" who help plan the next advancements?

For Drupal 8 we could use "architecting" in many areas:

• Form API changes to support fieldsets (eg dates), more label options, accessible form error messages
• Applying ARIA consistently throughout the interface
• Overlay
• Theme updates
• What else do you suggest?

Tuesday join us on the #drupal-accessibility IRC Group.

We'll review progress on D7 and coordinate our next steps.

In the past we've had detailed agendas, but lately the meeting has been more informal. Feel free to reply if you think there are specific topics you want to work on. Otherwise we'll meet up and chat about our current efforts.

mgifford suggested (thanks for the suggestion) I post here about the Readability module. It grades the readability of content using the five standard automated readability tests:

• Flesch Kincaid
• Gunning Fog Score
• Coleman Liau Index
• SMOG Index
• Automated Readability Index

Drupal's documentation needs a page (or set of pages) that explains how you go from installing Drupal to having an accessible website. This is not intended to explain what accessibility is — we'll have another page that does that. The idea is to give developers the quickest, shortest route possible to an accessible site.

If folks want to make an accessible Drupal site, what is the route that they should choose, starting with Drupal 7.

So let's start throwing some information together in this wiki. Don't worry about polish — that can come later.

I thought it was worth noting that there are several folks in the accessibility community who are taking notice of the work that is being done with improving Drupal's accessibility. I wanted to mention a couple that I just ran into today (even though they are in some cases months old).

The WebAxe podcast #82 mentions the work we're doing here, especially with Drupal 7.

Apologies in advance for this crossposting to 11 groups. I recently started an issue to help us get to know each other better: Add field for "Memberships in Associations, Societies, and Other Professional Organizations" to User Profile. The initial response was, "Don't see why not, but let's hear more support before we do." So this is an appeal to read the issue and consider giving it your support.

Hi,
I reciew this error info despite that I have installed Accessible content module and placed the quail directory as I should or..?

Accessible content module requires the Quail library. Please download and from http://code.google.com/p/quail-lib and place the "quail" directory in the accessible_content director

I downloaded the Quail-lib, expand the compressed file and got a directory quail-lib-0.3.8 containing a nother directory also named quail-lib-0.3.8 containing three directories: example, quail and tests, and also two files (readme.txt and Licens.txt)

This is a reaction to NonProfit's awesome and most useful post on modules pertaining to accessibility. Wiki pages don't have comments, so I thought we could track discussion here.

A list of modules that you can use to enhance the accessibility of your Drupal site. If you know of other Drupal modules that enhance accessibility, please add them to this list. There's an overview also here http://drupal.org/node/394252

This information is current as of 4th July 2016.

Join the #drupal-accessibility IRC Group now and meet with us on Tuesday, September 7th.

We'll review our progress on the #D7AX pledge, announce what is up for DrupalCon-Copenhagen, talk about our commits and the work that remains to be done for Drupal 7, and then develop our plans for Drupal 8.

For the latest agenda, read the full version of this item. To add an item to this agenda, either comment below or contact one of our group organizers — Cliff, mgifford, or brandonojc.

If you missed August's meeting, read the logs to find out what we got done then.

Join the #drupal-accessibility IRC Group now and join us on Tuesday, August 3rd.

The agenda will include:

• Agenda Review
• Accessibility statement status
• #D7AX pledge progress
• Drupal 7 remaining accessibility items
• Drag/Drop Accessibility Best Practice Documentation
• Drupal 8 approaches and collaboration
• Next Meeting

For most of the new D7 book that I'm working on I'll be using Bartik for screen shots. The theming chapter will include instructions on how to re-colour Bartik and Garland as well as give some good alternate themes. There will be little (if any) information on how to manipulate .tpl.php files. This is a pointy-clicky site building beginner book. (Yes, Front End Drupal will be updated for v7 next year.)

I'm in the mad dash to the finish on my new book, "Drupal: A User's Guide." I have an entire chapter dedicated to accessibility. I'm an author so I like to pretend it's a pretty awesome chapter (it helps me sleep at night). I could really use a second or fourth set of eyes on the content though. The book is D7 and the chapter includes information on WCAG 1/2, Section 508 compliance. If you have some time this weekend to review the chapter I would be very appreciative.

Just a thought that occurred while browsing around; the accessibility definition could be extended to include situational disability - e.g bright light, noisy, small screen etc. http://ow.ly/29Om5

Hey Folks,

I was just looking at evaluating the forum pages for accessibility:
http://drupal.org/node/821672

And noticed that there was no summary for the table here:
http://drupal7.dev.openconcept.ca/forum/1

I think that there should be a summary for this table as defined here:
http://www.dhs.state.il.us/IITAA/IITAAWebImplementationGuidelines.html#w...

But thought we should look & talk a bit more about where to insert these in core and how to approach it.

Any ideas.

Drupal Accessibility IRC chat, we're setting up another one for July.

Join the #drupal-accessibility IRC Group now and make sure to be there on Tuesday, July 6th

The agenda is still being formed but will likely include:

• Agenda Review
• Drupal's Accessibility Statement
• #D7AX pledge progress
• Remaining items for D7
• Approaches for D8, especially in collaboration with usability team
• Setting the time for the next meeting

We have a number of tools mentioned in various discussions on our site already, and I'm about to add another. So I thought I would put it in this wiki, where we can start linking to all these tools. It's also a workspace for refining our presentation of them until it's ready for prime time.

So given the interest and levels of participation in the May Drupal Accessibility IRC chat, we're setting up another one for June.

Join the #drupal-accessibility IRC Group now and make sure to be there on Tuesday, June 1st

The agenda is still being formed but will likely include:

• Drupal's Accessibility Statement
• #D7AX pledge progress
• Approaches for D8, especially in collaboration with usability team
• Remaining items for D7

Hey y'all. My Google Summer of Code proposal (see Drupal for All) has been accepted, so I will be working on improving the accessibility of Drupal 7 in a few areas this summer. Mainly I plan on making accessible sub-themes of the core themes, accessible content creation (through a wysywig editor), and making Views more accessible (or at least the output). I probably will not start the actual coding until the program officially begins (May 28).