LCFS - Screen Reader Does Not Announce Supporting Documents Icon or Chevron
- Dominant language
- Python
- Stars
- 6
- Forks
- 6
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 87
Description
**Describe the Bug**
Within the Compliance Report Supporting Documents section, the screen reader does not announce the icon and chevron associated with the Supporting Documents control. Users navigating with assistive technologies cannot determine the purpose, state, or functionality of these interactive elements.
**Expected Behaviour**
When navigating to the Supporting Documents section, the screen reader should announce the accessible name, role, and state of the icon and chevron. Users should be able to understand the purpose of the control, whether it is expandable/collapsible, and interact with it using a keyboard and screen reader.
**Actual Behaviour**
The screen reader does not announce the icon or chevron, leaving users without information about the control or its functionality.
**Implications**
Users who rely on screen readers may be unable to identify, understand, or interact with the Supporting Documents section. This creates an accessibility barrier and may prevent users from accessing or managing supporting document uploads independently.
**Steps To Reproduce**
Steps to reproduce the behaviour:
User/Role: Compliance Report User using a Screen Reader
1. Go to a Compliance Report.
2. Navigate to the Supporting Documents section.
3. Use a keyboard and screen reader to move focus to the icon and chevron beside the section heading.
4. Listen to the screen reader announcement.
5. Observe that the icon and chevron are not described or announced.
6. Attempt to determine the purpose or state of the control using screen reader output alone.
Contributor guide
Research direction
Start in the Compliance Report's Supporting Documents section and reproduce the issue with a keyboard and screen reader. Inspect the control beside the section heading; done when its accessible name, role, expanded or collapsed state, and keyboard interaction are announced clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100