You're definitely noting an implementation problem. The use of CSS positioning has no inherent impact on a users ability to read a page with the style sheet turned off. In fact, if you've implemented your design with proper semantic xHTML, the user should see a plain page of readable HTML.
The be
Jochem,
I'll explain by example.
For example the wired.com front page only uses stylesheets for mark-up and positioning, using just DIV, P, SPAN and Header tags attached to IDs. (This page uses best practices from accessablity point of view according to the W3). If one were to pull the stylesheet
Jim,
I'm in agreement with you on this issue and in partial agreement with Sandy. Let me explain why.
a) DHTML Menus. Although DHTML flyout menus (submenus one sees on many sites) technically meet Section 508 compliance --they fail on useabability. Turns out screen readers users do not have a clu
Three other points I want to point out.
1) In practice, Section 508 implementation in in the mind of the US Government Agency (in Gov speak called the COTR). Although, sometimes there are spot checks for compliance, in practice, many agencies do not have the budget to complete a Section 508 (or ev
Section 508 from the web developer's point of view is really a series of thirteen checkpoints (The rest of the regulations are while important (especally if one bids on US Government contracts for network administration/help desk). To put everything into focus I've outlined the requirements below.
5 matches
Mail list logo
