Skip to content
This repository has been archived by the owner on Oct 5, 2021. It is now read-only.

Android talkback can't focus on nav on subsequent pages #4

Closed
bogusred opened this issue Aug 31, 2018 · 2 comments
Closed

Android talkback can't focus on nav on subsequent pages #4

bogusred opened this issue Aug 31, 2018 · 2 comments
Assignees
@bogusred

Comments

@bogusred
Copy link
Contributor

After navigating to later pages, you can't focus on buttons in nav. it just focuses on the entire landmark.

Added aria-live="off" to fix this.
bogusred added a commit that referenced this issue Aug 31, 2018
@bogusred
fix(nav): landmarks with talkback and voiceover
d26890a 
- Fix bugs relating to landmarks that were preventing talkback and voiceover from reading content and/or navigation areas
- Remove completed TODO's
- Add aria-live to indicate to screen reader that the content area will change.

Fixes #1, #2, #3, #4
@bogusred bogusred reopened this Sep 1, 2018
@bogusred
Copy link
Contributor Author

bogusred commented Sep 1, 2018

still experiencing this bug in the e/aria branch. i think it might be because i nested header and nav and that these two things shouldn't be nested. i may need to make nav a top level item.

@bogusred bogusred self-assigned this Sep 1, 2018
@bogusred
Copy link
Contributor Author

bogusred commented Sep 1, 2018

According to specs, landmarks can be nested. Yet moving nav outside of header did fix the issue.

Other references:
https://www.w3.org/TR/wai-aria-practices/examples/landmarks/navigation.html

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bogusred bogusred

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bogusred