- From: David MacDonald <david100@sympatico.ca>
- Date: Fri, 6 May 2016 13:07:23 -0400
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- CC: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>, GLWAI Guidelines WG org <w3c-wai-gl@w3.org>, "lisa.seeman" <lisa.seeman@zoho.com>
- Message-ID: <BLU436-SMTP1879ABBCBB0C212E161E8FBFE7D0@phx.gbl>
I've started up a rough draft and added all these comments... https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_on_information_added_or_removed_from_a_page This is an early draft of a new SC. We have to strike the balance between not being overly prescriptive, and addressing the biggest problem. It is definitely a problem to have a control changing the content which is above precedes the control in the Accessibility tree. Jonathan and Gregg feel this is covered. I don't remember any sustained discussion about notifying users of changes on a page in WCAG except changes in context where the author moves the user focus or as patrick says, changes in the role state value of an interactive control ...I'm my reports and training, I've been marking it as a best practice to notify users of changes to the page, but haven't been logging failures. I'd have to search through the WCAG 2 minutes archives 2000-2008, but I don't remember us addressing additions/deletions specifically, and mapping it to a success criteria. Perhaps I missed a meeting where this happened. It wasn't very common back then... I'm still open to the idea it is already covered... If it is, then I think we have to manage this gap in a11y professionals understanding, including my own, with some specific failures, techniques and language on the Understanding documents... Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613.235.4902 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> twitter.com/davidmacd GitHub <https://github.com/DavidMacDonald> www.Can-Adapt.com <http://www.can-adapt.com/> * Adapting the web to all users* * Including those with disabilities* If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html> On Fri, May 6, 2016 at 11:20 AM, Patrick H. Lauke <redux@splintered.co.uk> wrote: > On 06/05/2016 15:56, Gregg Vanderheiden wrote: > >> >> I think this is essential - but I think it is already covered. >> > > 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 (so that if their status changes, or their > actual function/label, that this is done in a way that then conveys the > change programmatically to users), not about changes in the overall > document/structure/content elsewhere on the page. > > If not - then it would need to be clarified in connection with >> conformance rather than as another SC. >> If this isn’t obvious/clear already (and evidently it isnt) then I >> THINK it could be clarified in Understanding WCAG 2.0 — and be done >> immediately with the next publication of that document. >> >> I and Loretta and David and others can confirm that it was the intent >> and understanding of the group that if it changed - it should remain >> accessible. >> >> >> does this help? >> >> >> >> /gregg/ >> > > -- > 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 > > >
Received on Friday, 6 May 2016 17:07:54 UTC