E-mail List Archives
Re: screen readers: forcing focus on forms
From: Birkir R. Gunnarsson
Date: May 7, 2013 3:46PM
- Next message: Jennifer Sutton: "status of Twitter Bootstrap and accessibility"
- Previous message: Birkir R. Gunnarsson: "Re: Odd NVDA reading of role=contentinfo"
- Next message in Thread: None
- Previous message in Thread: Angela French: "Re: screen readers: forcing focus on forms"
- View all messages in this Thread
Hi
If there is an error detected in a form submition, I generally find
(as a screen reader user) that it does help to put the ocus inside the
problematic field when possible.
Screen reader users can jump to the first form element with the "e"
key, in most screen readers, all of them, as far as I konw, have
convenient navigation mechanisms to jump directly to edit fields.
Screen reader users rely most of all on consistency and
predictability, and it could be argued that moving the focus like this
may conflict with "change of content" WCAG, though not likely.
I think it is better to just leave the focus either at the top of the
page, or on an element at the beginning of a form, like the form
landmark div or similar.
On 5/7/13, Angela French < <EMAIL REMOVED> > wrote:
> Other than possibly failing "perceivable", does anyone else know of a
> WCAG2.0 guideline that this may be in conflict with?
>
>>
- Next message: Jennifer Sutton: "status of Twitter Bootstrap and accessibility"
- Previous message: Birkir R. Gunnarsson: "Re: Odd NVDA reading of role=contentinfo"
- Next message in Thread: None
- Previous message in Thread: Angela French: "Re: screen readers: forcing focus on forms"
- View all messages in this Thread