E-mail List Archives
Re: JavaScript and WCAG 2.0
From: Liko, Todd
Date: Jul 16, 2014 7:30AM
- Next message: Patrick H. Lauke: "Re: JavaScript and WCAG 2.0"
- Previous message: Andrew Kirkpatrick: "Re: JavaScript and WCAG 2.0"
- Next message in Thread: Patrick H. Lauke: "Re: JavaScript and WCAG 2.0"
- Previous message in Thread: Andrew Kirkpatrick: "Re: JavaScript and WCAG 2.0"
- View all messages in this Thread
Thank you Andrew.
I guess I lean more to the aggressive side. I do understand what you are saying and it does make sense to me when interpreting WCAG 2.0 in that way. I also understand that there will always be barriers for some users, but I do not think we should be creating those barriers. I am not comfortable with telling a user that because they are using a browser or assistive technology that does not support JavaScript, for example, that they cannot obtain the information.
I use the example of someone using a public computer at a public library and the computer has JavaScript disabled or outdated browsers and/or assistive technologies. The user may not be able to access the information. That being said, I also realize this kind of situation is out of our control, so as you said, it is the challenge of balancing the benefits to users vs. the difficulty in implementing and adopting into policies.
I realize this may be a black and white approach and this topic has no doubt been beaten to death already, but I appreciate the feedback.
Thanks,
Todd.
- Next message: Patrick H. Lauke: "Re: JavaScript and WCAG 2.0"
- Previous message: Andrew Kirkpatrick: "Re: JavaScript and WCAG 2.0"
- Next message in Thread: Patrick H. Lauke: "Re: JavaScript and WCAG 2.0"
- Previous message in Thread: Andrew Kirkpatrick: "Re: JavaScript and WCAG 2.0"
- View all messages in this Thread