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

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

Throughout the site, there are some links (such as the feedback link in the header and the Legal Aid Checker on the Start page), that open in a new tab without warning users visually or programmatically.

This could be problematic for screen reader users who might not realise that a new tab has been opened. They would expect to navigate to the previous page using the back button in the browser or shortcut commands; this is not possible when the page opens in a new tab. This could confuse users and may lead them to get frustrated and abandon the process.

It can also be disorienting for some users with cognitive disabilities, who would expect the page to behave in a certain way. When pages behave unpredictably, it poses problems for these users.

Links that open in a new tab on the Start page

FIGURE 2.1: Links that open in a new tab on the Start page

2.1.2 Recommendation

If opening a page in a new tab/window is required, all users should be informed in advance. This could be achieved by including the warning as part of the link text:

<a>feedback (Opens in a new tab) </a>

Note that this is how other links are presented on the site, such as the links within the Related Content section.

2.1.3 Resources

W3C’s guide to giving users advanced warning when opening a new tab

2.1.4 Spot check: April 2024

This issue is unresolved. Some links still do not warn users in advance that they open in a new tab. Please refer to the above recommendation.