Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Screenreader Navigation: Screenreader Focus in Guided Experience #1645

Open
brdunfield opened this issue Dec 20, 2018 · 6 comments
Open

Screenreader Navigation: Screenreader Focus in Guided Experience #1645

brdunfield opened this issue Dec 20, 2018 · 6 comments
Labels
accessibility

Comments

@brdunfield
Copy link
Collaborator

When you click a next button in the GE, the focus seems to persist on the old button that no longer exists, vs going back to the top of the "new" page.
@brdunfield brdunfield self-assigned this Jan 3, 2019
@brdunfield
Copy link
Collaborator Author

Might be related to #1478

@brdunfield brdunfield removed their assignment Jan 3, 2019
@SupeDeDupe
Copy link
Contributor

Accessibility: Keyboard Navigation

@courtneycl
Copy link

Does this still happen? I don't think I can repro but I might not be doing it properly.

@smcmurtry
Copy link
Collaborator

Accessibility: Screenreader Navigation

@smcmurtry smcmurtry changed the title Keyboard Navigation: Focus in Guided Experience Screenreader Navigation: Screenreader Focus in Guided Experience Feb 5, 2019
@smcmurtry
Copy link
Collaborator

Since we split the GE into separate pages it looks like this is fixed for keyboard users, but not for screenreader users. So I've changed the title and moved it on trello.

@JuliannaR
Copy link

Yay! you are using tags for accessibility. Thanks! Is the focus changing if a screen reader is active?

@smcmurtry smcmurtry mentioned this issue Mar 19, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accessibility
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@courtneycl @brdunfield @smcmurtry @SupeDeDupe @JuliannaR