Re: Guideline 3.2 HTML Tests

Thanks Chris. Apologies for the delayed response. Some answers to your 
questions and comments inline...

Chris Ridpath wrote:
> I've been looking over guideline 3.2 and created a document 
> that lists the HTML tests that are currently associated with it:
> http://checker.atrc.utoronto.ca/docs/tests-3.2-2005-09-09.html
>  
> So far, there is only one HTML test (test 92) that is associated with 
> this guideline. There are currently 4 techniques associated with the 
> guideline but only one of them has an associated test. The other 3 
> techniques have no tests.
>  
> We have some tests that may also fall under this guideline and I've 
> listed them below so we can discuss.
>  
> We harvested several techniques related to guideline 3.2 and they could 
> be open for discussion too:
> http://www.w3.org/WAI/GL/2005/06/30-tech-harvest-by-tech.html
>  
> Now that the techniques task force has been disbanded I'm not sure if we 
> will be following our previous process of accepting/rejecting the tests. 
> The techs task force was also in the process of harvesting more 
> techniques and I'm unsure if we'll continue that process too. Gregg et 
> al. - how would you like to proceed with accepting/rejecting the tests 
> and harvesting techniques?
>  

[BBC] I think that since we're not operating form a top-down perspective 
on this again, we should be postponing further work on tests until we're 
a bit further along with developing techniques. As we develop new 
techniques, we should be thinking about tests and (hopefully) drafting 
them at the same time. We should be able to stick with our previous 
process for reviewing tests when we reach that point.

> Tests that may be related to guideline 3.2:
>  
> Adjacent links with same resource must be combined.
> http://www.w3.org/WAI/GL/WCAG20/tests/test180.html
>  
[BBC] Not sure how this relates to 3.2. I don't think our guidelines 
currently require this.

> Link text is meaningful when read out of context
> http://www.w3.org/WAI/GL/WCAG20/tests/test19.html
>  
[BBC] I thihnk this is a better match for guideline 2.4 L2 SC4 (The 
destination of each programmatic reference to another delivery unit is 
identified through words or phrases that either occur in text or can be 
programmatically determined.)

> Anchor should not open new window without warning.
> http://www.w3.org/WAI/GL/WCAG20/tests/test18.html
>  
> area should not open new window without warning.
> http://www.w3.org/WAI/GL/WCAG20/tests/test68.html
>  

[BBC] 3.2 no longer requires that users be warned about new windows. 
However, this might fit under an advisory technique for 3.2 L3 SC2.

> All source anchors contain text that identifies the link destination.
> http://www.w3.org/WAI/GL/WCAG20/tests/test197.html
>  
> Alt text for all area elements identifies the link destination.
> http://www.w3.org/WAI/GL/WCAG20/tests/test65.html
> This is currently mapped to guideline 2.4 L2 SC4 "The destination of 
> each programatic reference..."
> http://www.w3.org/TR/2005/WD-WCAG20-20050630/#navigation-mechanisms-refs


[BBC] The 2.4 L2 SC4 mapping seems appropriate for both of these.

>  
> Sites must have a site map.
> http://www.w3.org/WAI/GL/WCAG20/tests/test184.html
>  
[BBC] I think this maps to 2.4 L2 SC1 (More than one way is available to 
locate content within a set of delivery units.)

> All data tables contain a caption that describes the nature of the table 
> unless the nature of the table is described by the table's summary.
> http://www.w3.org/WAI/GL/WCAG20/tests/test151.html
>  
[BBC] This seems to be something for guideline 1.3 L1 SC1 (Structures 
within the content can be programmatically determined)

Received on Tuesday, 4 October 2005 22:35:12 UTC