a11y-for-teams: merge guide sections into single pages

[nick-mon1]

Summary

Sets up the accessibility for teams guide navigation, page structure, content cleanup and changes to be consistent with existing digital.gov guides.

• Setup index (f32aeb6ca4bd230d5e60c9342ee57385500e4902) and guide navigation (c782025f681bac9e75d5e666faa8df99ea7f65b9)
• Merged sub-pages into single pages for each directory (daae57a33a7f81b31226775363b2dcf10c176ac2)
• All pages are formatted to the simplest plain text (no text based shortcodes) for content review (ceff11913b829a4a2d249fec6af1852df05ebb12, f0534e1ae8692bf06023f7e1cdeff1ccfd9e60b7)
• Refactored youtube short code to set video start time (381941036fa023d8dcc56526b660a3e499fc6423)
• Added summary-box component to each guide page (507d6596d5b4f5642bdcca7bad760072db7377de)

[!NOTE] All pages have combined the wcag 2.0 references items into the resources list except for the visual design page for comparison

[!NOTE] Refer to the epic PR for merge order

Preview

Preview

Content Review

• [ ] review content
  • [x] @bonnieAcameron
  • [ ] @mejiaj
  • [x] @clmedders
  • [ ] @ToniBonittoGSA
• [ ] content enhancements documented (in progress)

Content Review Checklist

• front matter fields are consistent with other guides/site
• header hierarchy is consistent
• youtube video is embedded into page, waiting on #7339 to merge into this pr
• wcag, voiceover instructions, and why it's important are moved into bulleted list format
• wcag list is merged with resources list as one except on the visual design page for comparison

---

Dev Checklist

• [x] PR has correct labels
• [x] A11y testing (voice over testing, meets WCAG, run axe tools)
• [x] Code is formatted properly

[clmedders]

Overall everything is looking good... i do have a question or something to spark conversation. Should we add the same instruction for PC for screen the way we do Mac? I know they are a bit different but worth asking if we need to list both? or maybe just direct folks to the docs or steps from each provider?

[nick-mon1]

Migrate accessibility.digital.gov to a guide on digital.gov

[nick-mon1]

Overall everything is looking good... i do have a question or something to spark conversation. Should we add the same instruction for PC for screen the way we do Mac? I know they are a bit different but worth asking if we need to list both? or maybe just direct folks to the docs or steps from each provider?

Fair point, I have added to this to our future enhancements document.