Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility notes jan 25 #1121

Merged
merged 2 commits into from
Jan 28, 2025
Merged

Accessibility notes jan 25 #1121

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f8439b4
docs: add accessibility issues content
murrlipp Jan 28, 2025
db2e2eb
docs: move content
murrlipp Jan 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/components/date-picker.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,18 @@ There's also the ['Ask users for dates' pattern in the GOV.UK Design System](htt

{% endtab %}

{% tab "Accessibility issues" %}

## Accessibility issues

There’s an accessibility issue with the date picker component. If you’re using it in your service you need to add these issue details to your accessibility statement.

### No focus indicator shown when navigating between dates (NVDA only)

When people use the screen reader software NVDA, no focus indicator is displayed when they navigate between dates. This only happens with NVDA software. This fails [WCAG 2.2 success criterion 2.4.7 (Focus visible)](https://www.w3.org/TR/WCAG22/#focus-visible). We’re aware of this issue and plan to implement a fix by April 2025.

{% endtab %}

{% tab "How to use" %}

## How to use
Expand Down
13 changes: 13 additions & 0 deletions docs/components/search.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,3 +18,16 @@ Use the search component to let users search by word or phrase. This can be used
## How to use

You can configure the search form to be inversed on black and to hide and show labels and hints depending on your use case. You'll see examples of this on the [Primary Navigation](/components/primary-navigation) component page.

## Accessibility issues

There’s an accessibility issue with the search component. If you’re using it in your service, you need to add these issue details to your accessibility statement.

### Screen reader and keyboard users cannot clear the text entry field

Screen reader and keyboard users cannot access the ‘x’ button to remove text from the search text entry field. This fails the following requirements:
- [WCAG 2.2 success criterion 2.1.1 (Keyboard)](https://www.w3.org/TR/WCAG22/#keyboard)
- [WCAG 2.2 success criterion 2.4.3 (Focus order)](https://www.w3.org/TR/WCAG22/#focus-order)
- [WCAG 2.2 success criterion 2.4.7. (Focus visible)](https://www.w3.org/TR/WCAG22/#focus-visible)

We’re aware of this issue and plan to implement a fix by April 2025.
8 changes: 8 additions & 0 deletions docs/components/sortable-table.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,3 +20,11 @@ Use this component when sorting is needed to help find data within a large table
## How to use

If you are using [Nunjucks](https://mozilla.github.io/nunjucks/) or the [GOV.UK Prototype Kit](https://govuk-prototype-kit.herokuapp.com/), you can use the Nunjucks [table macro](https://design-system.service.gov.uk/components/table/).

## Accessibility issues

There’s an accessibility issue with the sortable table component. If you’re using it in your service you need to add these issue details to your accessibility statement.

### The sorting icons are read out in a confusing way

The sorting icons are read out to screen reader users, but without meaningful information. This fails [WCAG 2.2 success criterion 1.1.1 (Non-text content)](https://www.w3.org/TR/WCAG22/#non-text-content) and [WCAG 2.2 success criterion 1.3.1 (Info and relationships)](https://www.w3.org/TR/WCAG22/#info-and-relationships). We’re aware of this issue and plan to implement a fix by April 2025.
Loading