RE: New SC relating to notifications of content change (was Re: Some thinking around the orientation discussion)

It is a 3.2.2 Level A violation not to tell them is it not?

I agree that when they tab they will run into them but perhaps they just left off one of the radio buttons as an error message told them. They fill that out and then go to the link/button to resubmit.

They now have more un-filled in items that they need to fill in.

I’ve always stated that a simple title or aria type label “selecting will display new form fields” will do the trick.

At least we have told them that new items are displayed. 

It is a 3.2.2 Level A violation not to tell them is it not?
3.2.2 On Input
Level A
Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
Best, 

Alan

Sent from Mail for Windows 10

From: Gregg Vanderheiden
Sent: Wednesday, May 11, 2016 5:19 PM
To: Patrick H. Lauke
Cc: GLWAI Guidelines WG org; public-mobile-a11y-tf@w3.org
Subject: Re: New SC relating to notifications of content change (was Re: Some thinking around the orientation discussion)

Hmmm

but as soon as they click the button and proceed down the page they will find them. 

Do we need to put the load on an author if a person does not navigate the page in a normal top down fashion ?  
Esp where it will annoy people who are navigating it down the page in the normal fashion  and keep getting alerts or have to read through all sorts of unnecessary text ?  (e.g.  Do you want to insurance (if you choose this there will be additional questions to answer just below)     Do you want GPS (if you click on this there will be additional questions to answer below)    Do you want  

Whatever method you use to alert them - will have to be repeated for any particular items on the page that expand.  And this will be very annoying I would think — especially to screen reader users.. 

No?  

gregg 

On May 11, 2016, at 4:08 PM, Patrick H. Lauke <redux@splintered.co.uk> wrote:

On 11/05/2016 22:00, Gregg Vanderheiden wrote:

Correct

The question is — if these are BELOW the radio button in question — is
there any accessibility problem at all.  ??

There can be a problem if the user has already navigated past those radio buttons (perhaps to get an overview/feel for the form...or maybe they already went past that particular set of buttons previously and have now backtracked in the form), and now the form has mutated from what they previously encountered.

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