Accessibility

Last updated: September 8, 2026

My commitment

A website that some people cannot use is an unfinished website, and finishing is the whole point of this business. actuallycoded.com 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 on this site

• Semantic HTML with landmark regions and a single, meaningful 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: smooth scrolling and reveal animation are switched off for visitors who ask for that, and no content ever depends on an animation completing.
• A responsive layout that remains usable when zoomed to 200% or viewed on a small phone, with no horizontal scrolling.
• Real text set in self hosted typefaces, never text baked into images, so your own text settings apply.
• Labelled form fields in the brief, with helper text linked to each field, and a status message announced to screen readers when the button is pressed.

Accessibility in the sites I sell

Every one-page site delivered by actuallycoded gets the same checks before it is handed over: heading order, keyboard operation, focus visibility, colour contrast, alternative text, reduced motion, and zoom. This is part of the product, not an extra. I will not describe a page as fully conformant unless it has actually been tested to that standard, and I will tell you plainly if something in your own content, such as a supplied image with text in it, is a barrier I cannot remove without your help.

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 audit team. The fictional concept pages are built to the same standard as this page but are demonstrations, and their non-functional demo forms are labelled as such for assistive technology. If you hit something that does not work, I want to hear about it, and a report is treated as a defect to fix.

Back to actuallycoded