RE: Should 2.4.4 require Link text or ACCNAME, rather than enclosing sentence etc...

Ø  Wouldn’t the effort to make link text clear in context (where that context is such that it can be programmatically determined) usually help most users? I think we are in agreement about what I suggested in my last contribution, though – that point 2 doesn’t create a guarantee

Right, from a cognitive standpoint I don’t think we can assume it is obvious that it is in context.  From a programmatic standpoint I don’t think we know the user has access to assistive technology.  In short I’m glad the COGA is taking another look at this and hopefully it can be tightened up to make the contextual aspect assist more users.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>
703.637.8957 (Office)
Visit us online: Website<http://www.ssbbartgroup.com/> | Twitter<https://twitter.com/SSBBARTGroup> | Facebook<https://www.facebook.com/ssbbartgroup> | Linkedin<https://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog/>
Check out our Digital Accessibility Webinars!<http://www.ssbbartgroup.com/webinars/>

From: White, Jason J [mailto:jjwhite@ets.org]
Sent: Monday, July 11, 2016 1:02 PM
To: Jonathan Avila; WCAG
Subject: RE: Should 2.4.4 require Link text or ACCNAME, rather than enclosing sentence etc...



From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com]
Sent: Monday, July 11, 2016 12:54 PM
Jason, I agree with your reading -- this was my area of concern – if point 2 can be used then it doesn’t help users with cognitive disabilities that aren’t using AT and doesn’t help users with motor impairment.  The benefits espoused only help in your point #1 – that isn’t clear in the understanding documents.
[Jason] I’m not sure that we are in agreement about point 2. In principle, yes, there could be a context of a link which can be programmatically determined but which is not visually obvious, but it seems to me that this is an exceptional case rather than a normal case. Wouldn’t the effort to make link text clear in context (where that context is such that it can be programmatically determined) usually help most users? I think we are in agreement about what I suggested in my last contribution, though – that point 2 doesn’t create a guarantee. The exceptional cases are allowed, even if they’re rare in practice.


________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________