Accessibility.
Last updated: August 26, 2026
The short version
- This site targets WCAG 2.1 Level AA.
- It works with a keyboard, with a screen reader, and when you zoom or reduce motion.
- Found a barrier? Email me and I will fix it. No form required.
My commitment
A website that some people cannot use is an unfinished website. cfwebdev.net is built to be usable by as many people as possible, including people who navigate by keyboard, use a screen reader or magnifier, need larger text, or prefer reduced motion.
The standard I aim for
This site targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That is the benchmark commonly referenced in relation to the Americans with Disabilities Act and adopted widely for public-facing websites.
What is in place
- Semantic HTML structure with landmark regions and a single, meaningful page heading order.
- A skip link so keyboard users can jump straight to the main content.
- Full keyboard operability, with a visible focus indicator on every interactive element.
- Text and interface colours checked against WCAG AA contrast ratios on the site's dark palette.
- Descriptive alternative text for meaningful images, and decorative graphics hidden from assistive technology.
- Accessible names on navigation, buttons, and links, so their purpose is clear out of context.
- Support for
prefers-reduced-motion, so animation is reduced for visitors who ask for that. - Responsive layout that remains usable when zoomed or viewed on small screens, with no horizontal scrolling traps.
- System fonts and real text rather than text baked into images, so your own text settings apply.
Known limitations
I test with keyboard navigation, browser zoom, automated tooling, and manual review. I do not claim perfection, and I do not employ a full-time accessibility audit team. Portfolio concept pages and older archived demo pages may not meet the same standard as the main site. If you hit something that does not work, I want to hear about it, and treating a report as a defect is part of how this site is maintained.
Accessibility in client work
Accessibility QA is part of the Lead Page Sprint and is applied to the pages I build. For an existing site I did not build, I can report and fix issues within the agreed scope, but a full remediation of a large site is a separate engagement. I will not claim a site is fully conformant unless it has actually been tested to that standard.
Report a barrier
If any part of this site is difficult or impossible to use, tell me what happened and what you were using (browser, device, assistive technology if any). I aim to respond within 5 business days and will provide the information in another format if that is what you need.
Email: calebseft@gmail.com