- From: Makoto UEKI - Infoaxia, Inc. <makoto.ueki@gmail.com>
- Date: Fri, 27 Jan 2012 11:57:16 +0900
- To: Loretta Guarino Reid <lorettaguarino@google.com>
- Cc: public-comments-wcag20@w3.org
Thank you very much for your response. > An approach like H2 would definitely be best practice for this situation, to > avoid redundant links for blind or other keyboard users. Note that H2 is not > required, that is, it is not a failure if the author does not use H2. H2 is > an advisory technique for SC 2.4.4 and 2.4.9, and it is sufficient for SC > 1.1.1 because the text provides the text alternative for the image. Do you mean that the following case would meet SC 1.1.1, 2.4.4 and 2.4.9? CASE 1: <p> <a href="xxx.html><img src="xxx.png" alt="WCAG 2.0"></a> <a href="xxx.html>WCAG 2.0</a> </p> CASE 2: <p> <a href="xxx.html><img src="xxx.png" alt=""></a> <a href="xxx.html>WCAG 2.0</a> </p> CASE 3: <p> <a href="xxx.html><img src="xxx01.png" alt="WCAG 2.0"></a> <a href="xxx.html><img src="xxx02.png" alt="WCAG 2.0"></a> </p> CASE 4: <p> <a href="xxx.html><img src="xxx01.png" alt="WCAG 2.0"></a> <a href="xxx.html><img src="xxx02.png" alt=""></a> </p> - Makoto 2012/1/27 Loretta Guarino Reid <lorettaguarino@google.com>: > On Sun, Jan 22, 2012 at 12:11 AM, <noreply@w3.org> wrote: >> >> >> Name: Makoto Ueki >> Email: makoto.ueki@gmail.com >> Affiliation: WAIC (Japan) / Infoaxia, Inc. >> Document: TD >> Item Number: H2 >> Part of Item: Applicability >> Comment Type: general comment >> Summary of Issue: adjacent multiple image links >> Comment (Including rationale for any proposed change): >> H2 title reads "Combining adjacent image and text links for the same >> resource". There can be a case that there are two a elements with img >> element which have the same href attribute and the same description, and >> they are adjacent. For example, One has image of text and the other is >> iconic photo. >> >> Proposed Change: >> Will H2 also be applied to this case? In other words, do authors have to >> put those images together in one link? >> >> WAIC needs to clarify this in order JIS to harmonize with WCAG. >> > ================================ > Response from the Working Group > ================================ > An approach like H2 would definitely be best practice for this situation, to > avoid redundant links for blind or other keyboard users. Note that H2 is not > required, that is, it is not a failure if the author does not use H2. H2 is > an advisory technique for SC 2.4.4 and 2.4.9, and it is sufficient for SC > 1.1.1 because the text provides the text alternative for the image. > Combining such image links into a single link is recommended but also just > advisory for WCAG. We have not made any change to the techniques because > advisory techniques are low priority to maintain, but hopefully this > guidance helps you coordinate with JIS. > > Loretta Guarino Reid, WCAG WG Co-Chair > Gregg Vanderheiden, WCAG WG Co-Chair > Michael Cooper, WCAG WG Staff Contact > > > On behalf of the WCAG Working Group
Received on Friday, 27 January 2012 02:57:43 UTC