- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Mon, 9 May 2016 17:10:45 -0400
- To: David MacDonald <david100@sympatico.ca>
- Cc: "White, Jason J" <jjwhite@ets.org>, Gregg Vanderheiden <gregg@raisingthefloor.org>, Alastair Campbell <acampbell@nomensa.com>, Jonathan Avila <jon.avila@ssbbartgroup.com>, GLWAI Guidelines WG org <w3c-wai-gl@w3.org>, "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
I point out that SC 3.2.2 says, "... unless the user has been advised of the behavior before using the component". So often in situations of checkboxes for filters sometimes accompanied with a sort feature too, if things are happening dynamically in an 'non-visual' manner, I suggest they need to include a visual notification advising users of the behavior or placement of a go-button that triggers the change only on user request. I agree, using title / aria-label and aria-live / aria-controls can be included in the recommendations. A title attribute helps AT users and mouse users ... user agents really should be made to support title for keyboard users too. [1] Also updating table caption / heading above the newly displayed content / search / filtered results and judicious use of aria-live helps. Depending on situation and context, one can use the present SCs notably 3.2.2, 1.3.2, 2.4.3 at most times. For the update to count of items in cart, if it is not in viewport for anyone or not easily perceivable even by non-PWD, one can highlighht that as a big usability issue generally and that may be considered more critical (sadly than even accessibility) by many clients and get fixed on a priority basis. Clients can be urged to change the UI design and then with aria-live etc. the content can be made accessible as well. Defining anew SC can be tricky and create some overlap. [1] https://blogs.windows.com/msedgedev/2016/04/20/building-a-more-accessible-web-platform/ Thanks, Sailesh Panchang On 5/9/16, David MacDonald <david100@sympatico.ca> wrote: > If it's not currently covered in WCAG SCs and we are chartered to update > WCAG, then I don't think we should shy away from the hard job of creating > normative language. Yes SCs are hard to write... but we've done it before > and we have several members who have been around a long time and can help > get drafts reasonably sharp...We have great language in the existing SCs to > draw from... > > Some proposals will require dozens of iterations, some won't make it, like > salmon swimming upstream, or baby turtles rushing to the ocean. But I think > we can do this, given that the entire disability community and web > community is begging for an update... > > Let's give it a shot, and if we fail, so be it... > > > > 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 Mon, May 9, 2016 at 4:08 PM, White, Jason J <jjwhite@ets.org> wrote: > >> >> >> >> >> *From:* Gregg Vanderheiden [mailto:gregg@raisingthefloor.org] >> *Sent:* Monday, May 09, 2016 3:51 PM >> >> ok >> >> >> >> now how do you define "sufficiently significant change “ >> >> >> >> this is what drives you nuts on creating Success CRITERIA >> >> >> >> >> >> +1 >> >> >> >> Writing good success criteria is hard. I don’t think it’s a suitable job >> for task forces; it needs the participation and the review of the entire >> working group, as well as the iterative process of responding to public >> comments and refining the text over time. >> >> >> >> ------------------------------ >> >> This e-mail and any files transmitted with it may contain privileged or >> confidential information. It is solely for use by the individual for whom >> it is intended, even if addressed incorrectly. If you received this >> e-mail >> in error, please notify the sender; do not disclose, copy, distribute, or >> take any action in reliance on the contents of this information; and >> delete >> it from your system. Any other use of this e-mail is prohibited. >> >> Thank you for your compliance. >> ------------------------------ >> >
Received on Monday, 9 May 2016 21:17:43 UTC