Update accessibility user testing post

[marcysutton]

Description

Since the blog post on accessible client-side routing and user testing was published in July, the recommended technique has evolved a bit. I updated the post to explain the latest rationale and include links to both the virtual talk where I retested it with Sam from Fable Tech Labs, and the example source code.

This has been on my mind for a while so I'm submitting the PR now! I tried to balance detail and understanding of the technique here, so let me know if it doesn't make sense.

Documentation

N/A

Related Issues

None

[madalynrose]

This looks great! The only question I have is around formatting: I believe on other pages with Note asides we keep formatting the same and don't pull it into a quote block. Are we setting a new precedent?

[laurieontech]

Thanks for the PR @marcysutton! I have a similar question to @madalynrose, but other than that I think this is a great update. Awesome to keep blogs as living documents, especially highly referenced topics like this one.

[marcysutton]

Great question about the blockquote. It's variable throughout docs / blog posts, so I made an update to remove the blockquote but keep the note. Let me know if that works better...?

[marcysutton]

Thanks for the reviews! I don't know what's going on with the Gatsby Build Service, but given it's an update to a pre-existing Markdown file I'm going to go ahead and merge it.

[gatsbot]

Holy buckets, @marcysutton — we just merged your PR to Gatsby! 💪💜

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. We’ve got Gatsby t-shirts, stickers, hats, scrunchies, and much more. (You can also unlock even more free swag with 5 contributions — wink wink nudge nudge.) See gatsby.dev/swag for details.
2. We just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. Accept the invite by visiting https://github.com/orgs/gatsbyjs/invitation. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again!