W3C home > Mailing lists > Public > w3c-wai-au@w3.org > July to September 2002

Re: Impact on ATAG Wombat of Changes to WCAG's Priority Scheme

From: Jan Richards <jan.richards@utoronto.ca>
Date: Mon, 09 Sep 2002 15:08:15 -0400
Message-ID: <3D7CF19F.E799AD42@utoronto.ca>
To: Liddy Nevile <Liddy.Nevile@motile.net>
CC: W3C WAI-AU <w3c-wai-au@w3.org>

I have reworded the priorities section using Liddy's comments to try and
make the definition of "Relative Priority" more clear.

Thoughts?

Cheers,
Jan


1.2 Checkpoint Priorities

The overall goals of this specification are the following:
That the authoring tool be accessible;
That the authoring tool produce accessible content by default;
That the authoring tool encourage the creation of accessible content.

Each checkpoint in the specification has been assigned one of the
following priority levels to reflect the importance of the checkpoint in
meeting these goals:

[Priority 1]:
This checkpoint is essential to meeting the goals. 

[Priority 2]:
This checkpoint is important to meeting the goals. 

[Priority 3]:
This checkpoint is beneficial to meeting the goals. 

[Relative Priority]
This checkpoint requires a high-level authoring function (e.g. checking
markup accessibility) that depends for its specific requirements on the
checkpoints of the Web Content Accessibility Guidelines (WCAG) 2.0
[WCAG20]. The priority of this checkpoint is relative because its effect
on the goals is determined by the extent to which its required authoring
function meets the WCAG 2.0 checkpoints. Specifically, the required
authoring function may meet each of the WCAG 2.0 checkpoints at one of
four levels: not met, minimum (most important requirements met), level 2
and level 3 (least important requirements met). The relative priority
level reflects this as follows:

Relative Priority - Level "A": The checkpoint satisfies all relevant
WCAG 2.0 checkpoint requirements to at least the minimum level.

Relative Priority - Level "Double-A": The checkpoint satisfies all
relevant WCAG 2.0 checkpoint requirements to at least level 2.

Relative Priority - Level "Triple-A": The checkpoint satisfies all
relevant WCAG 2.0 checkpoint requirements to at least level 3.

For example:

ATAG checkpoint 5.1 has a relative priority. The checkpoint requires
tools to check for accessible content as defined by the requirements of
WCAG 2.0. This means that if the tool checks for minimum and level 2
requirements of several WCAG checkpoints, but only the minimum
requirements for the rest, the tool would receive Relative Priority -
Priority 1 - for ATAG checkpoint 5.1.

Note: The priority level for each checkpoint has been chosen based on
the assumption that the author is a competent, but not necessarily
expert, user of the authoring tool, and that the author has little or no
knowledge of accessibility. For example, the author is not expected to
have read all of the documentation, but is expected to know how to turn
to the documentation for assistance.



Liddy Nevile wrote:
> 
> Jan
> the 7.2 change seems OK to me but I found it hard to read your new
> 'Relative Priority' para...
> I suggest modifying it as follows:
> 
> >[Relative Priority]
> >When the checkpoint requires implementation of some
> >functionality (i.e. generating, checking, repairing, etc.) for which
> >some or all of the checkpoints in the Web Content Accessibility
> >Guidelines (WCAG) 2.0 [WCAG20] are relevant, relative priority is
> >assigned. This priority level is
> >relative to the priority of requirements of the WCAG 2.0
> >checkpoints that are not all equally important for the accessibility of Web
> >Content. WCAG 2.0 prioritises requirements by
> >establishing three different levels of conformance for each checkpoint:
> >minimum (for the most important requirements), level 2 and level 3 (for
> >the least important requirements). ATAG Wombat Relative
> >Priority checkpoints inherit their priorities as follows:
> >
> >Relative Priority - Level "A": The checkpoint satisfies relevant WCAG
> >2.0 checkpoint requirements to at least the minimum level.
> >
> >Relative Priority - Level "Double-A": The checkpoint satisfies relevant
> >WCAG 2.0 checkpoint requirements to at least level 2.
> >
> >Relative Priority - Level "Triple-A": The checkpoint satisfies relevant
> >WCAG 2.0 checkpoint requirements to at least level 3.
> >
> >For example:
> >
> >ATAG checkpoint 5.1 requires tools to check
> >for accessible content as defined by the requirements of WCAG 2.0.
> >5.1 has relative priority. This
> >means that if the tool checks for minimum and level 2 requirements
> >of several WCAG checkpoints, but only the minimum requirements for the
> >rest, the tool would receive Relative Priority - Priority 1 - for ATAG
> >checkpoint 5.1.
> >
> >Note: The priority level for each checkpoint has been chosen based on
> >the assumption that the author is a competent, but not necessarily
> >expert, user of the authoring tool, and that the author has little or no
> >knowledge of accessibility. For example, the author is not expected to
> >have read all of the documentation, but is expected to know how to turn
> >to the documentation for assistance.
> 
> Liddy

-- 
Jan Richards, User Interface Design Specialist
Adaptive Technology Resource Centre (ATRC), University of Toronto

  Email: jan.richards@utoronto.ca
  Web:   http://ultrajuan.ic.utoronto.ca/~jan/jan.html
  Phone: 416-946-7060
  Fax:   416-971-2896
Received on Monday, 9 September 2002 15:08:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 22 September 2008 15:53:01 GMT