This didn't really hit home until I tried to write a section about this screen for the Lullabook.
Putting this screen into text is impossible without either mentioning:
a) the colour (which goes out the window entirely depending on the theme, and is useless to someone by a screen reader), or
b) the icons (which are lacking alt/title attributes and thus not visible at all if images are disabled or if viewed by a screen-reader)
The message itself on each row (esp rows that need updating) also varies depending on what's actually wrong. Looking at the defines in update.module, it looks like there are something like 10 possible statuses that could be displayed here.
I'd advocate at least one (preferably both) of the following:
a) Put alt/title attributes on the icons, at the very least. That way I could mouseover them to figure out what "class" of error I'm seeing (info, warning, error).
b) Put "Error: " or "Warning: " in front of the status if it's not a-ok. For example, "Warning: No available releases found", "Error: Update available", and "Error: Security update required!"
c) Any other bright ideas one might have.
Comment | File | Size | Author |
---|---|---|---|
#4 | update_status-accessibility_1.patch | 1.35 KB | dww |
#1 | update_status-accessibility.patch | 1.3 KB | webernet |
Comments
Comment #1
webernet CreditAttribution: webernet commentedAttached patch adds alt/title attributes to the images.
I'm not sure about adding the "Error:" or "Warning:" prefixes, as the explanations themselves are already pretty self explanatory.
Untested.
Comment #2
webchickThe statuses are self-explanatory, but not their "class." At least imo. People who can't see the colours are missing a lot compared to people who can.
Comment #3
dwwIf you use the lowercase versions, at least 'error' and 'warning' won't break the string freeze:
modules/dblog/dblog.admin.inc:
Comment #4
dwwLike so.
Comment #5
dwwI did test this and the alt attributes work... I don't know if changing the wording of the messages themselves is going to fly, since that's obviously (and visibly) going to break the string freeze. So, I'm calling this CNR for now. The string freeze (again) really ties our hands here for a better fix. *shrug*
Comment #6
webchickCan confirm that this does indeed address the problem at least to the extent that we can prior to D7.
Thanks, Derek and webernet!
Comment #7
Gábor HojtsyOh, well, committed.
Comment #8
dwwThanks. Backported to update_status 5.x-2.* in contrib: http://drupal.org/cvs?commit=99140.
Comment #9
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.