W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2009

RE: Silent / Hidden Automatically Updating Information

From: Andrew Kirkpatrick <akirkpat@adobe.com>
Date: Thu, 8 Jan 2009 13:38:10 -0800
To: WCAG <w3c-wai-gl@w3.org>
Message-ID: <5076E68FCD2E91428C2479984A81E1147B2165C1B7@NAMBX01.corp.adobe.com>

Bruce,
Can you describe a couple of specific scenarios that highlight your concerns? I think I understand what you are saying but I'm not sure that it isn't being handled as Andi suggests under 4.1.2.  When a control value is changed, by the user or by a script, there is a valuechange event that is communicated for assistive technologies to use. Whether the AT does or not is another question.

Thanks,
AWK

Andrew Kirkpatrick

Senior Product Manager, Accessibility

Adobe Systems 

akirkpat@adobe.com


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Bailey, Bruce
Sent: Thursday, January 08, 2009 9:12 AM
To: WCAG
Subject: Silent / Hidden Automatically Updating Information


I am thinking of a situation where a web app form element silently fills
in data elsewhere on the form without explicitly alerting the end user.
Assuming no other problems, like unexpected change of context, do we
have an SC which requires that auto-updating data be proactively exposed
to the end user?

This is pretty standard AJAX behavior, but it is a problem that AT users
are experiencing disproportionately.  It is altogether too easy for a
user to submit data that may be visually pretty obvious, but easy to
miss when using screen magnification or screen reader (since the
automatically updated information is hidden off screen or made silent by
default by purposeful design).

I am thinking maybe we missed this, since some aspect of the behavior is
often desirable.  Do we have something documented about this as far as
best practices go?

SC 2.2.2 (which is actually in the Enough Time GL 2.2) is pretty much a
requirement for the opposite behavior.

Updated information which does not interrupt the end-user would not
violate 3.2.1 On Focus or 3.2.2 On Input.

Being able to review a form for changes is required by 4.1.2 Name, Role,
Value -- but there might be no indication that reviewing the form is
warranted!

Arguably, leaving out details that a form has automatically updated
fields violates <q>instructions are provided when content requires user
input</q> (3.3.2 Labels or Instructions) but that feels *very* tenuous
to me.

It is fine if I have just created an action item for myself, but then
where would be the home for such a best practice advisory?
Received on Thursday, 8 January 2009 21:38:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:56 GMT