This report explains the accessibility issues that are stopping the Independent Health and Aged Care Pricing Authority (IHACPA) website from conforming to WCAG 2.1 at Level AA. While the structure of the website is good, some features and custom functionality have been implemented without web accessibility in mind.
This report was prepared in by Larry Hudson, Hilary Kaplan and Shannon Loh from the Information Access Group. The screen reader user testing was completed by James Battaglia and Assunta Fogliaro.
| Principle | Results by principle |
| Perceivable | 20 of 20 |
| Operable | 15 of 17 |
| Understandable | 10 of 10 |
| Robust | 3 of 3 |
| Total | 48 of 50 |
This report explains the accessibility issues that are stopping the Independent Health and Aged Care Pricing Authority (IHACPA) website from conforming to WCAG 2.1 at Level AA. While the structure of the website is good, some features and custom functionality have been implemented without web accessibility in mind.
This report was prepared in by Larry Hudson, Hilary Kaplan and Shannon Loh from the Information Access Group. The screen reader user testing was completed by James Battaglia and Assunta Fogliaro.
This report has been updated to reflect the status of the issues after re-testing on 25 March 2024.
Our standard process is to test a website in different browsers and on different devices. This includes Chrome, Firefox and Edge on Windows 11, Safari on macOS, Chrome on Android and Safari on iPhone.
We use a mix of machine level testing of the entire site with testing software called Accessibility Insights.
We then undertake manual checking, including testing keyboard accessibility, as well as testing behaviour with different screen readers including JAWS, NVDA and VoiceOver.
Our screen reader testers James and Assunta supported us with manual checking. For this project, they conducted checks using JAWS and Edge on Windows and VoiceOver and Safari on iPhone.
We also conducted user testing of the website with James and Assunta over Zoom.
We use the WCAG-EM reporting methodology.
The WCAG-EM methodology consists of:
Scope:
Not in scope:
The audited website should work in at least the following browsers and assistive technologies:
The audited web page relies on the following technologies:
The homepage of Example Company.
An example of a blog post
The main menu does not work with just a keyboard. The links are marked up like this:
<div class="link 202034rsfd oiarjgeoi" onclick="woo()">About us</div>Use <a> tags for the links, and use the href attribute for the location to link to, like this:
<a href="/about-us">About us</a>The <a>-tag works with keyboard out of the box, does not rely on JavaScript and makes it easier for search engines to understand what is going on.
Focus styles have been removed through the website's stylesheets:
* {
outline: none
}This causes problems for people who use the website without a mouse, as they will not be able to see where they are.
Remove the outline: none rule, and/or add a specific style that applies on :focus. Make sure that it has sufficient contrast, too.