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 20:59:33 UTC