Short description
The ability to provide alt texts for images like attachment:MacroMarket/Image.py is one of the main criterias in evaluating web accessibility. Missing alt text often result in judging a web site as badly accessible. The WCAG criterias also say that not only images but also embeded object need to have an alt text (this is done here by the NOEMBED tag instead of alt=""). For AccessibleMoin it is therefore crucial to implement the ability to set alt texts. Also coding guidelines for users are needed in the HelpContents which tell them how they can contribute to a more accessible wiki.
For a start: Here's a changed version of the EmbedObject macro which implements alt tags attachment:EmbedObject.py -- OliverSiemoneit DateTime(2007-02-04T23:05:18Z)
Please add a diff for me, thanks -- ReimarBauer DateTime(2007-02-05T16:41:24Z)
Here we go with the diff for moin1.6dev (moin-1-6-main-7c58e8af1a97)
inline:embedobject.diff
-- OliverSiemoneit DateTime(2007-02-05T23:54:18Z)
Concering accessiblity having alt texts with embedded objects is not an option but a must, i.e. you can't leave the alt simply away (like for example for some layout images). How to deal with that? Force providing alt tags with the calling paras, so that alt is not an optional para anymore?? Or leave it as it is and develop some coding guidelines on moinmaster and trust in the self-healing powers of wikis, i.e. faults done by someone will be cleared by others? Or have an built in accessibility checker?
-- OliverSiemoneit DateTime(2007-02-06T00:11:12Z)
To be w3c conform we do need an alt tag always. There was some discussion on ImageLink in the past not to use "" as default. So that was changed for the attachment name
-- ReimarBauer DateTime(2007-02-06T08:35:34Z)
Ah ok, I see. Two things:
It's a good idea to deal with that on the "coding level", however this does not suffice in my eyes and needs to be complemented by coding guide-lines on Moinmaster for an AccessibleMoin, e.g. "Image links are always some web element performing a certain action or function when you click on it. According to the WAI w3v guidelines funtional elements do always have an alt tag which explains e.g. to the blind what happens when clicking on it e.g. "Click here to download source code EmbedObject.py" "Return to FrontPage" "Click to enlarge image" and so on. By default this alt is set to the linked URL or attachment but this is only a fallback solution. Please do think also of visually impaired people and do always provide a sensible alt text and not just the URL or attachment name."
So you would plead concerning embed object to have not an empty alt="" but by default and alt="%s %s" % (_('Embeded'), mtype) e.g. "embeded application/x-shockwave-flash" complemented by some coding guidelines as described above? Or do you think turning alt in a "must" calling parameter rather than an optional parameter which would force an error when forgetting to provide an alt is also a solution? This could force people to think about an sensible alt maybe (problems: (1)backwards compatibility after Moin upgrading von non accessilbe to accessible (2) against idea of wikinature:too restrictive)...
-- OliverSiemoneit DateTime(2007-02-06T13:32:47Z)
see also ../EmbedObject, ../EmbedObjectExtensions
CategoryFeatureImplemented changeset 1876:e308a0e74069