Chykalophia Docs

What web accessibility means, why it matters for every website, and what WCAG 2.1 AA requires — explained in plain English.

Web accessibility means making your website usable by as many people as possible — including people with disabilities. This covers people who are blind or have low vision, people who are deaf or hard of hearing, people with motor disabilities, and people with cognitive differences like ADHD or dyslexia.

Accessibility is both the right thing to do and, in many contexts, a legal requirement.

Quick summary

An accessible website can be used by everyone, regardless of disability. The international standard is WCAG, and most sites aim at Level AA (of WCAG 2.1, or of the newer WCAG 2.2). Key requirements include alt text for images, sufficient color contrast, keyboard navigation, captions for video, and readable, well-structured content.

What is WCAG?

WCAG stands for the Web Content Accessibility Guidelines. It is the international standard for web accessibility, published by the W3C (the World Wide Web Consortium — the organization that sets web standards).

The latest version is WCAG 2.2, first published in October 2023 and updated in December 2024. It doesn't retire WCAG 2.1: both are current standards, and content that meets 2.2 also meets 2.1. The target level most websites aim for is Level AA, and that's the level accessibility laws and policies usually point to. In the US, the Justice Department's 2024 rule for state and local government sets WCAG 2.1 Level AA; in the UK, public sector bodies are told to check their sites against WCAG 2.2.

Level AA is achievable for most websites with careful planning.

Who does accessibility help?

More people than you might expect. Globally, at least a billion people — around 15% of the world's population — have a recognized disability, and that number grows as populations age. On a website, that includes:

People who use screen readers (software that reads content aloud)
People who navigate with a keyboard only (can't use a mouse)
People with color blindness
People with motor disabilities who use switch controls or eye-tracking
People with ADHD, dyslexia, or autism who benefit from clear, structured content
People in bright sunlight who struggle with low-contrast text
People with slow internet connections
People on small screens

Many accessibility improvements benefit everyone — not just people with diagnosed disabilities.

The four WCAG principles

WCAG organizes its guidelines under four principles. An accessible site must be:

1. Perceivable

Information must be presentable in ways all users can perceive.

Images have alt text
Videos have captions — a transcript is a useful addition, not a replacement for them
Text has sufficient color contrast against its background
Content doesn't rely solely on color to convey meaning

2. Operable

Users must be able to interact with the interface.

All functionality is available from a keyboard (not mouse-only)
Nothing flashes more than three times per second (can trigger seizures)
Users have enough time to complete tasks
Navigation is consistent and predictable

3. Understandable

Users must be able to understand content and interface.

Language is identified in the page code (so screen readers use the right voice)
Error messages are helpful and specific
Navigation is consistent
Labels on forms are clear

4. Robust

Content must be interpreted reliably by assistive technologies.

HTML is valid and well-structured
Interface components are properly labeled for assistive technologies

What this means for your content

As a website owner, the accessibility areas most within your control are:

Alt text for all informational images — see Alt text explained
Color contrast — see Color contrast & readability
Captions for video — see Using video on your website
Clear, plain-language content — structured with proper headings and short paragraphs
Meaningful link text — not "click here" — describing what the link goes to
Accessible PDFs — see PDFs & documents on your site

The technical accessibility of your site's code — keyboard navigation, semantic HTML, ARIA labels — is something we handle when we build and maintain your site.

Is accessibility legally required?

In many cases, yes. The US Department of Justice's position is that the ADA (Americans with Disabilities Act) applies to the goods and services a business open to the public offers online, not just in person. For businesses, the Department has not issued a regulation setting out detailed technical standards, so you have some flexibility in how you comply — its guidance points to WCAG as a helpful reference. For state and local government, a 2024 Justice Department rule does set a standard: WCAG 2.1 Level AA.

We build sites to WCAG 2.1 AA. This page is general information, not legal advice — if you have specific compliance questions, speak with a legal professional familiar with digital accessibility law.

Common questions

Does accessibility make my site look worse?

No. Good accessibility practice and good design practice overlap significantly. High-contrast text is easier to read for everyone. Clear headings help everyone navigate. Alt text helps search engines as well as screen readers. Accessibility usually improves the experience for all users.

Can I get sued for an inaccessible website?

In the United States, yes. Organizations of all sizes have faced complaints, and the Justice Department has itself sued over inaccessible web content. Prevention (building accessibly from the start) is much cheaper than remediation after a complaint.

No. The Justice Department's own web guidance says automated checkers and overlays "can be helpful tools, but ... they need to be used carefully", and that a clean report from one does not necessarily mean everything on a site is accessible. An overlay sits on top of the problem rather than fixing the code and content underneath, so we don't recommend one as a substitute for building accessibly.

Need a hand?

If you're stuck, email support@chykalophia.com and we'll help. Include your website address and a screenshot if you can.

Web accessibility basics