All you WCAG nuts this is the place for you: how to make Drupal more accessible. Hints, tips, discussion and patch proposals.
Tables should have summaries and captions and table headers and table cells should be marked (as you teach me) with correspondent "headers" and "id" values.
I added some simple Php functions to block-admin-display-form.tpl.php and the output seems to be complete.Read more
Call for Proposals: Drupal 6 Theme Accessibility Redesign
We are currently conducting an accessibility review of our Drupal 6.0/CiviCRM install (http://training.dyslexiaaction.org.uk). We are seeking a Drupal accessibility and theming specialist to implement the recommendations from the review.Read more
I started developing an accessible template for Drupal which I called "Visioni".
The work in progress is at the address
the compressed file of the template at the address
I an not new to Web Accessibility: I released an accessible template for Wordpress, one for Joomla 1.5 and one for PhpBB.
I would be enormously glad to keep on developing it with this community.
I propose to increase the accessibility (as well as SEO) of the sites using Drupal by supporting the HTML link Element which defines the document relationship. As this element is placed within the HTML head, it isn't directly seen by the user, however the browsers as well as assistive technologies may use this information in order to provide better navigation e.g. by offering a dedicated navigation bar.Read more
How many aspects of Drupal conform with the W3C's Authoring Tool Accessibility Guidelines (ATAG 2.0)?
If we can write each of those aspects up, we can help the Authoring Tool Accessibility Working Group (AUWG) of the W3C's Web Accessibility Initiative improve two important documents.
And while we're doing that, we can make it easier for Drupal themers and developers to understand what they can do—or, in some cases, must do—to ensure that Drupal remains accessible and continues to help people who use it create websites that are themselves accessible.
This post is not yet complete. Check back in a few hours. Or perhaps even tomorrow.Read more
I'm very much a newbie to drupal 7, so forgive what may be a rather inane question. I should also point out at the start of this post that I'm a blind drupal user and most of my work is carried out on the mac.
Ok I'll be as brief as possible. I had an old, perfectly functional and adequate d6 site. The structure was based around a very very simple menu which had 4 top-level menu items. When I activated one of them (say the link called "teaching") all of the courses I taught expanded out as submenu items.Read more
Anyone interested in contributing to Drupal Accessibility is invited:
Tuesday, October 11, 2011
4pm GMT/11am CDT
on Skype (contact m.gifford or brandonbowersox on Skype to be added to the group if this is your first time joining)
Please respond with suggested topics
The call is a voice conference call on Skype. We'll be asking for a volunteer to post notes to the g.d.o. group so that people who could not attend can still review the notes and post comments. We will try to limit the main agenda to one hour.Read more
I'm pretty new at working with the Drupal API. Developing on D6, I've noticed that the core theme_image() function will output an empty title attribute value if none is supplied, e.g.
<img src="myimage.png" alt="my image description" title="" />
(In the case of @alt, blank is actually a good default BTW.)
I could see this being a problem if the image is hyperlinked, where the link itself uses a title attribute, e.g.
A lot of time and effort went into improving the accessibility of Drupal 7. We all deserve a round of applause for the work we did, we truly have a product to be proud of.
Our work is not complete.
Work on Drupal Core accessibility has slowed to a trickle, or perhaps an occasional drop (pun intended). We need to begin to rally the troops to pick up from where we left off at the end of the Drupal 7 development cycle, so that Drupal 8 can be an extremely accessible CMS out-of-the-box, one that would make ponies, kittens, and unicorns smile!Read more
Web developers and designers, are you accessible? Attend the 2nd annual online, LIVE Accessibility Summit! Get your tickets now at http://environmentsforhumans.com/2011/accessibility-summit/Read more
During the accessibility BoF at Drupalcon London several people showed interest in resuming the monthly conference calls that we have had in the past.
I would be happy to participate in these calls, and think we should get started. There are several initiatives that require some attention, primarily:
- html5 accessibility (including WAI-ARIA in Core)
- WYSIWYG in Core
- Further triage and patches for open accessibility issues
I'm hoping that someone will volunteer to organize these calls so that we can:Read more
Just a quick post to let everyone know that @DrupalA11y is now on Twitter.
The account is setup to automatically post from the feeds of this group, and from the Drupal Core issue queue for issues tagged "accessibility".
If you have any suggestions for a Twitter profile bio for the account please let me know.Read more
On the Friday of Drupalcon London we ran a Mobile Usability Testing Session on Drupal's admin interface.
We had a strong turnout, with lots of enthusiasm from the testers. We managed to test the UI on the following devices:
- Nokia N900
- Sony Ericsson Xperia Arc
- HTC Sensation
- Samsung galaxy s2
- iPad 2
- iPhone 4
- iPhone 3GS
- iPhone 3G
Here are some of the thoughts I came away with after the session.Read more
Is there a module that would or could prevent content providers from creating links consisting solely of "click here" or "here" (for link accessibility) or even preventing those words from appearing in a link at all (for link conciseness)?Read more
When publishing a calendar or an overview of news items, the dates are often in a short custom format, like '12 Sep', or '2/7'. From an accessibility point of view, should a theme or view also provide the full date format?
With abbreviated months should we use the abbr tag for the month? like:
<abbr title="August">Aug.</abbr> (http://www.littlewebhut.com/html/abbr_tag/)
Demotix.com is about to undergo a redesign. We are looking for someone to help us make the UX better. We have designers and coders but we need someone like you to make the UX a joy. We hope to do this by talking to you about our ideas and have you then take a look at our wireframes before we have our designer make them look nice. (we are also open to other workflows)
We want to talk to you on Tuesday 30th of August with a view to start shortly after. Contact email@example.com with your details and examples of why your great at UX.Read more
This is Todd at the University of Iowa.
We're just scratching the surface of Drupal here--three or four departments are letting our central web group pilot. We have a couple of really sharp developers and a deep commitment to accessibility. What we're missing is a good understanding of our options for integrating the two. Some things I'd very much like to know--an incomplete list:
How to add uncommon attributes to HTML tags (e.g., scope="col" to a
Setting divs and other regions as ARIA landmarks (aria-live, aria-required)Read more
We have planned a meeting on accessibility in D8 on Tuesday 14:15 BST during DrupalCon London. In looking ahead to building Drupal 8 we want to talk about how we can best approach AA compliance of the Web Content Accessibility Guidelines (WCAG) 2.0. Implementing the accessibility gate in a way that is understandable by Drupal developers, providing useful examples to make it easier for them to grapple with the challenges of accessibility.Read more
Has anyone ever tried implementing this in Drupal?
Specifically, I'm looking at adding an error message to the page title:
It is also best practice to include an error notification in the page title (title element) since a screen reader user is likely to believe the page was submitted correctly and continue to navigate to another page as soon as the new page is returned instead of reading the main content area of the page again.
I saw a demo of the Views 3.0 module today at Berkeley Drupal Users Group (BDUG) today. The presenter noted that if a page that is part of a tabbed-pages view differs from the default of the view, the differing options are displayed in the Views UI as italics. I haven't seen the view source of the page, so it may well be empasis tags.
But the larger issue, is marking content with italics or emphasis to distinguish that it has a certain quality, e.g., not a default value, considered sufficient for accessibility, without some other indication that would be read out, e.g., an asterisk?Read more