Professional Accessibility Audit Prep
A founder planning page for preparing Ask Uncle G for a future professional accessibility review. No audit has been completed.
No audit has been completed
- ▸This is not a professional audit
- ▸This does not certify accessibility
- ▸This does not confirm WCAG compliance
- ▸No professional audit has been completed as of this writing
- ▸This is a prep checklist for a future qualified reviewer only
What to Prepare for an Auditor
Route list
- Provide the auditor with the full list of 208 routes (available via /all-guides and /route-seo-review)
- Group routes into: public help guides, tools/calculators, accessibility review pages, founder/private tools
- Highlight which routes are public-facing and which are founder/private-preview only
- Note any routes that share the same component template (library pages)
Priority user flows
- Help Finder: user selects situation type and finds the right guide
- Safety First: user describes warning signs and receives safety level assessment
- Checklist Library: user filters, opens, checks off, copies, and prints a checklist
- Display Settings: user turns on large text, contrast, and reduced motion
- Emergency Readiness: user navigates to emergency plan from the homepage
Accessibility review pages
- Share the full list of accessibility review pages (/accessibility-quick-check and related)
- Explain that these are founder/private review tools — not professional audits
- Confirm the auditor should prioritize the public-facing pages, not the founder tools
- Provide the Screen Reader Review, Landmark Review, Form Label Review as context documents
Known limitations
- Not professionally audited yet — this prep page documents the intent
- Mobile screen reader testing is still manual founder/private review
- Some grouped controls may not use fieldset/legend HTML yet
- No public accessibility feedback form exists yet
- Display preferences are not saved cross-device
- No multilingual accessibility support
Safety-critical pages
- Safety First (/safety-first) — emergency stop and call-a-pro assessment
- Emergency Readiness (/emergency-readiness-planner) — family/home emergency plans
- Home Systems (/home-systems) — electrical, water, leak triage
- Repair Simulator Lab (/repair-simulator-lab) — danger scenario decisions
- Safety page (/safety) — when to call a professional
Forms and validation messages
- Help Finder form (/help-finder) — select inputs with labels
- Safety First form (/safety-first) — checkbox groups and results
- Calculator inputs — labeled with visible units
- Display Settings toggles — on/off state, visible labels
- All form validation messages should be reviewed for clarity and plain language
Print and large print behavior
- Checklist Library print and copy functions (/checklists)
- Large Print Starter Packs (/large-print-starter-packs)
- Print Center (/print-center) — overview of printable content
- Safety disclaimer text should be verified to survive printing
Privacy and sensitive-information warnings
- Home Records planner pages — privacy warnings about not entering private data
- Senior Accessibility planner — warnings about not entering medication details
- Senior Family Help — scam call safety page
- Privacy Records Safety Guide (/home-records-planner/privacy-records-safety-guide)
- All review pages remind users what NOT to enter
Priority Route Groups
Share these groups with the auditor to orient their review.
Homepage / Start Here / Help Finder / Safety First
Checklist Library / All Guides / Print Center
Accessibility Settings / Reading Comfort / Quick Check
Keyboard / Screen Reader / Focus Order
Landmark / Form Label / Icon Button
Error Message / Fieldset Legend / ARIA
Emergency Readiness / Senior Support / Home Systems
Public Readiness / Route SEO / Sitemap
Questions for the Auditor
Are heading levels logical and sequential across all priority pages?
Are landmark regions clear — header, main, footer, nav?
Are forms understandable — visible labels, helper text, logical order?
Are warning and error messages accessible — text only, not color alone?
Can users complete key flows with keyboard only?
Are privacy warnings visible and clearly worded?
Are emergency warnings understandable via screen reader?
Are there screen reader blockers — unlabeled controls, empty links?
Are mobile touch interactions accessible and usable?
What must be fixed before public launch to prevent harm?
Are any safety-critical warnings hidden or relying on icon/color only?
Are there any redundant or conflicting ARIA attributes?
What Not to Send to an Auditor
Passwords or PINs
Private account information
Medical details, medication names, or dosages
User data or personal records
Private church or member records
Customer records or contact lists
Insurance, legal, or tax documents
Financial account or banking information
Social Security Numbers or government IDs
What this page does not claim
- ✗No audit has been completed
- ✗No accessibility certification is granted
- ✗No legal compliance approval is given
- ✗No public launch certification is given
- ✗No WCAG compliance is confirmed
Professional Accessibility Audit Prep Checklist
0/15Next Readiness Steps