Accessibility
Accessibility is part of the structure, not an add-on.
This concept is built toward WCAG 2.2 AA as a practical baseline for a public-facing service website. Final production compliance should include formal testing with the final content and integrations.
Included in this demo
- Semantic headings, landmarks, lists, forms, and navigation
- A keyboard-accessible mobile navigation and visible focus states
- A skip link for keyboard and screen-reader users
- Color choices designed for readable contrast
- Responsive layouts that work at narrow widths and high zoom
- Reduced-motion support for users who request it
- Accessible labels and live regions for interactive tools
- No critical information that depends only on color
Production checklist
Before a real launch, CSNT should test keyboard-only navigation, screen readers, zoom/reflow, PDF accessibility, form error handling, language support, third-party tools, and any embedded maps or social widgets. Accessibility also needs to be preserved during monthly content updates.