Re: Compromise on Numbering: Changing 11 AAA numbers solves the level problem

> have the numbers all mixed up in the new WCAG 2.0

Just to confirm, we aren't going to have a "new" WCAG 2.0, but rather a
'dot-release' of WCAG (2.1), which consists of newly emergent Success
Criteria built on top of WCAG 2.0.

Respectfully David, your proposal appears to presume that entities will
either be fully WCAG 2.0 compliant, or fully WCAG 2.1 compliant, and yet
doesn't leave room for entities going for mandated compliance to 2.0 +
cherry picking *some* new SC now, and gradually adding additional new SC
over time. In a case like that (which I personally anticipate will be the
norm, certainly in the early days), how do we address numbering conflicts
in your proposal?

Like others, I continue to believe this is not a workable proposal (-1).
More importantly however, I think we need to evaluate this proposal against
all the other proposals that have come forward equitably. Your suggestion
that there are only 3 other options (of which the quoted text is one of
them) does not match the 6 current proposed models
<https://www.w3.org/WAI/GL/wiki/WCAG_2.1_SC_Numbering> in the wiki page.

Additionally, also captured in that wiki page, we have previously heard
from stakeholders the following:

To renumber or not to renumber…

In the legislative/statutory world


   - renumbering generally the last option
      - people rely on section and title/chapter numbers – these become
      citations.
      - if renumbering, Revisor of Statutes creates a detailed table to
      show the old number, the new number, when it took effect, etc.
      - WCAG – has become international standard and may have been adopted
      in whole by states, countries, etc. If we renumber, the numbers will no
      longer be consistent.
      - Inconsistent numbers/citations mean everything that cites them
      contains invalid cites.


Given the global legislative dependencies we have on WCAG 2.0 today, I
believe we need to take this feedback with the appropriate seriousness it
deserves.

JF

On Mon, Sep 18, 2017 at 7:23 PM, David MacDonald <david@can-adapt.com>
wrote:

> Here's what it would look like
>
> tinyurl.com/jmo9st4
>
> It's a new proposal not included in any previous proposed numbering model.
>
> The remaining options are to have:
> - the levels all mixed up
> - have the numbers all mixed up in the new WCAG 2.0
> - deemphasize numbers
>
> I would like to see the document look elegant, new, and integrated. I
> think it's a worthwhile compromise to allow AAA to change numbers.
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
> Mobile:  613.806.9005 <(613)%20806-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 Mon, Sep 18, 2017 at 4:57 PM, David MacDonald <david@can-adapt.com>
> wrote:
>
>> The current problem is that new Level SCs come in after AAA in
>> thenstandard unless we jugle the order or deemphise number, neither of
>> which is ideal.
>>
>> Here's a proposal that might work as a compromise.
>>
>> Level AAA SCs are less entrenched in the WCAG culture. What if we agree
>> that those numbers can change.
>>
>> - Change 11 Level AAA SC numbers
>> - Insert the new SCs in their proper place
>> - move accidental activation to Pointer Guideling as per Steve's
>> suggestion Issue #376
>> - Make new Speech guideline 2.7
>>
>> This would allow the numbers to make sense with the levels also in order,
>> so no Level A or AA would follow AAA, and would keep ALL Level A and AA SC
>> numbers in tact.
>>
>> Cheers,
>> David MacDonald
>>
>>
>>
>> *Can**Adapt* *Solutions Inc.*
>> Mobile:  613.806.9005 <(613)%20806-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>
>>
>
>


-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion