Component testing
As a developer, automation can be your friend.
How do we know what a component should do?
Look at the WAI-ARIA Authoring Practices.
Tip:
- The expected keyboard interaction is really helpful for testing.
- The examples are worth looking at.
Are there best practice design systems?
Yes. Take a look at:
- Gov.uk
- Agriculture Design System, Australian Government
- NSW Gov Components
- Vic Gov Components
- ARIA Authoring Practices Guide (APG)
- Design System, W3C
What tools are available for checking?
As a developer, automation can be your friend. A popular and free testing engine is axe-core.
Tip:
- Have a look at the community projects which integrate axe-core.
Can I see axe-core in action?
- Here is an axe-core test page with no code. Add some code and then click on 'Check Accessibility'.
- Here is an axe-core test page with some form input fields. Can you fix the problems?
Other Tools
- Siteimprove is an excellent plugin for Chrome that can check for accessibility problems.
- NVDA is a free screen reader for Windows that is excellent for testing.
- MAC users can perform screen reader testing using Voiceover.
Need web help?
All websites and applications which form part of the University web presence are expected to be compliant with the W3C's Web Accessibility Guidelines (WCAG) 2.2 AA guidelines.
Get web accessibility help