Last modified: 2014-05-29 20:32:59 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T54267, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 52267 - Don't use filename as alt attribute
Don't use filename as alt attribute
Status: NEW
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.22.0
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
: accessibility
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-30 09:25 UTC by Michael M.
Modified: 2014-05-29 20:32 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Michael M. 2013-07-30 09:25:41 UTC
Example wiki text:

[[File:Example.jpg|50px]]
[[File:Example.jpg|thumb]]
[[File:Example.jpg|50px|link=foo]]

This currently sets the alt attribute for all images to "Example.jpg", which shouldn't be done (http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/F30).

IMHO an empty alt attribute for the first two, and an alt="foo" for the last makes much more sense.
Comment 1 Derk-Jan Hartman 2013-07-31 18:52:21 UTC
We have had many discussion about this in the past. I think in the past we concluded that it was better to set the alt this way (also because we actually have quite descriptive filenames quite often). I also remember some discourse on that though.

It definitely should NOT be empty alt. Part of the reasoning was if I remember correctly, that alt='' means an active acknowledgment of the fact that it is an image does not even require an alt text. Which is not the case for these 'auto generated' alts. At most we should then simply not define an alt at all.

Anyway, there should be a couple of closed tickets discussing this very topic, and a slew of en.wp discussion somewhere on this.
Comment 2 C. Scott Ananian 2014-05-29 20:32:59 UTC
See bug 24586 comment 3, etc.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links