Add alt attribute for locked icon on entries in style=light

[faithofone]

Title:
Add alt attribute for locked icon on entries in style=light

Area:
accessibility

Summary:
Right now there's no alt text for the icon that signifies an entry is locked when using style=light.

Description:
When viewing an individual entry while using "style=light", there is an icon over the title of the entry which signifies its security level, such as private, protected or custom.

In most styles, this icon has an alt text. When using "style=light", it does not.

This is an accessibility issue because this icon provides important information about the entry. On one's own entries this information is available at the top of the post in text form, but on an entry belonging to someone else, there is no textual representation of this data. An alt text would make it so that if for some reason (failure to load the image, images turned off, browsers that do not process images at all, etc.) the image is not displayed, the information the image represents is still accessible to the user.

In this instance, there are a lot of issues that could arise from someone mistaking a protected or filtered post for something that was publicly posted.

So my suggestion is to add the proper alt text so that the implementation of this icon on the individual entry pages matches the way it is used on the other pages (like the reading page, or the main journal page).

Poll #6496 Add alt attribute for locked icon on entries in style=light

Open to: Registered Users, detailed results viewable to: All, participants: 59

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
57 (96.6%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
2 (3.4%)

(Other: please comment)
0 (0.0%)

Comments

[denise]

We really don't want people filing reports directly with Bugzilla. It's for developers, not for the end user -- as you point out it's fairly foreboding-looking, the usability is horrid, and the workflow is not at all intuitive. Nor is it easy to find duplicates -- if we started asking people to file reports in Bugzilla, it would be overrun very quickly with multiple reports of the same thing (I reject at least 50% of things put in the suggestions moderation queue as duplicates or as things we've repeatedly said we won't/can't do), and the maintenance necessary to keep Bugzilla triaged is a great deal of time and effort that could much more easily be put elsewhere.

The proper place to report bugs is Support; I won't outright reject bug reports from Suggestions, though, since by the time I get to the queue the person has usually waited long enough, and rejecting the report and saying "please go let support know!" runs the risk of the bug report never being made. The line between "this isn't working as designed" (bug) and "this is working as designed, but as designed is stupid" (suggestion) isn't ever something a user should have to know; it can all come to suggestions and we'll handle it from there.

[feathertail]

Ah, okies, that makes sense.

[denise]

Heh, I just realized both of the comments I made about Bugzilla were to you! I wasn't trying to be too emphatic there, I just didn't notice :)

[feathertail]

S'okay! I was confused again. >.>