accessibility

Hi

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.

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/

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:

1. html5 accessibility (including WAI-ARIA in Core)
2. WYSIWYG in Core
3. Further triage and patches for open accessibility issues
4. ...

I'm hoping that someone will volunteer to organize these calls so that we can:

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)?

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)

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?

Often a single organization will have multiple staff creating content. The staff member who is most concious of accessibility requirements will often discover content that other staff members have added that are not as accessible as they might be, if only because certain checks cannot be automated. It would be good if Drupal modules provided productivity tools for these individuals who have oversight whether by responsibility or default.

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 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.

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.