Skip to content

Lack of a11y unit testing. #7

Open

Description

@harryhmc

PR #6 was raised to solve an a11y issue in one of the components that was not caught by the built-in Storybook tests.

In order to prevent such problems in the future, it would be good to have unit tests covering the accessibility of each component in their respective test files.

Activity

  1. colinrotherham commented on Sep 29, 2025

    @colinrotherham
    Collaborator

    Linking this with #192 (comment)

    Can we pick this up as part of #216?

    All component HTML is tested by Axe (upstream) in NHS.UK frontend

    Rather than repeat the tests here we should test if our HTML matches NHS.UK frontend

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions