W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2006

Re: updated table

From: Jan Richards <jan.richards@utoronto.ca>
Date: Fri, 05 May 2006 11:08:58 -0400
Message-ID: <445B6A8A.3030108@utoronto.ca>
To: w3c-wai-ua@w3.org
Hi,

Yesterday I took an action item to pull out of the alignment list the 
UAAG checkpoints that support WCAG success criteria at each level (see 
attached). Then I cross-referenced these with the UAAG Implementation 
report for HTML 4.01 (see below). Here are some observations:

1. Most of the supporting checkpoints apply to level 1 WCAG success 
criteria (of the 3 that don't at the moment, I think there is a case 
that all of them might be "general") - this would simplify things by 
collapsing the checkpoints into a single "subset of UAAG that directly 
supports any level of WCAG conformance".

2. Unfortunately, the implementation of this subset of UAAG is not 
widespread, so the same argument the WCAG-WG used for not requiring UAAG 
  Level A would apply.

3. Compiling such a subset also raises a bigger question...is this a de 
facto re-prioritizing of UAAG? And if so, this probably isn't a good 
idea since those priorities were agreed upon as part of W3C process. (my 
sense is that if we looked through UAAG there's probably more 
checkpoints that would qualify for the general category anyway - 
otherwise why are they P1's?)

4. And, as mentioned yesterday, there are probably differences between 
technologies (e.g. HTML vs Flash) when it comes to the supporting subset.

So...perhaps this was a useful exercise, but one that we may want to 
keep internal.

Cheers,
Jan






Cross-referencing with the UAAG Implementation report for HTML 4.01

COMPLETE (>2 browsers)
2.8 No repair text (P3)
9.8 Provide text search (P2)

ALMOST COMPLETE (>2 browsers)
1.1 Full keyboard access (P1)
2.1 Render content according to specification (P1)
8.1 Implement accessibility features (P1)
8.2 Conform to specifications (P2)
9.3 Move content focus (P1)

PARTIALLY IMPLEMENTED
10.2 Highlight selection, content focus, enabled elements, visited links 
(P1)

NOT IMPLEMENTED
2.5 Make captions, transcripts, audio descriptions available (P1)
2.6 Respect synchronization cues (P1)
4.6 Do not obscure captions (P1)

UNKNOWN
6.1 Programmatic access to HTML/XML infoset (P1)
6.3 Programmatic access to non-HTML/XML content (P1)
6.4 Programmatic access to information about rendered content (P1)
6.5 Programmatic operation of user agent user interface (P1)
6.6 Programmatic notification of changes (P1)






-- 
Jan Richards, M.Sc.
User Interface Design Specialist
Adaptive Technology Resource Centre (ATRC)
Faculty of Information Studies
University of Toronto

   Email: jan.richards@utoronto.ca
   Web:   http://jan.atrc.utoronto.ca
   Phone: 416-946-7060
   Fax:   416-971-2896




Received on Friday, 5 May 2006 15:10:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:34 GMT