Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add TalkBack and keyboard navigation coverage for the Android reader

Open
  • Is something wrong?
#115 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android
Domain
accessibility, mobile-dev, testing

Research direction

Start with the Android reader screens from #84 and #85 and the app navigation, using the Android accessibility testing reference. Map the listed reading flows to automated accessibility assertions and define a repeatable manual procedure for TalkBack and keyboard checks. Done means the acceptance criteria are covered and each reproducible defect includes its screen, steps, expected result, and evidence.

Written by the indexing model from the issue text.

Description

android difficulty: intermediate enhancement help wanted needs testing

Roadmap: #76

Goal

Make the public reading flows verifiable with assistive input.

Acceptance criteria

  • Exercise project selection, locale selection, article opening, headings, links, retry, and back navigation with TalkBack.
  • Verify meaningful control names, reading/focus order, and announcements for loading/error states.
  • Check keyboard navigation and focus restoration for the same core controls.
  • Add automated accessibility assertions supported by the selected stack and a repeatable manual procedure for the remaining checks.
  • File each independently reproducible defect with a screen, steps, expected result, and evidence.

Start: Reader screens from #84/#85 and app navigation. This is Android coverage; website smoke testing remains #51.

Reference: Android accessibility testing.

Prerequisites: #84, #85.

Dominant language
Go
Stars
1
Forks
7
Avg merge
2h 19m
Merged PRs (30d)
17

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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.

More from wavefnd/wave-platform

All issues in wavefnd/wave-platform

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.