You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here are a few considerations that should at least be acknowledged, and possible changed, prior to the initial import of the handbook onto Make Accessibility Team's P2.
Confirm that the following page found in production is deliberately omitted in GitHub: Site Feedback Guide. If so, does it warrant an redirect or is it just gone?
Confirm that the slug for the "Accessibility Guidelines" page is changing from "which-questions-should-you-as" to "accessibility-guidelines". (It makes sense, but we'll want to add a redirect.)
Inconsistent page title casing in the manifest. Most pages only capitalize the first letter and proper names, some capitalize all (or most) words. I'd lean towards the former (affects both the title in the manifest and in each page's markdown):
"Profile Badges" → "Profile badges"
"Accessibility Audits and testing" → "Accessibility audits and testing"
Presumably all content differences between the current handbook and the GH handbook are intentional, so I haven't gone so far as comparing the content.
Nothing above is a blocker, but they are worth addressing ahead of time (if needed). Any needed redirects would be the most beneficial thing to have sorted before importing.
Yes, we want to remove Site Feedback Guide because how to test for accessibility is already written down in the knowledge base and the whole point of the project is to avoid duplicated content.
I've replied to #17 with the proposed redirects code. Looks like this particular issue can now be closed. Once the redirects are signed off on, let me know when you'd like me to proceed with importing the handbook.
Activity
rianrietveld commentedon Sep 22, 2026
@coffee2code Thanks for your review 🌷
Aswering your questions:
@joedolson did a review on the content itself, so that is good to go.
I will create a PR for the changes and a new issue with list of redirects. I will close #2 as you know how redirects are done.
rianrietveld commentedon Sep 22, 2026
@coffee2code I've created issue #17 with a list of redirects.
If you tell me how, I can create a PR for this.
cc @joedolson
coffee2code commentedon Sep 24, 2026
I've replied to #17 with the proposed redirects code. Looks like this particular issue can now be closed. Once the redirects are signed off on, let me know when you'd like me to proceed with importing the handbook.
rianrietveld commentedon Sep 25, 2026
Thanks @coffee2code for reviewing.