Should we drop any WCAG 2 SCs in 2.1?

On today's mobile call Jeanne brought up an important consideration as we
make the WCAG 2.1. If 2.1 seems much longer than 2.0 we may be facing
resistance to the new version. It came up in the context of the question
about whether we should try to roll new SCs into the existing SCs where
possible, or introduce new SCs.

But I think the issue raises another question.

Are there any SCs that have been overcome sufficiently by the environment,
OS, User Agents etc. that we can remove them without breaking the
acceptance requirement of WCAG 2.1 that meeting it also meets 2.0?

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>