I am now interested in how the standard of readily available or free works here, since each person is working with the specifics of their physical situation to accommodate. You referenced in browsers, and reference with Jaws, adaptive technology that i cannot physically use.which sort of illustrates my understanding that design is not about tool, but interaction. Perhaps your comment that it was done in a stupid fashion illustrates that point. My understanding is that JavaScript is a compliant technology, so long as it works from the keyboard. A button or input element would do the job perfectly well using far less coding, and there is absolutely no reason to use JavaScript in this case.Ĭc: Eric Eggert RE: Short Survey for CSUN Likewise, it is best practice to use the simplest solution. The reason I say the coding is stupid, is that WCAG states that native elements should be used where possible. Is there any reason why you cannot use a modern browser? These are all available free, so if you choose to use an out of date browser with incomplete JavaScript support, WCAG takes the view that that is your problem. Most people would still consider it to be compliant because the button is keyboard accessible with Chrome, Firefox, Internet Explorer and Edge. I can't work out exactly how it works, but I am not entirely surprised it doesn't work with some less-capable browsers. The JavaScript on the button responds to various events, such as "click" and "mousedown", but these are not implemented by means of the usual onClick and onMousedown event handlers. The specification is actually ECMAScript, and it's got nothing to do with Google. The JavaScript specification is continuously updated, so older browsers will not support new changes. There have been no changes at all since 2017. The last stable release was ten years ago and development has essentially stopped. It only ever had partial JavaScript support.
If it isn't, the website could violate many WCAG success criteria, of which keyboard operation is only one.Įlinks is not "JavaScript friendly" and you should not be using it. JavaScript is an accessibility supported technology, but it needs to be implemented correctly. You are mixing up a whole load of different things, so let's deal with them one at a time.
0 kommentar(er)
