WEB STANDARDS CREATIVITY

260
There may be unforeseen consequences for an invalid value, and manipulating the DOM to include a tabindex value on
nodes where it is not a valid attribute seems a bit hackish. We’re really using JavaScript only to camouflage the fact that
we’re doing something that is invalid per the HTML specification.
Conclusion
The -1 tabindex strategy seems to have support within the industry. The Web Hypertext Application Technology
Working Group (WHAT WG, www.whatwg.org), a group that is composed of web browser vendors and
other interested parties, is working on producing HTML5. In that specification, tabindex is an attribute that
will be allowed for any element, and will allow negative tabindex values.
Is this the ultimate accessible solution? Maybe and maybe not. What we do know is that we’ve done our best to ensure we
have a baseline of interoperability and accessibility in the solution by doing the following:
Providing content and core functionality through simple HTML code
Ensuring that we use unobtrusive scripting
Ensuring our fonts are scalable and use both foreground and background colors together
Using CSS in creative ways to modify the way things appear while maintaining a logical, semantic structure
Using JavaScript such that we use links and hrefs to our advantage to lead a keyboard user or screen reader user
through the page
We have done basic testing that allows us to address many of the issues a person with a disability will face when using this
solution. Additional testing will tell you for sure whether or not this solution is usable and useful to all users with all levels
of ability. It is imperative that you do your own accessibility testing with real users.
Try the techniques demonstrated here on your websites. This chapter has given you enough information to get started with
your own accessible JavaScript solutions.