-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
P2Not critical at the momentNot critical at the momentUICSS and layout relatedCSS and layout relatedoutsourcedtasks for contractortasks for contractor
Milestone
Description
Description
To make our app more friendly for assistive technologies, we should implement the following improvements to support screen readers, keyboard navigation, and other tools.
Tasks
- Mark decorative containers: Add
aria-hidden="true"
to anythat only holds icons (e.g. those using thei-nimiq:...
syntax) or is otherwise empty/decorative. - Provide meaningful
alt
text on images and icons that convey information. - Follow other best practices
- Ensure focus indicators are visible for keyboard users.
- Clarify structure for screen readers
- Establish a clear heading hierarchy (H1 → H2 → H3).
- Add a “Skip to content” link at the top of each page.
- Improve blog posts for screen readers—see this video for guidance on /blog.
Discussion
- Are there any other accessibility checks we should include?
- What’s the best approach for testing—manual review vs. automated tooling (e.g. axe, Lighthouse)?
Done when:
- All checklist items are implemented.
- CI passes
Metadata
Metadata
Assignees
Labels
P2Not critical at the momentNot critical at the momentUICSS and layout relatedCSS and layout relatedoutsourcedtasks for contractortasks for contractor