logo

New Response

« Return to the blog entry

You are replying to:

    • avatar
    • Ron Yuen
    • Posted on Thu 1 Dec 2005 08:28 AM

    Jake

    I must be missing something here as I don't understand what 'Accessibility' has to do with any of this.

    JS is not proscribed by any Accessibility guidelines that I know of, nor should it be, Accessibility is fundamentally determined by the way technologies are deployed rather than the technologies themselves.

    1. You can design the form without JS for those that are not allowed JS though I suggest that if there is much application complexity then I personally would not bother. (Users have to go some of the way)

    2. You can validate at the backend using SaveOptions etc etc

    3. You can notify the user of any failure via an agent 'Print' message

    4. They can use their Back button to go back to the form, still with the field values visible, correct and re-submit.

    ?? Where is the 'Accessibility' issue ??

    It's perfectly possible to re-create the user page, 'merge' the field values and send it back to them, but it's a shed load of work, why bother when they have a back button !

    Those who do not use JS or other client side scripting cannot expect as slick an experience as those that do.

    BTW I continue to enjoy the blog, keep it up.

    Regards

Your Comments

Name:
E-mail:
(optional)
Website:
(optional)
Comment: