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:
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.
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://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: