On 29 Jun 2010, at 00:30, grant_malcolm_bai...@westnet.com.au wrote: > I'm trying to avoid use of Javascript due to accessibility concerns.
Trying to shoehorn functionality (which is what JS was designed for) into CSS (which is designed for presentation, not logic) is not good for accessibility. The classic example is the drop down menu which, if built using :hover instead of JS: * Can't respond to navigation without a pointer (e.g. keyboard tabbing, or a breath switch) * Can't have any 'fuzz factor' around the pointer position and timing of when a menu goes away (so if someone has any trouble at all with motor skills (e.g. because they have arthritis) they they could find it very different to get to the bottom of a menu without sliding outside it for a second and losing it) * Can't work in IE6 (since it's support for :hover is poor) (at least not without using a really evil hack involving conditional comments and layout tables). JavaScript is not the enemy of accessibility, it just has to be handled with care. If you are worried about pages breaking if JS is not available, then build on things that work: http://icant.co.uk/articles/pragmatic-progressive-enhancement/#build -- David Dorward http://dorward.me.uk ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
