hey there,

I miss some accessibility support in CCK.

for example, when you have an image field, it can have a TITLE and an ALT text, but no LONGDESC or LANG attributes as of now.

the LANG attribute could also benefit from i18n.

it'd be good to have it as a module, though I think it should go into CCK core for obvious reasons.

whattya think?

cheers,
Luciano

Comments

yched’s picture

yched commented
Status: Active » Postponed (maintainer needs more info)

CCK doesn't handle image fields. See imagefield module.

Don't know for sure what you mean with LANG. In D6, nodes as a whole have a language, you can use that one.

luco’s picture

luco commented

sorry.

I meant to use images as an example since they're the tag which is most prone to accessibility issues.

but it could be anything: a table, to use another example.

a blind person accesing a page with a table, via JAWS or Lynx, would hear every term in every cell of every column. now imagine a complex table with IRS tax values, for example, which must be accessible.

that's not very user-friendly. which is why we use the DESC attribute: to summarise long pieces of information and allow the user to tab through.

as for the lang, it's another accessibility-facilitating attribute. picture this: you have a pie chart image with a description like "this pie chart demonstrates a balance of 50% between men and women who vote". now imagine a French, blind person accessing this. she won't get the description at all because even though it's written in English, it will most likely be read in French, resulting in a messed-up message.

see what I mean? oh and such issues are not only a barrier but, in the near future, they will become entirely illegal - they're partially already. so why wait to support the disabled?

cheers,
Luciano

quicksketch’s picture

quicksketch
he/him
commented
Category: feature » support
Status: Postponed (maintainer needs more info) » Fixed

Hi Luciano, I'd suggest making individual requests for specific things that could be improved. There's a great thread over in the ImageField queue on the examples you described: #193887: Accessibility enhancements.

Drupal is a great platform for accessibility (at least compared to the competition, though maybe that's not saying much). Here are a few others that might serve as good examples:

#780434: Improve accessibility of multi-value fields
#638526: Accessibility of the upload

Individual requests are much easier to act upon than a general fix-everything request, especially since many developers don't even know where to begin with such work. You can think of it as a train-the-developer sort of exercise. :-)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.