Re: Should we drop any WCAG 2 SCs in 2.1?

On 14/07/2016 21:58, David MacDonald wrote:
> I agree it would be difficult to drop anything and make make 2.1
> backward compatible, unless an SC has been overcome by events, and is
> automatically met.
>
> A candidate might be...
>
> 1.4.2 audio control, because user agents are implementing a way to mute
> a tab without muting system audio. On Firefox Control+M mutes any sound
> coming from the page and allows the screen reader to read the page. The
> SC says "a mechanism is available" so now its available in a major
> browser... and will soon be in all browsers (hopefully). But for WCAG
> one stack is enough.

Browsers aren't the only user agents around, though (particularly when 
WCAG gets applied to more than just websites, but actual native apps etc 
as well)

> I don't see how I can ever fail someone on 1.4.2 anymore, thanks to
> James pointing this out.  If we are looking to not cause SC bloat with
> the new SCs, perhaps we can make a new category for SCs which have been
> largely overcome by advances in User Agents etc... which still apply to
> 2.1 but are folded away somewhere so 2.1 is not bloated with SCs that
> developers don't need to worry about.
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613.235.4902
>
> LinkedIn
> <http://www.linkedin.com/in/davidmacdonald100>
>
> twitter.com/davidmacd <http://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 Thu, Jul 14, 2016 at 2:05 PM, John Foliot <john.foliot@deque.com
> <mailto:john.foliot@deque.com>> wrote:
>
>     Hi David,
>
>     I don't think I'm understanding the question - I can't see how we
>     could remove a SC from a WCAG 2.1 and preserve a
>     backwards-compatible path to 2.0.
>
>     Again, WCAG is about content requirements AFAIK, and while
>     techniques and patterns can come and go, the principles and Success
>     Criteria remain, and I would be concerned about dropping a Success
>     Criteria simply on the basis that newer technologies seemingly make
>     it easier to achieve any individual Success Criteria. That, in and
>     of itself, would not justify removing a requirement in my mind (only
>     make it simpler for content authors to meet the Success Criteria).
>
>     Can you elaborate more please?  Thanks.
>
>     JF
>
>     On Thu, Jul 14, 2016 at 12:00 PM, David MacDonald
>     <david100@sympatico.ca <mailto:david100@sympatico.ca>> wrote:
>
>         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 <tel:613.235.4902>
>
>         LinkedIn
>         <http://www.linkedin.com/in/davidmacdonald100>
>
>         twitter.com/davidmacd <http://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>
>
>
>
>
>     --
>     John Foliot
>     Principal Accessibility Strategist
>     Deque Systems Inc.
>     john.foliot@deque.com <mailto:john.foliot@deque.com>
>
>     Advancing the mission of digital accessibility and inclusion
>
>


-- 
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 Thursday, 14 July 2016 21:08:16 UTC