No problem. You start from this page:
http://www.w3.org/TR/WAI-WEBCONTENT/
There is a huge list of rules divided into 3 priority levels:
Priority 1: Developer *must* satisfy this point. Otherwise some people
will find it impossible to access information. Satisfying this point
is a basic requirement for some groups to use the site.
Priority 2: Developer *should* satisfy this point. Otherwise some people
will find it difficult to access information. Satisfying this point
will remove significant barriers for some people.
Priority 3: Developer *may* address this point. Otherwise some people will
find it somewhat difficult to access information. Satisfying this
point will improve access to documents.
If you meet all the priority 1 requirements you have WAI-A compliance.
If you also meet the priority 2 requirements you have WAI-AA compliance.
If you also meet the priority 3 requirements you have WAI-AAA compliance.
>From my experience, WAI-AA is a good goal. It takes work, but is doable.
WAI-AAA sounds good, but is *very* difficult to achieve. I consider WAI-A
a bare minimum. It's amazing how many sites wouldn't make it to WAI-A. :-(
Cheers,
Daniel.
On Wed, Jan 19, 2005 at 11:56:56AM +1100, Matthew Wardrop wrote:
> Oh, and sure... It would be great to have it tested for usability.
>
> Might you show me how it is done after you've done it, or as, depending
> on the procedure.
>
> It sounds interesting.
>
> Kind Regards,
> --
> Matthew Wardrop <[EMAIL PROTECTED]>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
Daniel Carrera | I know everything, I just can't remember
Join OOoAuthors today! | it all at once.
http://www.oooauthors.org | :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
