RE: Success criteria in ATAG2 that refer to WCAG2

And the WCAG-WG commenters include another idea:

>     A.1.1.1 Web-Based Accessible (WCAG Conformance): Web-based
> authoring tool user interfaces conform to WCAG 2.0 at one of the
> following conformance levels.
> 
>         * Level A: For Level A conformance, web-based authoring tool
> user interfaces conform to WCAG 2.0 Level A. (Level A)
>         * Level AA: For Level A conformance, web-based authoring tool
> user interfaces conform to WCAG 2.0 Level AA. (Level AA)
>         * Level AAA: For Level A conformance, web-based authoring tool
> user interfaces conform to WCAG 2.0 Level AAA. (Level AAA)

Cheers,
Jan

-- 
(Mr) Jan Richards, M.Sc.
jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
Inclusive Design Research Centre (IDRC) | http://inclusivedesign.ca/
Faculty of Design | OCAD University


> -----Original Message-----
> From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On
> Behalf Of Richards, Jan
> Sent: August 30, 2010 12:26 PM
> To: w3c-wai-au@w3.org
> Subject: Success criteria in ATAG2 that refer to WCAG2
> 
> Hi all,
> 
> Quite a few commenters in the past (and now WCAG WG) have had an issue
> with how we split up our success criteria that point to WCAG 2.0:
> 
> Current Wording:
> ================
> B.1.1.1 Accessible Content Production (WCAG Level A): Authors can use
> the authoring tool to produce web content that conforms to WCAG 2.0
> Level A. (Level A) [Implementing B.1.1.1]
> 
> B.1.1.2 Accessible Content Production (WCAG Level AA): Authors can use
> the authoring tool to produce web content that conforms to WCAG 2.0
> Level AA. (Level AA) [Implementing B.1.1.2]
> 
> B.1.1.3 Accessible Content Production (WCAG Level AAA): Authors can use
> the authoring tool to produce web content that conforms to WCAG 2.0
> Level AAA. (Level AAA) [Implementing B.1.1.3]
> 
> In the past:
> ============
> We had a concept of Relative Priority. Which looked simple enough in
> the success criteria: "A.0.1 For the authoring tool user interface,
> ensure that Web-based functionality conforms to WCAG. [Relative
> Priority]"
> 
> But which had too much explanatory overhead
> (http://www.w3.org/TR/2006/WD-ATAG20-20061207/#priority-Relative).
> Commenters found it confusing and suggested splitting them up.
> 
> Options:
> ========
> Option A: Keep it the way it is (split up).
> Option B: Attempt to re-combine them in a way that maintains clarity...
> 
> Ideas:
> - B.1.1.1 Accessible Content Production: Authors can use the authoring
> tool to produce web content that conforms to WCAG 2.0. (Level A/AA/AAA
> depending on the level of conformance to WCAG 2.0 ) [Implementing
> B.1.1.1]
> 
> - B.1.1.1 Accessible Content Production: Authors can use the authoring
> tool to produce web content that conforms to WCAG 2.0. (Level is the
> same as the level of conformance to WCAG 2.0) [Implementing B.1.1.1]
> 
> Other ideas?
> 
> Cheers,
> Jan
> 
>

Received on Monday, 30 August 2010 16:31:28 UTC