User Vision logo
  • Accessibility Audit
    • Executive Summary
    • Summary of Findings
    • WCAG 2.2 Overview
      • WCAG 2.2 Compliance
  • Project Background
    • Approach
    • How to use this report
    • Understanding our findings
  • I Findings
  • 1 Resolved Issues
    • 1.1 Site doesn’t allow for custom text spacing (Positive)
      • 1.1.1 Site doesn’t allow for custom text spacing
      • 1.1.2 Recommendation
      • 1.1.3 Spot check: April 2024
    • 1.2 Radio hint announcements are quite verbose (Positive)
      • 1.2.1 Radio hint announcements are quite verbose
      • 1.2.2 Recommendation
      • 1.2.3 Resources
      • 1.2.4 Spot check: April 2024
    • 1.3 Users not informed that link triggers a PDF download (Positive)
      • 1.3.1 WCAG 3.2.2 (A), 3.3.2 (A) - Mobile, iPad
      • 1.3.2 Recommendation
      • 1.3.3 Spot check: April 2024
    • 1.4 Dropdown items announced as not selected on receiving focus (Positive)
      • 1.4.1 WCAG 1.3.1 (A), 4.1.2 (A) -
      • 1.4.2 Code Snippet
      • 1.4.3 Recommendation
      • 1.4.4 Post-discussion Update
      • 1.4.5 Spot check: April 2024
    • 1.5 Fieldset not associated with a legend (Positive)
      • 1.5.1 WCAG 1.3.1 (A), 3.3.2 (A) - Desktop, Automated Finding
      • 1.5.2 Code Snippet
      • 1.5.3 Recommendation
      • 1.5.4 Spot check: April 2024
    • 1.6 Conditionally revealed fields not effectively announced by screen readers (Positive)
      • 1.6.1 WCAG 4.1.2 (A) - Android
      • 1.6.2 Recommendation
      • 1.6.3 Spot check: April 2024
    • 1.7 Content within collapsed field announced by screen readers (Positive)
      • 1.7.1 WCAG 1.3.1 (A), 4.1.2 (A) - Android
      • 1.7.2 Code Snippet
      • 1.7.3 Recommendation
      • 1.7.4 Spot check: April 2024
    • 1.8 No notification that feedback has been sent (Positive)
      • 1.8.1 WCAG 4.1.3 (AA) - Desktop, Mobile, iPad
      • 1.8.2 Recommendation
    • 1.9 Change links not programmatically associated with context (Positive)
      • 1.9.1 WCAG 1.3.1 (A), 2.4.4 (A) - Desktop, Mobile, iPad
      • 1.9.2 Recommendation
      • 1.9.3 Spot check: April 2024
    • 1.10 Confusing heading structure and hierarchy (Positive)
      • 1.10.1 WCAG 1.3.1 (A), 2.4.6 (AA) - Desktop, Mobile, iPad
      • 1.10.2 Recommendation
      • 1.10.3 Spot check: April 2024
    • 1.11 ARIA labels used on invalid div elements (Positive)
      • 1.11.1 WCAG 4.1.2 (A) - Desktop, Automated Finding
      • 1.11.2 Code Snippet:
      • 1.11.3 Spot check: April 2024
    • 1.12 Screen reader users not informed of feedback update (Positive)
      • 1.12.1 WCAG 4.1.3 (AA) - Desktop, Mobile, iPad
      • 1.12.2 Recommendation
      • 1.12.3 Spot check: April 2024
    • 1.13 Expanded elements not announced as such on iOS (Positive)
      • 1.13.1 WCAG 4.1.3 (AA), 4.1.2 (A) - iPad, iPhone
      • 1.13.2 Code Snippet
      • 1.13.3 Recommendation
      • 1.13.4 Resources
      • 1.13.5 Spot check: April 2024
      • 1.13.6 Spot Check update: July 2024
  • 2 Unresolved issues
    • 2.1 Some links open in a new tab without informing users in advance (Observation)
      • 2.1.1 Some links open in a new tab without informing users in advance
      • 2.1.2 Recommendation
      • 2.1.3 Resources
      • 2.1.4 Spot check: April 2024
    • 2.2 Purpose of the Back link could be more informative (Observation)
      • 2.2.1 Purpose of the Back link could be more informative
      • 2.2.2 Code Snippet
      • 2.2.3 Recommendation
      • 2.2.4 Spot check: April 2024
    • 2.3 Alternative options could be announced more clearly (Observation)
      • 2.3.1 Alternative options could be announced more clearly
      • 2.3.2 Code Snippet
      • 2.3.3 Recommendation
      • 2.3.4 Spot check: April 2024
    • 2.4 Acronyms could be expanded initially (Observation)
      • 2.4.1 Acronyms could be expanded initially
      • 2.4.2 Recommendation
      • 2.4.3 Spot check: April 2024
    • 2.5 Feedback buttons are not linked to the question prompt (Observation)
      • 2.5.1 Feedback buttons are not linked to the question prompt
      • 2.5.2 Code Snippet
      • 2.5.3 Recommendation
      • 2.5.4 Spot check: April 2024
    • 2.6 Hint text not completely announced on iOS (Observation)
      • 2.6.1 WCAG 1.3.1 (A), 4.1.2 (A) - iPad, iPhone
      • 2.6.2 Code Snippet
      • 2.6.3 Recommendation
      • 2.6.4 Spot check: April 2024
  • II Recommendations
  • 3 Suggested Next Steps
  • III Appendix
  • Contact Details
  • Prepared by User Vision for the Ministry of Justice

UV3073 MoJ Check If Your Client Qualifies for Legal Aid - Spot Check

1.9 Change links not programmatically associated with context (Positive)

1.9.1 WCAG 1.3.1 (A), 2.4.4 (A) - Desktop, Mobile, iPad

The Check Your Answers page presents users with the option to edit their previous options. This is presented visually with a ‘Change’ link adjacent to the heading of the section that users can edit. For sighted users, the purpose of this link is clear because of its position within a container, next the heading text. However, for screen reader users, this association is unclear.

When tabbing through the site with a screen reader, only the text “Change” is announced. As there are multiple such links, each announced as “change” on the page, screen reader users are not provided with the same level of information as sighted users. The purpose of these links could be confusing; users would have to navigate using their directional arrows to identify the section each link corresponds to. This causes a frustrating and time-confusing experience.

Sighted users can skim through a web page to get a quick overview of the content and functionality. Screen reader users often achieve this by going through certain elements of the page such as hyperlinks and buttons. Therefore, it is important to provide context to these interactive elements so that they know its purpose without having to navigate through additional content.

Similarly, when multiple elements have the same link text, screen reader users who navigate through the links using a list or heading structure may not be able to differentiate between them. They heavily rely on the link text to understand the destination or purpose of a link. If multiple links have identical link text, it becomes challenging for them to determine which link they want to follow.

This is similarly observed on the ‘Results’ page, where the ‘See Calculation’ links are not programmatically associated to the related heading.

Change links highlighted on the the Check Your Answers page

FIGURE 1.13: Change links highlighted on the the Check Your Answers page

Calculation links on the Results page with NVDA speech viewer activated

FIGURE 1.14: Calculation links on the Results page with NVDA speech viewer activated

1.9.2 Recommendation

Ensure that the link text is meaningful with its purpose made clear to all users.

The best method to achieve this is to make the displayed link text in itself meaningful and descriptive, such as:

<a> 
    Change Employment Status
</a>

Where this is not possible, or if it makes the page appear cluttered, ensure this additional context is also provided to screen reader users. This could be done by:

  • Using a span element within the link that is visually hidden using CSS. E.g:
<a> 
  Change
 <span class="visually-hidden">  Employment Status </span>
</a>
  • Using aria-label, e.g. <a aria-label="Change Employment Status"> Change </a>. Do note that using aria-label overrides the visually presented text for screen reader users.

1.9.3 Spot check: April 2024

This issue has been resolved. The change links are associated with their context using the aria-label attribute.

This has been changed from a ‘Low’ severity issue to a ‘Positive’ finding.