What it means
Accessibility helps people with a range of visual, hearing, physical and cognitive characteristics use web information and functions. It involves text contrast, meaningful headings, keyboard operation and alternatives for images and audio. W3C’s WCAG is one set of guidelines, but an automated score cannot assess everything. Also check whether people can find the information they need and complete the intended task.
A practical example
Going beyond “red means closed”
If a clinic calendar uses red alone to mark closure days, people who have difficulty distinguishing colors may miss the information. Adding the word “Closed” or an explained symbol provides another cue. Clear contrast on booking buttons and a visible keyboard focus indicator also help people who do not use a mouse.
Before you commission a website
Check text contrast and make sure important meaning is not communicated only through color or visual position.
Use menus, buttons and forms with a keyboard. Check that the current position and any errors are understandable.
Agree the standards, pages and testing methods in scope, then establish how accessibility will be maintained when content changes.
What to watch for
Passing an automated check does not mean everyone can use the website. Instead of relying on claims of “full accessibility,” ask about scope and testing. Recheck the site when text or images are updated.
RELATED VOCABULARY
Related vocabulary, explained
These terms help clarify the details and the decisions you may need to make.
WCAG
The Web Content Accessibility Guidelines from W3C provide testable criteria for making web content more accessible. Success criteria have A, AA or AAA levels.
Specify the version, level and scope being assessed, and also examine real user journeys.
Primary reference · W3C WAI / WCAG overview (opens in a new tab)WCAG Level AA
Level AA is a WCAG conformance level. It requires meeting the A and AA success criteria for the specified version, together with the other conformance requirements.
A few color or text changes do not establish conformance. Assess the defined pages and complete processes, and document the checks.
Primary reference · W3C WAI / Understanding conformance (opens in a new tab)Alternative text (alt)
Alternative text conveys an image’s meaning or function in words, including for screen-reader users. The appropriate description depends on its purpose and context.
Decorative images may need empty alt text. For linked images, describe the link’s purpose rather than appearance alone.
Primary reference · W3C WAI / Images tutorial (opens in a new tab)ARIA attributes
ARIA attributes expose information such as roles, states and accessible names to assistive technology. For example, they can communicate whether a menu is expanded.
Prefer native HTML when it provides the needed behavior. Adding ARIA does not implement keyboard interaction.
Primary reference · W3C WAI / ARIA practices (opens in a new tab)Related vocabulary reviewed: October 13, 2026.
Frequently asked questions
Does accessibility restrict design?
Distinctive design and accessibility can work together. Plan photographs, spacing and color while preserving readable text and clear interaction cues. It is easier to consider these together from the start than to retrofit them after the design is finished.
Is a tool’s accessibility score enough?
Tools can identify useful issues, but human judgment is needed for image descriptions, interaction order and other details. Combine automated checks with keyboard use, screen-reader checks and realistic visitor journeys.
At KOHO
Our approach to readability and usabilityPrimary references
- W3C WAI: Introduction to Web Accessibility (opens in a new tab)
- W3C WAI: Accessibility Fundamentals Overview (opens in a new tab)
References accessed October 6, 2026. Explanations are edited by KOHO for people planning a website. Some linked references are in Japanese.
