LCFS - Screen Reader Does Not Announce Focused Navigation Tab
- Dominant language
- Python
- Stars
- 6
- Forks
- 6
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 87
Description
**Describe the Bug**
The screen reader does not announce the focused navigation tab within the Organisation Dashboard navigation menu. As a result, users navigating with a keyboard and screen reader cannot determine which tab currently has focus.
**Expected Behaviour**
When a user navigates through the dashboard navigation tabs using a keyboard, the screen reader should announce the focused tab, including its name and state, allowing the user to understand their current location within the navigation.
**Actual Behaviour**
The visual focus indicator appears on the navigation tab, but the screen reader does not announce the focused tab or its associated information.
**Implications**
Users who rely on screen readers may be unable to identify which navigation item currently has focus, making navigation difficult and creating a significant accessibility barrier. This may result in users losing context within the application and prevent compliance with WCAG 2.2 accessibility requirements related to focus, navigation, and assistive technology compatibility.
**Steps To Reproduce**
Steps to reproduce the behaviour:
User/Role: Any screen reader user
1. Go to the Organisation Dashboard.
2. Navigate to the dashboard navigation menu containing tabs such as Dashboard, Users, Credit ledger, and Penalty log.
3. Use the keyboard (Tab or Arrow keys, as applicable) to move focus between navigation items.
4. Observe that the visual focus state appears on the selected tab.
5. Listen to the screen reader output.
6. Note that the focused navigation tab is not announced by the screen reader.
Contributor guide
Research direction
Start at the Organisation Dashboard navigation menu and reproduce the issue with a keyboard and screen reader, focusing on tabs such as Dashboard, Users, Credit ledger, and Penalty log. Done means the focused tab's name and state are announced while moving through the navigation items.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100