All components page created for accessibility testing

[SMakaiTakori]

Pull Request Background

The work in this pull request was created as a proof of concept for our accessibility tests. One main components page was created, incorporating all components and then tests were run across the entire page.

GitHub Issue

Build Accessibility test page

What Changed

• Created a new md file all-components.md that includes all components on one page, located at the URL /components/all-components
• Updated accessibility tests to run on the new main accessibility page

How to Check Change

• [ ] Make sure server is running at localhost:8000 and run npx cypress run in the command line to run accessibility tests set up for the /components/all-components page. They should be passing.
• [ ] Run sh ./ci/linter.sh to run linter tests. They should be passing.

Automated Testing

I created a new accessibility test in the Cypress spec file. This tests the new page that holds all components at /components/all-components

• [x] All node tests are passing.
• [x] All linter tests are passing.
• [x] All accessibility tests are passing.

Additional Context

In the spec file, I commented out the accessibility tests that were created previously for the array of component URLs. I think future devs may benefit from seeing the example but this is open to discussion.

[netlify[bot]]

✅ Deploy Preview for bloom-guides-template ready!

Name	Link
🔨 Latest commit	7d4710816f1285b05e01c045134218ebcbafb7ac
🔍 Latest deploy log	https://app.netlify.com/sites/bloom-guides-template/deploys/64b6e86c0d37e00008c83a23
😎 Deploy Preview	https://deploy-preview-55--bloom-guides-template.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[SMakaiTakori]

@LynnHerrick9 and @jeffmaher This is ready for review when you have time. Thank you!