-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Blog 2020-02-05 Accessible Routing #21018
Blog 2020-02-05 Accessible Routing #21018
Conversation
LGTM 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome! No major changes, just some cosmetic stuff and relative links. One thing I was unsure about is whether @reach/router should be in back ticks. I added them, but not sold on that decision.
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
Co-Authored-By: LB <barth.laurie@gmail.com>
also add descriptive text for issue #5581
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks awesome!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is so awesome!! Great job putting this together. I left some comments and suggestions, let me know if you have any questions!
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
|
||
### Some Background | ||
|
||
Our first step to addressing focus management (the first recommendation, above) was [switching](/blog/2018-09-27-reach-router/) to [`@reach/router`](https://reach.tech/router). This got us part of the way there out-of-the-box. However, Gatsby’s implementation of `@reach/router` isn’t idiomatic in that Gatsby puts everything on a single, catch-all route. This means that every page is technically on the same route and route changes weren’t getting picked up by `@reach/router`. Our improvements in [2.13.2](https://github.com/gatsbyjs/gatsby/pull/13197) made sure that every time a route changed, we reset focus on a wrapping `div`. These changes also ensure that our single, catch-all route is dynamic so we can register changes and take advantage of `@reach/router’s` strengths. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should add up front that this didn't work in some assistive technologies–that was why work on the router needed to continue (NVDA and VoiceOver weren't actually working even with that fix, which meant the related GitHub issue couldn't be closed).
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
Co-Authored-By: Marcy Sutton <marcy@gatsbyjs.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is so awesome!! I left a couple of minor suggestions, let me know what you think. And thanks for working on a post to share your work with the world!
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md
Outdated
Show resolved
Hide resolved
Co-Authored-By: Marcy Sutton <marcy@gatsbyjs.com>
…-05-accessible-routing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, @madalynrose! Looking forward to seeing this out in the world!!
…-05-accessible-routing
16b5a76
Description
Blog post announcing changes that went out in #19290 and #20914 (I'm lumping them together because I want people to use the version that came after the latter was released)
Related Issues
Related to #5581