Writing JavaScript with accessibility in mind
Manuel Matuzovic
8319

Hi,
This is a good article. One note, adding tabindex to a simulated element is not sufficient by itself to make it accessible, because browsers handle key events automatically for native active elements but do not for simulated active elements, regardless if tabindex is used to make it focusable. The following article section describes these differences in detail, which was written in collaboration with others in the W3C:
http://whatsock.com/training/#hd31

Regarding additional resources:

All of the WhatSock accessible widgets provided are designed to be scalable components that can be individually customized and dropped into any web technology, and are equally supported in jQuery, MooTools, and Dojo so they will tie directly into the rendering processes for any of these.

Specific framework download links:
Powered by jQuery: https://github.com/accdc/tsg
Powered by MooTools: https://github.com/accdc/tsg-mootools
Powered by Dojo: https://github.com/accdc/tsg-dojo

The following ARIA roadmap was written to assist university students in engineering programs plus existing engineers in learning ARIA more accurately, which is available as a PDF within the above GitHub project downloads plus at the following article address:
https://www.linkedin.com/pulse/engineers-self-paced-training-roadmap-learning-aria-bryan-garaventa

Regarding the concept of “unobtrusive accessibility” for HTML template engines and CMS frameworks, it is necessary to include a JavaScript layer that will automatically parse standard HTML markup and use this standard content to automatically configure and render complex interactive widgets that include all of the requisite focus handling and ARIA markup as needed to make it work accessibly. One such is available for this purpose at:
http://whatsock.com/bootstrap/jquery/
( https://github.com/accdc/bootstrap-jquery )

Also, Visual ARIA allows engineers, testers, educators, and students to physically observe ARIA usage within web technologies, including ARIA 1.1 structural, live region, and widget roles, proper nesting and focus management, plus requisite and optional supporting attributes to aid in development, available at:
http://whatsock.com/training/matrices/visual-aria.htm

Sincerely,
Bryan Garaventa

Like what you read? Give Bryan Garaventa a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.