Re: Techniques with added structure

I agree.  I'd really like to work on emphasizing cross-over situations
in which doing one thing contributes to meeting several guidelines.

In the end this could be pulled out into a separate list of techniques
that need to be implemented as opposed to checkpoints that need to be
met.

- Jan  

> How about we have the following categories:
> 
> + Things you need to do to meet the checkpoint (these can be fairly general)
> + Techniques to do this (which should say how much of it they do)
> + Things which are good to do although they go beyond the requirements of the
>     checkpoint.
> + References
> 
> These probably need to be sorted (where applicable) by tool type and
> priority.
> 
> For example to meet checkpoint 1.1 in a level-A tool, all that needs to be
> done is to provide source editing (and meet checkpoint 1.2 Preserve all
> accessibiltiy information, which can be done by not messing up the source).
> 
> But for a WYSIWYG tool this will not conform to 5.1 and 5.2, so the tool
> cannot get to double-A. A source editing tool can use this technique to any
> level.
> 
> Cheers
> 
> Charles
> 
> On Tue, 17 Oct 2000, Jan Richards wrote:
> 
>   Hi all,
> 
>   Sorry I forgot to attach the file.
> 
>   Cheers,
>   Jan
> 
> 
> --
> Charles McCathieNevile    mailto:charles@w3.org    phone: +61 (0) 409 134 136
> W3C Web Accessibility Initiative                      http://www.w3.org/WAI
> Location: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia
> September - November 2000:
> W3C INRIA, 2004 Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France

Received on Wednesday, 18 October 2000 13:51:00 UTC