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 Sitewide Findings
    • 1.1 Positive: radio buttons associated to the question (Positive)
      • 1.1.1 WCAG 1.3.1 (A) - Desktop
      • 1.1.2 Code snippet
    • 1.2 Positive: Checkboxes programmatically associated with the question (Positive)
      • 1.2.1 WCAG 1.3.1 (A) - Desktop
      • 1.2.2 Code snippet
    • 1.3 Focus state of button elements doesn’t meet non-text colour contrast requirements (Medium)
      • 1.3.1 WCAG 1.4.11 (AA) - Desktop
      • 1.3.2 Recommendation
    • 1.4 Missing heading level (Low)
      • 1.4.1 WCAG 1.3.1 (A) - Desktop
      • 1.4.2 Recommendation
    • 1.5 Breadcrumb navigation could be improved (Low)
      • 1.5.1 WCAG 1.3.1 (A), 4.1.2 (A) - Desktop
      • 1.5.2 Code snippet
      • 1.5.3 Recommendation
      • 1.5.4 Resource
    • 1.6 Purpose of the Back link could be more informative (Observation)
      • 1.6.1 Purpose of the Back link could be more informative
      • 1.6.2 Code Snippet
      • 1.6.3 Recommendation
  • 2 Prisoner not hoping to work after release
    • 2.1 Positive: Change links programmatically associated to context (Positive)
      • 2.1.1 WCAG 1.3.1 (A) - Desktop
      • 2.1.2 Code snippet
    • 2.2 Text coded as a table (Medium)
      • 2.2.1 WCAG 1.3.1 (A), 2.4.3 (A) - Desktop, iPad
      • 2.2.2 Code snippet
      • 2.2.3 Recommendation
    • 2.3 Problematic column headers (Low)
      • 2.3.1 WCAG 1.3.1 (A) - Desktop
      • 2.3.2 Code snippet
      • 2.3.3 Recommendation
      • 2.3.4 Resources
    • 2.4 Remove link not associated with context (Observation)
      • 2.4.1 Remove link not associated with context
      • 2.4.2 Recommendation
    • 2.5 No space between elements on iPad (Observation)
      • 2.5.1 No space between elements on iPad
      • 2.5.2 Recommendation
  • 3 Induction for employed ex prisoners
  • 4 View full plan
    • 4.1 Visually hidden table column announced by screen readers (Medium)
      • 4.1.1 WCAG 1.3.1 (A) - Desktop
      • 4.1.2 Code snippet
      • 4.1.3 Recommendation
  • 5 Edit induction information
  • 6 Adding a goal
    • 6.1 Textarea not associated with the warning message (Observation)
      • 6.1.1 Textarea not associated with the warning message
      • 6.1.2 Code snippet
      • 6.1.3 Recommendation
  • 7 Editing a goal
  • II Recommendations
  • 8 Suggested Next Steps
  • III Appendix
  • Contact Details
  • Prepared by User Vision for the Ministry of Justice

UV2986 Ministry Of Justice - Learning and Work Progress

2.4 Remove link not associated with context (Observation)

2.4.1 Remove link not associated with context

On the Prisoner’s qualifications page, users are required to confirm their answers prior to submitting the report. Users can make changes to the information by selecting the adjacent ‘change’ link. To sighted users, it is easy to instantly see the association between the links and the adjacent information. However, there is no programmatic association between the link text and the adjacent information, which means blind screen reader users will need to use the arrow keys to navigate across the table.

Link text should be consistently clear, both visually and programmatically, so the emphasis isn’t on the user to decipher where the link goes.

For a positive example of this see: Positive: Change links programmatically associated to context (Positive)

Remove button highlighted with NVDA speech viewer activated

FIGURE 2.4: Remove button highlighted with NVDA speech viewer activated

2.4.2 Recommendation

As a suggestion, consider implementing a visually hidden span in the same way it is elsewhere on the site i.e.

<button 
type="submit"
 value="LEVEL_5-test-b" 
name="removeQualification">Remove
</button> <span 
class="govuk-visually-hidden"> 
[level], [subject], [grade]</span>