A user should be warned against using alternative text for images that is something like "image", "picture", "photo", or similarly generic meaningless names.
Likewise, a filename should not be accepted as acceptable "DC123.jpg" should not be allowed.
Guideline B.2.3: Assist authors with managing alternative content for non-text content.
B.2.3.2 Automating Repair of Text Alternatives: The authoring tool does not attempt to repair text alternatives for non-text content or the following are all true: (Level A)
(a) No Generic or Irrelevant Strings: Generic strings (e.g. "image") and irrelevant strings (e.g. the file name, file format) are not used as text alternatives; and...
Some examples
Comments
Comment #1
mgiffordComment #2
mgiffordComment #3
mgiffordComment #4
mgiffordComment #17
wim leersOhhhhh, this is really interesting!
This will require adding validation to things that have historically had zero validation. I think the easiest place to start is with the
imagefield. That will work for image fields, media fields and image media.It won't work yet for images uploaded using
EditorImageDialog(i.e. in the text editor).Comment #21
mgiffordI just forked another project here to illustrate kinda how it might work:
https://codepen.io/mgifford/pen/oNaObMj
Not that we have a very long list of issues words to avoid here.