E-mail List Archives
Re: Where does invisible link text fail WCAG2?
From: Patrick H. Lauke
Date: Jul 20, 2015 10:57AM
- Next message: MEJ - Beth Sullivan: "JAWS 14 issues with partial view reloads for Single Page Java web applications"
- Previous message: Lynn Holdsworth: "Re: Tiny clickable element: does this fail WCAG2?"
- Next message in Thread: chaals@yandex-team.ru: "Re: Where does invisible link text fail WCAG2?"
- Previous message in Thread: deborah.kaplan@suberic.net: "Re: Where does invisible link text fail WCAG2?"
- View all messages in this Thread
On 20/07/2015 17:18, Jared Smith wrote:
> These types of statements always cause me concern. If you can't find a
> WCAG failure would it not be documented as an issue? It's clearly an
> accessibility and usability issue and should be noted as such even if
> it isn't a WCAG failure.
Indeed (also relating to the other thread about tiny clickable
elements). In my reports, I often include an issue, explain that
*nominally* a tested page/site passes the letter of WCAG, but that
nonetheless there are things that should be fixed (same goes for, say,
still including a skip link, despite the use of landmark roles and
proper heading structure, to account for keyboard users without any
special AT).
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
- Next message: MEJ - Beth Sullivan: "JAWS 14 issues with partial view reloads for Single Page Java web applications"
- Previous message: Lynn Holdsworth: "Re: Tiny clickable element: does this fail WCAG2?"
- Next message in Thread: chaals@yandex-team.ru: "Re: Where does invisible link text fail WCAG2?"
- Previous message in Thread: deborah.kaplan@suberic.net: "Re: Where does invisible link text fail WCAG2?"
- View all messages in this Thread