- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Tue, 19 Jul 2016 10:41:45 -0400
- To: "White, Jason J" <jjwhite@ets.org>
- Cc: Gregg Vanderheiden <gregg@raisingthefloor.org>, David MacDonald <david100@sympatico.ca>, GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
Plus another one for Greg's comment. One can also use title or aria-describedby to qualify what the linked text "Read more" relates to ... that is not an accessible name. I do not think 2.4.4 needs any tinkering. What is needed, is to coax AT manufacturers to support sufficient techniques that will enable users to read sentence / para / list item / closest preceding heading so that they can determine context without moving focus away from the link. Regards, Sailesh Panchang On 7/19/16, White, Jason J <jjwhite@ets.org> wrote: > > > From: Gregg Vanderheiden [mailto:gregg@raisingthefloor.org] > Sent: Tuesday, July 19, 2016 9:44 AM > > this isnt a clarification but a change and would restrict the solutions > here. > > [Jason] +1 to Gregg’s comments. Since “accessible name” is a precise > technical term, it’s too narrow for this success criterion. > > ________________________________ > > 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. > > ________________________________ >
Received on Tuesday, 19 July 2016 14:42:13 UTC