MDN React Tutorials #6: Accessibility & Resources

[mxmason]

Description

Following #31093, as part of mdn/mdn#474, this PR makes some modifications to the sixth and seventh pages in our "Getting started with React" tutorial.

---

Do not merge this until #31093 has been merged and you have updated this PR with mdn main and checked for breakages.

[github-actions]

Preview URLs

• /en-US/docs/Learn/Tools_and_testing/Client-side_JavaScript_frameworks/React_accessibility
• /en-US/docs/Learn/Tools_and_testing/Client-side_JavaScript_frameworks/React_resources

External URLs (13)

URL: /en-US/docs/Learn/Tools_and_testing/Client-side_JavaScript_frameworks/React_resources
Title: React resources

• https://jestjs.io/ (1 time) (Note! This may be a new URL 👀)
• https://react.dev/learn/extracting-state-logic-into-a-reducer (1 time) (Note! This may be a new URL 👀)
• https://react.dev/learn/react-developer-tools (1 time) (Note! This may be a new URL 👀)
• https://react.dev/learn/state-a-components-memory (1 time) (Note! This may be a new URL 👀)
• https://react.dev/learn/synchronizing-with-effects (1 time) (Note! This may be a new URL 👀)
• https://react.dev/reference/react/Component (1 time) (Note! This may be a new URL 👀)
• https://reactrouter.com/ (1 time) (Note! This may be a new URL 👀)
• https://testing-library.com/docs/react-testing-library/intro/ (1 time) (Note! This may be a new URL 👀)
• https://testingaccessibility.com/implications-of-client-side-routing (1 time) (Note! This may be a new URL 👀)
• https://vitest.dev/ (1 time) (Note! This may be a new URL 👀)
• https://www.smashingmagazine.com/2020/05/styling-components-react/ (1 time) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Learn/Tools_and_testing/Client-side_JavaScript_frameworks/React_accessibility
Title: Accessibility in React

• https://react.dev/reference/react/useEffect (1 time) (Note! This may be a new URL 👀)
• https://reactjs.org/docs/hooks-faq.html (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2023-12-21 12:01:48)

[mxmason]

A two-for-one special to close us out, @chrisdavidmills! Mostly some little line edits, but I called out some notable stuff.

[chrisdavidmills]

Great work as always @mxmason! I've worked through the whole tutorial and all is working well. I've got some comments for you here, but nothing too major.

[mxmason]

Back to you, @chrisdavidmills!

[chrisdavidmills]

@mxmason lovely work! Just a few more changes/suggestions for you to consider. Very close now!

[mxmason]

Back to you @chrisdavidmills! As I said, I'm on my phone so pardon the mess – I just wanted to get this back to you ASAP.

[chrisdavidmills]

@mxmason OK, changes made, and approving!

Have another look at the updated usePrevious() description, and let me know if you are happy. I mostly used your wording.

[mxmason]

This looks great, @chrisdavidmills! I'm good to move on with this if you are.

I assume that mdn/todo-react#97 blocks this series of content PRs, so I'll do my best to get to your notes today. I'm also fine with merging and releasing this content, if you'd prefer.

And, of course, I'm happy to do one final sweep over all this content after we merge, just to make sure it's all tidy. I'm just excited to get this out! 😁

[chrisdavidmills]

This looks great, @chrisdavidmills! I'm good to move on with this if you are.

I assume that mdn/todo-react#97 blocks this series of content PRs, so I'll do my best to get to your notes today. I'm also fine with merging and releasing this content, if you'd prefer.

And, of course, I'm happy to do one final sweep over all this content after we merge, just to make sure it's all tidy. I'm just excited to get this out! 😁

Faaaantastic.

Ideally, I'd like the demo repo to be updated before we merge the content, but I don't see that as an absolute dealbreaker as long as it is merged soon after. As you've seen on the other repo, I'm having trouble there because I don't have the privs to merge on that repo. If I don't find someone who does in the next 30 mins or so, I'm going to go ahead anyway and merge the content.

[chrisdavidmills]

@mxmason And with that, your work is all merged, and the job is complete. It should go live on MDN in about 24 hours, possibly sooner. As soon as that happens, I'll give everything a read-through and get ready to file a PR to fix any minor bits we may have missed.

Great work though! It has been a pleasure working with you again. I hope you have a restful festive period.

[chrisdavidmills]

@mxmason your updates are live! I'll give them a good read through now, and see if I can spot any typos. Let me know if you spot any, and I'll add them into a PR of fixes.