E-mail List Archives
Re: WCAG2: Form fields and labels
From: Patrick H. Lauke
Date: Feb 5, 2015 6:41AM
- Next message: Andrew Kirkpatrick: "Re: WCAG2: Form fields and labels"
- Previous message: Birkir R. Gunnarsson: "Re: WCAG2: Form fields and labels"
- Next message in Thread: Andrew Kirkpatrick: "Re: WCAG2: Form fields and labels"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: WCAG2: Form fields and labels"
- View all messages in this Thread
On 05/02/2015 13:19, Lynn Holdsworth wrote:
> What exactly does WCAG mean by "programmatically"? I always assumed
> that it meant that a browser's accessibility layer could pick up, for
> example, this field/label association, so that AT wouldn't need to use
> heuristics to guess from positioning or other factors. But I discussed
> this with a more knowledgeable friend yesterday, who felt that
> positioning in this scenario would have been a sufficient technique.
I would disagree with your friend here. Programmatically to me means "is
exposed correctly in the accessibility API by the browser", which
generally means "no AT-specific heuristics". In fact, if you rely purely
on AT heuristics, you're going to have a bad time...as heuristics can
and will differ between different ATs (and even different
versions/combinations of browser/OS of the same 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: Andrew Kirkpatrick: "Re: WCAG2: Form fields and labels"
- Previous message: Birkir R. Gunnarsson: "Re: WCAG2: Form fields and labels"
- Next message in Thread: Andrew Kirkpatrick: "Re: WCAG2: Form fields and labels"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: WCAG2: Form fields and labels"
- View all messages in this Thread