Accessibility
Accessibility
We aim to meet WCAG 2.2 AA. Tell us when we fall short.
Report a barrier
Contact us with the page and the issue; we'll respond and fix it.
How to report a barrier
Tell us the page, what you were trying to do, and the device, browser or assistive technology you were using. That detail helps us reproduce the problem and fix it properly. We review every report and will reply with what we changed or when to expect a fix.
Read next: · Corrections
Content choices
We write in plain language, use descriptive link text instead of 'click here', and keep headings in a logical order so each guide can be skimmed or navigated by heading. Tools such as the planner and checklist work with a keyboard.
Read next: Build vs. Buy · Moving to Kannapolis
What we've built in
- Semantic headings and landmarks so screen readers can navigate each page.
- Descriptive text for images, all labeled as AI-generated where they are.
- Keyboard-reachable navigation and visible focus states.
- Text and background colors chosen for readable contrast.
Read next: · Editorial Policy