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.

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

Focus new content on route changes #57

Merged
merged 3 commits into from
Jul 30, 2019

Conversation

seanforyou23
Copy link
Collaborator

@seanforyou23 seanforyou23 commented Jul 15, 2019

This PR adds some code that ensures focus is placed on new content after route changes. This has the effect of causing screen readers to read the content aloud upon loading new page content. This helps ensure users receive adequate feedback in response to their actions and ensures they are oriented after page transitions and don't have to needlessly re-find the content after switching views.

It also works for async routes!

It builds on top of #56 and is dependent on patternfly/patternfly-react#2519.

Should help close #55

src/app/routes.tsx Outdated Show resolved Hide resolved
@seanforyou23 seanforyou23 force-pushed the route-change-focus-content branch from 7a6d30b to 2e6d218 Compare July 23, 2019 17:23
@seanforyou23 seanforyou23 changed the title [WIP] Focus new content on route changes Focus new content on route changes Jul 23, 2019
@seanforyou23 seanforyou23 requested review from dlabaj and dgutride July 23, 2019 22:20
listen for route changes, send focus to the new content after route changes
add react styles pkg, adjust webpack config
specify main container element id
allow for sending route props to page components
ensure focus is sent after sync and async routing alike
bump pf version to consume changes in react-core
@seanforyou23 seanforyou23 force-pushed the route-change-focus-content branch from 2c3552d to a1467f5 Compare July 30, 2019 20:30
@mturley
Copy link
Collaborator

mturley commented Aug 19, 2022

Note for posterity: this feature was broken on the Support page by the removal of the async route feature in #103. See #103 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Screen reader users should be made aware of route changes
3 participants