Here's some things to think about that will keep accessibility in mind:

* resizable text (designer)
* sufficent contrast (designer)
* associate labels with form controls (designer/developer)
* meaningful link text (content owner)
* content chunks with good headings (content owner)

Accessibility does not start with valid code.

Valid code is nice, of course, however, accessibility is a usability
concern that goes beyond machine validation and into areas such as the
structual, IA, visual design, and content of a site.

It is possible to have create pages which validate (including WAI Priority
1) that present siginificant barriers to people with (and without)
disabilities. Conversely, it is possible to produce a very accessible site
where the markup does not validate.

What's more important IMHO is that you use structural markup as it is
intended (e.g. h1-h6, strong, em). My understanding is that it takes some
extra effort to get .net to produce good markup and getting the dev's to
do their bit first is a good.

The hardest part is getting content owners to write well for the internet
and the intended audience.


kind regards
Terrence Wood.

email: [EMAIL PROTECTED]
phone: +64-4-8033354
mobile: +64-21-120-1234

kvnmcwebn said:
> hello all,
> Ive started designing sites for this company that specilizes in .net
> databases driven/xml feed type sites. I just give them a graphics file and
> they slice it up.  Anyway they asked me yesterday if i could do this
> particular job with web accessability in mind. But heres the thing-when
> they
> mark up my designs and ad the vb .net code a typical page will be running
> validation errors in the hundreds. I told them that they need to start
> with
> web standards and get thier pages to validate before they start on
> accessability.
> Was that sound advice?



******************************************************
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
******************************************************

Reply via email to