- From: Ramón Corominas <rcorominas@technosite.es>
- Date: Mon, 13 Jan 2014 12:25:16 +0100
- CC: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Joshue wrote: > True, but that really is a user agent issue and as the use of > <figcaption> gains traction new screen readers could suppress/modify the > heuristic that will read the file name, in the presence of a populated > <figcaption> element. In any case, the screen reader should read the image first (that is, "graphic" followed by the <figcaption> content) and after that the <figcaption> again. Otherwise, the user would miss either the presence of the image or the presence of the <figcaption>. In the first case, the user will be unable to browse through images or to download them (to share them with friends, for example); in the second case, the user will not know that there is a visible caption that he/she can use to identify the images when taling with his/her sighted friends. Therefore, I cannot see the advantage of suppressing the @alt text. since the screen reader would repeat the text anyway (assuming that the @alt and the <figcaption> should really be the same). Regards, Ramón.
Received on Monday, 13 January 2014 11:26:40 UTC