​Hmmm... Let's kick this around a bit ... what this might look like. We reference HTML 5.2. Jurisdiction B implements a law or policy requiring WCAG 2.1 ... hundreds or thousands of web sites go back over all their form fields and add these at great expense. HTML 5.3 comes out and 10 of the 50 get dropped. Then in WCAG 2.2 we want to update the list. We cannot because we can't be backwards compatible.... so until Silver comes out authors are forced to use these antiquated tokens... This is a very realistic scenario. Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Mobile: 613.806.9005 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 Tue, Feb 20, 2018 at 3:59 AM, Joshue O Connor - InterAccess < josh@interaccess.ie> wrote: > John Foliot wrote: > > I think we need to step back from the fatalistic scenarios. > > +1 to this. The fact that these SCs have made it this far to CR > practically demonstrates their considerable robustness and potential. So I > urge the group to err on the side of collaborative optimism and continue on > with the good work. > > Thanks > > -- > Joshue O Connor > Director | InterAccess.ie >
Received on Tuesday, 20 February 2018 14:12:28 UTC