Adding Strings for Translation for Accessibility

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
mgifford's picture

There are a number of places where for accessibility in D7 we still need to add strings to fields in core. There are still quite a few missing labels for fields in and this is very important so that individuals using screen readers have an opportunity to understand what the field represents. We want to do this however in a way which doesn't loading a tonne more work on translators.

There will be more fields discovered without labels in D7 and hopefully we'll be able to bring them in as small bugs in point releases however, this would mean more work for translation. We hopefully will be able to re-use strings more than we have done in the past and produce more generic descriptions. In D8 this will need to have more meaning associated with them, but for D7 we may not be able to perfect how this is implemented.

Following a discussion with @webchick on #drupal-contribute I'm starting up a discussion here between the translation folks and accessibility folks to see what type of compromise we can arrive at. I believe almost all of the label changes will be visible only to screen readers, that being said it will add more to the work load for translation.

To quote @webchick "I'm not saying that the accessibility teams and i18n teams can't get together and decide that that's ok. I'm saying that unilaterally saying "Well these strings don't show up in the UI so who cares" isn't going to work. you need buy-in from them"

Translations

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: