W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2012

Re: Invisible elements for additional link text [SEC=UNOFFICIAL]

From: Ramón Corominas <listas@ramoncorominas.com>
Date: Thu, 13 Sep 2012 11:08:39 +0200
Message-ID: <5051A297.50303@ramoncorominas.com>
To: Vivienne CONWAY <v.conway@ecu.edu.au>
CC: "ANDERSEN, Leon" <Leon.Andersen@fahcsia.gov.au>, 'Christian Biggins' <cbiggins@gmail.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Hi, Vivienne and all.

I'm not sure that the technique about "same paragraph" is really a 
"sufficient" technique for SC 2.4.4 in most real-world scenarios.

Although the paragraph's text *can* be "programmatically determined", no 
current screen reader *does* determine it and presents it to the user, 
so I would say this technique is not "accessibility supported". Thus, 
IMO an ambiguous "read more" link fails Conformance Requirement #4, 
because the user always have to perform additional actions (and realize 
what to do) to find the contextual information.

In addition, the "hidden portion of a text link" technique is also a 
documented WCAG 2.0 sufficient technique (C7) that has wide 
accessibility support (even with Dragon).

As suggested, I would also recommend to show the complete text when the 
link gets focus/hover (for example, using a tooltip-like style). This 
way, sighted keyboard and magnifier users will have the information even 
if the context is not visible because of a high magnification level.


Vivienne wrote:

> One other thing to note is that while 'read more' etc within context passes 2.4.4 for link text in context, it does not pass 2.4.9 (AAA) which requires that the link text makes sense whether in context or not.  Meeting this requirement would make it easier for someone with a screen reader (and other also).
Received on Thursday, 13 September 2012 09:12:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:41 UTC