On Fri, 8 Jun 2007 16:49:00 +1000, Kane Tapping wrote: > I took this one to mean that you should be writing your form in a > accessible and non-js way first then use JS to HIJAX ( > http://ajaxian.com/archives/hijax-graceful-degration) that version to > provide enhanced useability.This way you get a perfectly useable form > without JS and enhanced usability when it is enabled.
I have considered that, and there are very, very few places where I would use a noscript element - the 'select dropdown' is probably the only *common* implementation I do. The only problem with the 'make it plain, then pretty it with JS' approach is the Redraw Problem. The first thing to bear in mind is that for the majority of applications more than 95% of your visitors will be using a plain vanilla graphical browser. While a web page/app must be accessiible, it must also service your majority audience *perfectly*. Having elements pop in and out on a slow connection is very confusing for Joe Public, and if its a page or site that will take their money its important Not to make them feel in anyway insecure on what is happening. Because of this, I've made a specific decision that, rather than having a: select + button, then use JS to remove the button and add an onclick, I have: select + noscripted-button, and use js to add an onclick (actually, I think its an onchange - I'd have to go look). This gives an almost identical experience to non-js browsers and a perfect experience to Joe Public's vanilla browser, and avoids elements popping in and out on the screen. If its below the fold it doesn't matter so much If the element is very visible at the top of the page then its important. It would probably be worthwhile to consider browsers that do js, but don't support onchange but I haven't looked into it - its a pretty old element. IMHO warmly, Lea -- Lea de Groot Elysian Systems Brisbane, Australia ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
