Agencies
ServicesPossible online services disruption due to Internet related outage
Web Accessibility
Illinois follows the World Wide Web Consortium (W3C)'s Web Content Accessibility Guidelines (WCAG). For more information, see:
- Introduction to Web Accessibility - an overview from WebAIM.
- WCAG 2.1 - the definitive guidelines for web accessibility from the W3C.
- IITAA Techniques - how to meet WCAG in terms developers may find easier to understand.
ARIA
The Accessible Rich Internet Applications (ARIA) guidelines explain how to make custom Javascript-based web components like dialogs, grids, menus, and tab panels accessible. With ARIA, almost anything is possible, but it's not easy. And remember, with great power comes great responsibility!
- Introduction to ARIA - instructions and cautions about using ARIA. READ THIS FIRST!
- ARIA 1.2 - the current specification. (ARIA 1.3 is in the works.)
- ARIA Authoring Practices Guide - instructions, patterns, and examples. You shouldn't be using ARIA without referring to this guide.
Accessibility Testing
There's a lot you can do to test websites and applications for accessibility without being an accessibility expert:
- Keyboard Testing - anything you can do with a mouse, you should be able to do from the keyboard. Here's how to check.
- Visual Testing - you can do a few basic visual tests using only your web browser and Windows settings.
- Screen Reader Testing - testing with a screen reader is harder than it seems. Here's how to get started, but don't do it without getting some training.
- Testing Standards - the process the State of Illinois follows when testing accessibility.
Accessibility Testing Tools
There are a number of free tools that can help you test accessibility. NONE of these tools can test everything that's required to be accessible. (If one says it can, don't use it!). But they're a good start:
- Accessibility Insights for Web - Microsoft's browser extension uses the reliable, open soure axe-core engine and adds some helpful tools and a guide for manual testing.
- axe DevTools - Deque's browser extension is careful to minimize false positives.
- ARC Toolkit - TPGi's browser extension is a little more aggressive, which is good as long as you can recognize false positives.
- WAVE - WebAIM's browser extension and web-based tester is probably the easiest to use and understand, but has some technical limitations. (It can't yet test within shadow DOMs.)
- Why Automated Accessibility Testing Isn't Enough - which ever automated testing tool you choose, read this first!