Evaluator evidence · Clear Path concept
Accessibility is treated as an operating requirement.
This page records design intent, code-level implementation, and suggested verification for this portfolio demonstration. It does not claim formal WCAG conformance, certification, or testing by people with disabilities.
Target: WCAG 2.2 Level AA. Status: implementation evidence is present; full automated, manual, assistive-technology, content, and user testing would be required before a production conformance statement.
Implemented in the theme
- Semantic header, navigation, main, and footer landmarks
- A keyboard-visible skip link and high-contrast focus indicator
- Responsive block layouts designed to reflow without horizontal scrolling
- Relative, fluid type and spacing that tolerate zoom and text resizing
- Reduced-motion and forced-colours media-query support
- Help actions described in text, not by colour or icon alone
- External-destination and demo-mode warnings before consequential actions
- System and locally available fonts only; no remote requests or trackers
Form design evidence
- Visible labels remain present; placeholders are not used as labels
- Required status and instructions appear before input
- Programmatic input purpose supports browser autofill where relevant
- Errors are associated with fields and summarized for screen-reader and keyboard users
- Status messages use live-region semantics without stealing focus
- Demo mode prevents persistence and email delivery, with an explicit warning
- Real 24/7 support remains available without completing a form
Verification still required
- Automated scans across representative templates and form states
- Keyboard-only completion at mobile and desktop widths
- Screen-reader checks with current browser and assistive-technology pairs
- 200% and 400% zoom, text spacing, reflow, and orientation checks
- Contrast review in all authored and editor-customized states
- Error prevention and recovery with realistic tasks
- Usability research with people with disabilities and people with lived experience
Content and trauma-informed safeguards
What this concept does
- Uses non-judgmental, choice-preserving language
- Separates confirmed service facts from prototype recommendations
- Keeps real help visible before optional forms or external tools
- Avoids casino imagery, autoplay, deceptive quick-exit controls, and simulated chat
What production work must add
- Partner validation for Indigenous service content
- Verified language, interpretation, relay, and accommodation details
- Content governance, plain-language review, and service-owner approvals
- Privacy, security, threat, and production data-flow assessments
Evidence boundary: the claims above describe observable code and content decisions in this demonstration. They are not a substitute for an accessibility audit or a production accessibility statement.