Thank you all for responding, and thank you for the link regarding forms.
As with div's, I am beginning to understand. Use them for overall layout, but if there is an alternative within a div tag not to use them, then don't use them.
Take care,
Nancy
russ - maxdesign <[EMAIL PROTECTED]> wrote:
> 1. Where can I find a good example of how forms should be laid out for
> accessibility.
Try these:
http://www.d.umn.edu/itss/support/Training/Online/webdesign/accessibility.ht
ml#forms
http://www.nils.org.au/ais/web/resources/WSG_Oct_04/toc.html
> 2. Comment on div tags. If we are not suppose to use tables for layout and div
> tags are supposed to be used with restraint. What other options with layout
> are there?
Are you referring to this:
7.and elements have no real semantic meaning, so use
them judiciously. I'm not saying "don't use them", but if there is another
element that explains the content, use it instead!
This seems to be talking more about the direct mark-up of content than
overall positioning. With marking up content, the aim is to use the most
correct elements (the element that has the most meaning) where possible and
use divs only if needed.
With overall layout, the aim is to get away from tables and unnecessary divs
- there may be times when you can position an element directly. For example:
If you use afor your navigation, you may not need to place the
inside a- you could apply positioning style to thedirectly.
However, if the nav also needed other elements, you would probably need to
wrap them all in a div and position that.
Russ
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
