WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Examples, Context Changing, OnFocus and OnInput

for

From: Birkir R. Gunnarsson
Date: Oct 28, 2016 2:25PM

Jim

You're right.
If you are arrowing through a dropdown (select) or selecting a
radiobutton, the content can be updated on the page, if it remains
discoverable (comes after the control you are interacting with).
That's dynamic content display, which is actually good for users
because it limits the amount of unnecessary info on the page.
Bad behavior (one that triggers a violation for that success
criterion) is when selecting from a dropdown (pushing arrow down)
automatically refreshes the whole page, directs you to a different
page, or jumps your focus to a different spot on the page
automatically.
That is the unexpected behavior and significant change of content (or
whatever that exact phrase is).
I have to put my examples out on a11yideas to demonstrate, they've
been sitting on my laptop for months.
The problem with changing content on input (3.2.1) is that the auto
jumping (which may be ok if users are warned of it beforehand and if
it does not prevent the user from correcting mistakes, I have actually
seen a situation where I try to shift-tab into a field of 2
digits,with 2 digits, and JavaScript auto jumped my focus away again,
so I was not able to delete and fix a wrong entry in that box).
Another problem with displaying focusable content in response to the
user entering info is that some browsers don't insert the new content
intot he focus order until the user has moved focus away from the
field.
Imagine you get two extra form fields if the amount you type is over 10,000
If you type 12,000 and press the tab key, your focus jumps past the 2
new components to the third, then you have to shift-tab to find the
two new components.dynamically displayed.
This used to always happen in Firefox, it may still do that, and it
makes it very hard for screen reader users to discover the 2 new
fields.
Cheers



On 10/28/16, Jim Homme < <EMAIL REMOVED> > wrote:
> Hi,
> Every once in a while I get confused about this, because, for example,
> moving from one list item to another in a list box is the classic example I
> keep seeing where we advise the developer to allow the user to change to the
> item they want, then hit a button to initiate the change. This would be on
> input, would it not? Also, let's say that the user arrows from one radio
> button to another, and the one they are moving from gets unchecked, and the
> one they are moving to gets checked. I see this as focus changing. Would
> this be correct?
>
> Also, in the explanation of the criterion, it says that a change of content
> isn't necessarily a change of context, so I tend to think, for example, that
> if you check a checkbox, change a radio button choice, or select a new list
> item, and some content appears on the same page right below where you are
> reading, that this would not be a change of context. Is my thinking correct
> about all of this?
>
> Also, I see on input as a failure when, for example, you are looking at a
> date entry group of fields with two-digit day and month, and as soon as you
> hit the second digit of one of those fields, focus jumps into the next
> control.
>
> Thanks.
>
> Jim
> Thanks.
>
> Jim
>
>
>
>
>
>
>
> =========> Jim Homme,
> Accessibility Consultant,
> Bender HighTest Accessibility Team
> Bender Consulting Services, Inc.,
> 412-787-8567,
> <EMAIL REMOVED>
> http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
> E+R=O
>
> > > > >


--
Work hard. Have fun. Make history.