WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: source order

for

From: Patrick H. Lauke
Date: Apr 7, 2008 7:20PM

Jared Smith wrote:

> - Using absolute positioning can cause other issues (pages that break
> when fonts are enlarged, etc.)

unless you're careful and also use relative units for your absolute
positioning - which sounds like a paradox, but actually works nicely.

> - If users disable styles, suddenly the order is different than what
> they saw visually.

even more common: a sighted user that has stylesheets enabled and
expects the visual tab order to match the onscreen layout may well be
confused if it isn't the case.

A "mechanism/method to skip" has been mentioned in relation to 508. This
is also in WCAG 2. Worth noting, though, that this mechanism doesn't
necessarily have to be something that the developer actively provides
(e.g. a skip link), but it can be (at least for WCAG 2) simply grouping
things in logical containers (e.g. marking up navbar as a list) and/or
adding headers before the navigation and the content...the active
skipping can then be taken care of by assistive technology, for instance.

P
--
Patrick H. Lauke
______________________________________________________________
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com
______________________________________________________________
Co-lead, Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
______________________________________________________________
_______________________________________________
To manage your subscription, visit http://list.webaim.org/
Address list messages to <EMAIL REMOVED>