DFE-Digital / DFE-Digital/check-performance-data

[A11y] 4.1.2 Name, Role, Value – 'Disclosure triangle' announced on expandable sections

Open
#388 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
0
Forks
1
Avg merge
19h 21m
Merged PRs (30d)
54

Description

Split from #381, which reported five separate problems under one ticket.

Tester has observed that on Android TalkBack, "disclosure triangle" is announced when the user navigates to the expandable sections.

This does not comply with WCAG Level A 2.2:
4.1.2 Name, Role, Value - https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html

Steps to Recreate:

  1. Navigate to URL
  2. Navigate to an expandable section with Android TalkBack enabled
  3. Observe issue

This has been observed on the following pages:

  • Guidance
  • Permanent Exclusion

Environment:
Android 15 - Samsung Galaxy S22 - Chrome 151 - TalkBack (mobile screen reader)

Reproduction rate:
100% - Consistently reproducible.

Supporting material:
Video: https://drive.google.com/drive/folders/1Ph21Q5-UlnfnvKJ1zQQA-K5uM-WY14X2?usp=sharing

Version: https://check-performance-data-preproduction.teacherservices.cloud/

2.Major Impact on Accessibility


Assessment needed before any work. The expandable sections use the native HTML <details> / <summary> elements (the GOV.UK Details component, Views/Journey/_Question.cshtml). "Disclosure triangle" is TalkBack's own name for that native role, not text this service supplies. This may well be a "no action" outcome. Confirm with the auditor before changing the markup, because replacing the native element with ARIA is usually worse for other assistive technology.

Priority: High
DoneDone issue: https://zoonou.mydonedone.com/issuetracker/projects/91343/issues/8

Parent: #373. Split from: #381

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Views/Journey/_Question.cshtml and the GOV.UK Details component used for the expandable sections. Reproduce the announcement on the Guidance and Permanent Exclusion pages with Android TalkBack, then confirm the expected behavior with the auditor before changing markup. Done means the auditor agrees on either no action or a specific accessible outcome.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, html
Domain
accessibility, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.