The World Wide Web Consortium (W3C) via the Web Access Initiative (WAI) has published the Web Content Accessibility Guidelines (WCAG) 2.0 Level of Conformance AA which have been adopted by Iowa State to guide web development that is accessible. Their Quick Reference Guide is useful in helping developers identify guidelines applicable to their projects.
For Rich Internet Applications, the W3C has put forth standards- the Accessible Rich Internet Applications (WAI-ARIA) Recommendation 1.0 - that help inform behaviors, focus, element definition, and other aspects of rich UIs to make them accessible.
If you adopt any of these code examples or tools, or have any established workflow or tools that inform your accessible development, we would like to hear from you. The Office of Digital Access is working to identify viable tools and workflows for the various platforms and development workflows on campus. We will appreciate your feedback and collaborate in this effort.
Demos and Code
Bryan Garaventa, accessibility expert and founder of WhatSock, shares technical documentation and code examples about the the "Accessibility Tree and How ARIA works" for those who want in-depth understanding of the intricacies of the layers involved in the accessibility of rich internet applications.
W3C provides an Accessible UI Components List including previews and code.
Deque University shares a library of accessible elements with its respective code.
Favelets is yet another way to address accessibility throughout development. SSB Bart Group provides information and resources on how to take advantage of favelets for checking web accessibility.
The a11yproject, a github community, has extensive documentation on how to for web developers. It is also a good way to contribute to accessibility efforts with your developer peers.
If you have to insert a carrousel in your page, please take time to look at W3C recommendations, rethink if it's possible to convey the message in a more accessible way. WhatSock provides an example of an accessible carrousel you may use as a guide.
Drupal developers can view this content management system's accessibility features in their documentation.
Visual Studio users can resort to the IDE's accessibility checker.
Axe-core, from Deque, offers the possibility of automated testing.
To test code, you may resort to Tenon.io.
A11yfy Library Functions for making jQuery code accessible
There is a list and links to accessibility tools in GitHub.
Android development can be made accessible with their accessibility scanner
Examples Library by SSB Bart Group