This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
public-html-comments posting from: Reinaldo Ferraz <reinaldo@nic.br> http://www.w3.org/mid/4DE6932D.7060708@nic.br Dear Srs. Follow my contributions to the document *HTML5: Techniques for providing useful text alternatives* Best Regards Reinaldo Ferraz -------------------------------------------------- *Examples of scenarios where users benefit from text alternatives for images* Add: - They have problems to load images or the source of image is wrong -------------------------------------------------- Question: In the *Example 2.5*, is it possible to use Image maps <map></map> to create alternatives and to put ALT inside of each <area> tag? -------------------------------------------------- Removing the link *Providing a text alternative that is not null. (e.g., alt="spacer" or alt="image") for images that should be ignored by assistive technology [WCAG20-TECHS]*. In that way, it would made users confused about the meaning (if the user doesnt click on the link) In the *Example 6.4*, I consider important a short description to the image. It´s important even for a blind person or somebody who cannot load images perceive that there is an image with a purpose: create a medieval atmosphere to the webpage. I disagree that the image with description is only related to the blind or low vision webpage. The link example shows the users preference http://webaim.org/projects/screenreadersurvey/#images -------------------------------------------------- I belive that *3.11 A group of images that form a single larger picture with and without links* is not necessary. the same situation is been using at the examples *Example 1.1* and *Example 1.2*
mass-move component to LC1
Hi Reinald, >Add: >- They have problems to load images or the source of image is wrong Words to this effect have been added. >Question: In the *Example 2.5*, is it possible to use Image maps ><map></map> to create alternatives and to put ALT inside of each <area> tag? responded in a seperate bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=12874 >Removing the link *Providing a text alternative that is not null. (e.g., >alt="spacer" or alt="image") for images that should be ignored by >assistive technology [WCAG20-TECHS]*. In that way, it would made users >confused about the meaning (if the user doesnt click on the link) I have left the link in as I don't understand why its inclusion is confusing. If you would like to explain further please reopen the bug. >I belive that *3.11 A group of images that form a single larger picture >with and without links* is not necessary. the same situation is been >using at the examples *Example 1.1* and *Example 1.2* responded in a seperate bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=12877 >In the *Example 6.4*, I consider important a short description to the >image. It´s important even for a blind person or somebody who cannot >load images perceive that there is an image with a purpose: create a >medieval atmosphere to the webpage. I disagree that the image with >description is only related to the blind or low vision webpage. The link >example shows the users preference >http://webaim.org/projects/screenreadersurvey/#images I have modified the spec text in Example 6.4 Please review http://dev.w3.org/html5/alt-techniques/Overview.html#sec6 I have not made it mandatory to provide an non null alt as there are some circumstances where it is appropriate, but do encourage authors to provide a text alternative. EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: partially accepted Change Description: spec modified Rationale:see above.