6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.
WAI Priority 2 states that:
6.4 For scripts and applets, ensure that event handlers are input device-independent.
This means that:
i. if you use Javascript, provide an alternative for non-JS browsers
ii. if you use Javascript, as well as providing an alternative for non-JS browsers, ensure that the JS you use is not dependent on things such as mouse clicks etc...
Therefore, onClick is bad (although being able to tab to a button and use return may not be), but client-side validation (e.g. onBlur) may not be, provided that:
i. you can navigate away from the field you wish to validate without relying on your mouse (e.g. using tabs)
ii. you provide an alternative client-side validation for non-JS browsers.
Bearing the above in mind (i.e. the need to always provide an alternative method) it makes sense to provide only one method that works (i.e only provide the alternative) to cut down development and maintenance time. However, this means that developers are often stuck with the option of providing a less satisfactory method to appease the non-JS browser market.
I'm not sure that Section 508 has these specific JS restrictions.
Creating dynamic and interactive sites without JS is a major pain, and removing JS is often to the detriment of type of functionality that can be offered (IMO). That said, removing JS in Domino is probably more difficult than in other applications.
WAI Priority 1 states that:
6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.
WAI Priority 2 states that:
6.4 For scripts and applets, ensure that event handlers are input device-independent.
This means that:
i. if you use Javascript, provide an alternative for non-JS browsers
ii. if you use Javascript, as well as providing an alternative for non-JS browsers, ensure that the JS you use is not dependent on things such as mouse clicks etc...
Therefore, onClick is bad (although being able to tab to a button and use return may not be), but client-side validation (e.g. onBlur) may not be, provided that:
i. you can navigate away from the field you wish to validate without relying on your mouse (e.g. using tabs)
ii. you provide an alternative client-side validation for non-JS browsers.
Bearing the above in mind (i.e. the need to always provide an alternative method) it makes sense to provide only one method that works (i.e only provide the alternative) to cut down development and maintenance time. However, this means that developers are often stuck with the option of providing a less satisfactory method to appease the non-JS browser market.
I'm not sure that Section 508 has these specific JS restrictions.
Creating dynamic and interactive sites without JS is a major pain, and removing JS is often to the detriment of type of functionality that can be offered (IMO). That said, removing JS in Domino is probably more difficult than in other applications.
Cheers all
Jonathon
Cheers all
Jonathon