Accessibility Statement
Last updated: April 6, 2026
CodeWalkers is committed to making our content accessible to everyone, including people with disabilities. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, the international standard for web accessibility.
Our Commitment
We believe technical content should be available to everyone. Accessibility is part of how we design, write, and ship every page on this site — not an afterthought. We treat accessibility issues as bugs and prioritize them alongside other defects.
Conformance Status
CodeWalkers is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not yet fully conform to the standard. We are actively working to improve conformance.
Accessibility Features
The site includes the following accessibility features:
- Keyboard navigation — every interactive element can be reached and operated with the keyboard alone
- Skip links — press Tab on any page to reveal "Skip to main content" and "Skip to navigation" shortcuts
- Visible focus indicators — keyboard focus is clearly visible on every interactive element
- Semantic HTML landmarks — every page uses proper
<header>,<nav>,<main>, and<footer>regions for screen reader users - ARIA labels — navigation regions and interactive controls are labelled for assistive technology
- Reduced motion support — animations and transitions are
automatically minimised for users who set
prefers-reduced-motion: reducein their operating system - High-contrast text — body text on the site exceeds the WCAG AAA contrast ratio of 7:1 against the background
- Responsive design — content reflows cleanly at 320px width and zoom levels up to 400% without loss of functionality
- Alt text — all meaningful images have descriptive alternative text
- Heading hierarchy — articles use a logical
h1,h2,h3structure with no skipped levels
Known Limitations
Despite our best efforts, some content on the site may not yet meet WCAG 2.1 AA in full. Known limitations include:
- Code blocks — syntax-highlighted code uses colours that may not meet 4.5:1 contrast for every token type. We rely on Shiki's default themes; we are evaluating higher-contrast variants.
- Embedded third-party content — when we embed external content (videos, GitHub gists, social media posts), the accessibility of that content depends on the third-party provider.
- Older articles — some legacy articles may have alt-text gaps or heading-hierarchy issues that we are working through. If you find one, please report it.
- Light mode — the site is currently dark-mode only by design. A light theme is on our roadmap.
Browser and Assistive Technology Support
The site is tested to work with:
- The latest versions of Chrome, Firefox, Safari, and Edge
- VoiceOver on macOS and iOS
- NVDA and JAWS on Windows (limited testing)
- TalkBack on Android (limited testing)
Reporting Accessibility Issues
We welcome feedback on the accessibility of CodeWalkers. If you encounter a barrier, please let us know — we treat accessibility reports as priority bugs.
- Email: hello@codewalkers.com with the subject line "Accessibility issue"
When you report an issue, please include:
- The URL of the page where you encountered the problem
- A description of what went wrong
- The browser and assistive technology you were using (if relevant)
We aim to acknowledge accessibility reports within five business days.
Assessment Approach
CodeWalkers assesses the accessibility of the site using a combination of:
- Automated testing with Lighthouse, Axe DevTools, and Pa11y
- Manual keyboard-only navigation testing
- Screen reader spot-checks (VoiceOver)
- Contrast checks against the WCAG 2.1 AA thresholds
Formal Complaints
If you are not satisfied with our response to an accessibility report, you may also raise the issue with the relevant accessibility regulator in your country. In the United States, the Department of Justice ADA information line can provide guidance.
Contact
For accessibility questions or feedback, contact us at hello@codewalkers.com.