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

> For example, on an ecommerce site you add an item to your basket and the indicator that it has worked is away from your focus. If affects everyone to some degree, but if it is completely off-screen (or if you are using a screen reader and no ARIA live) you have no idea.

I agree this is an issue.  The challenge then becomes if this is an issue related to AT for low vision that don't communicate live region or the author's responsibility.  When the page is 200% zoom you also see a smaller view of the page and may miss these changes without assistive technology active.  So would we require authors to do something other than an aria-control or aria-live region such as a visual notification?

Jonathan


-----Original Message-----
From: Alastair Campbell [mailto:acampbell@nomensa.com] 
Sent: Friday, May 06, 2016 11:51 AM
To: Patrick H. Lauke; public-mobile-a11y-tf@w3.org; GLWAI Guidelines WG org
Cc: lisa.seeman
Subject: Re: New SC relating to notifications of content change (was Re: Some thinking around the orientation discussion)

Patrick wrote: 
> "Where? Under which SC would this fall? To clarify, this is not (I 
> think)
4.1.2 as that SC relates to updating/notifying user of change to interactive elements/controls ... not about changes in the overall document/structure/content elsewhere on the page."

In support of this idea, there are two things I over-emphasise in training compared to the guidelines:

1. Off-screen changes for people using magnifiers (not covered).
2. Plain language (under 3.1 at AAA, but it actually helps almost everyone).

I do that having seen issues related to these come up a lot in usability testing.

For example, on an ecommerce site you add an item to your basket and the indicator that it has worked is away from your focus. If affects everyone to some degree, but if it is completely off-screen (or if you are using a screen reader and no ARIA live) you have no idea.

I'd been meaning to check if the LVTF had covered this scenario, perhaps not? 

I think one success criteria could cover the magnifier and screen reader aspects if written well, as it is about notifying someone of a change away from the keyboard and/or visual focus.

It can't just be covered by the user-agent as the meaning of the change will vary depending on the site and functionality of the site. Automatic notification would be overwhelming, and it probably needs some indication of what the change actually means.

Cheers,

-Alastair

Received on Friday, 6 May 2016 17:33:36 UTC