Web Accessibility Basics: A WCAG Starter Guide for Teams
What WCAG 2.2 asks for in plain terms, and the contrast, keyboard, alt text, form and structure checks a design and development team can start running this week.

Most accessibility problems on a website come from a short list of causes: text too pale to read, controls that cannot be reached without a mouse, images with no description, form fields with no label and pages with no real structure. Web accessibility basics are the habits that remove those causes during design and build, where they cost very little to get right.
This guide explains enough of WCAG to plan the work, then lists the checks a team can start running this week. It is not legal advice, and it will not make anyone an auditor.
What WCAG is and which version to work to
The Web Content Accessibility Guidelines (WCAG) are published by the World Wide Web Consortium (W3C). The current version is WCAG 2.2. W3C encourages teams to use the newest published version, and content that meets 2.2 also meets 2.1 and 2.0, so new work has no reason to target an older one. WCAG 3 exists only as an early draft.
The guidelines sit under four principles. Content has to be:
- Perceivable: people can see or hear it, or get an equivalent (text for images, captions for video, enough contrast).
- Operable: every function works with a keyboard and other inputs.
- Understandable: labels, instructions and error messages make sense, and the interface behaves predictably.
- Robust: the markup is clean enough for browsers and assistive technology, such as screen readers, to interpret.
Under the principles are testable success criteria, each at one of three levels: A, AA and AAA. Most policies and contracts that mention WCAG ask for Level AA, which includes Level A. The W3C overview of WCAG links to the full text.
Color and contrast are decided in the design file
Contrast is cheap to fix before development and tedious to fix after. At Level AA, normal text needs a contrast ratio of at least 4.5:1 against its background, and large text (18 point, or 14 point bold) needs at least 3:1. The same 3:1 minimum applies to the parts of the interface people must see to use it: input borders, icons that carry meaning, the focus indicator.
Check every text and background pair in the brand palette once and record the pairs that pass in the style guide. The usual failures are light gray body text, placeholder text, white text on a brand color and text laid over photographs.
Color also cannot be the only signal. A field that turns red needs an error message in words, and a link inside body text needs an underline.
Everything has to work from the keyboard
Screen reader users, people with limited movement and people using switch devices all depend on the keyboard interface. Put the mouse aside and use Tab, Shift+Tab, Enter, Space, the arrow keys and Esc. Four things must hold:
- You can reach and operate every link, button, menu, tab and form field.
- You can always see where you are. If the stylesheet contains
outline: nonewith no replacement, focus is invisible. - Focus moves in the order the page reads and never gets stuck inside a widget.
- The focused element is not hidden behind a sticky header, a cookie banner or a chat bubble. That check arrived with WCAG 2.2.
Most keyboard failures come from building controls out of div and span elements with click handlers. A real button is focusable, responds to Enter and Space and announces itself as a button. Use ARIA attributes only when HTML has no element for the job.
A visible focus style takes a few lines of CSS:
:focus-visible {
outline: 3px solid #1a4fd6;
outline-offset: 2px;
}
Add a "Skip to content" link as the first focusable element. In a modal dialog, focus should move in when it opens, stay inside, and return to the opening button when the dialog closes, including on Esc. WCAG 2.2 also sets a minimum size of 24 by 24 CSS pixels for most pointer targets, which matters for icon buttons on phones.
Text alternatives for images, icons and media
Every image needs an alt attribute, and what goes in it depends on what the image does:
- Informative image: describe what it shows that the surrounding text does not. Skip "image of".
- Decorative image: use an empty attribute,
alt="", so screen readers skip it. With the attribute missing, many screen readers read out the file name. - Image that is a link or a button: describe the destination or the action ("Search", "Download the brochure"), not the picture.
- Chart or diagram: give a short alternative and put the data or the conclusion in the text nearby.
An icon-only button has no name unless you give it one, with visually hidden text or an aria-label. Video needs captions and audio needs a transcript. In a CMS, alt text is the editor's job as much as the developer's, so make it part of publishing.
Forms need labels, clear errors and input purpose
A form someone cannot complete is a lost inquiry or order. The essentials:
- Every field has a visible
labelelement tied to its input. A placeholder is not a label: it disappears when typing starts and usually fails contrast. - Errors appear in words next to the field, say how to fix the problem and are linked to the input so a screen reader announces them.
- Fields that collect personal details carry the right
autocompletevalue, so browsers and password managers can fill them in.
A field in its error state:
<label for="email">Work email</label>
<input id="email" name="email" type="email" autocomplete="email"
aria-describedby="email-error" aria-invalid="true">
<p id="email-error">Enter an email address like name@example.com.</p>
WCAG 2.2 added two form rules worth knowing. Do not make people re-enter information they already gave earlier in the same process, and do not make login depend on a memory or puzzle test with no alternative. In practice: allow paste in password fields and offer a way past any puzzle-style CAPTCHA. On a WordPress site the form plugin produces this markup, so inspect its output and treat gaps as WordPress form development work, not styling.
Headings, landmarks and zoom
Screen reader users move around a page by jumping between headings and regions, which only works when the structure is real. Use one h1 for the page title, then h2 and h3 in order, chosen for meaning and not for font size. Wrap the page regions in header, nav, main and footer, set the page language on the html element and give every page a unique title.
Link text should make sense when read alone, because assistive technology can list all the links on a page. Ten links that say "Read more" tell the listener nothing.
Then zoom. Text should stay usable when enlarged to twice its size, and at Level AA ordinary content should reflow into one column at a width of 320 CSS pixels without sideways scrolling.
How to test without being an auditor
A first pass over one page template is short work. Go in this order:
- Keyboard only. Tab through the whole page, open every menu and dialog and submit the form.
- Zoom. Enlarge the page to twice its size, then narrow the window to phone width.
- Automated scan. Run a checker such as axe DevTools, WAVE or the accessibility audit in Lighthouse. These catch missing alt attributes, missing labels and contrast failures.
- Screen reader. Listen to the page with NVDA on Windows, VoiceOver on macOS and iOS, or TalkBack on Android.
- Break the form on purpose. Submit it empty and with bad data, and check that each error is announced and explained.
Automated tools find only part of the problem. W3C says plainly that tools can assist in an evaluation but cannot determine accessibility by themselves, and that human judgment is required. A tool can tell you an image has alt text. It cannot tell you the text is useful. W3C's Easy Checks page describes a similar first review in more detail.
Putting web accessibility basics into practice
Start with shared components, not individual pages. The header, navigation, buttons, form fields and dialogs appear everywhere, so fixing them once fixes most of the site. Keep approved color pairs and focus styles in a design system so they are reused, not reinvented.
A team can handle everything above alone. Get help when you are planning a redesign and want accessibility built into the UI and UX design work from the first wireframe, when the templates need structural repair (on a WordPress site that is theme development), or when a customer, a tender or a regulator asks for evidence, which means an audit by someone who tests with assistive technology. WCAG 2.2 AA is a standard we build and test to when a client asks for it, and testing against a standard is not a legal sign-off. Whether a particular law applies to you, and what it requires, is a matter for your own legal counsel.
Frequently asked questions
Is WCAG a law?
No. WCAG is a technical standard published by W3C. Laws, regulations and procurement rules in many countries refer to it, usually at Level AA, but which rule applies to your organization and which version it names depends on where you operate and whom you serve. Put that part to your legal counsel.
Should we aim for Level A, AA or AAA?
Level AA is the usual target. WCAG itself notes that requiring Level AAA across entire sites is not recommended as a general policy, because some content cannot satisfy every AAA criterion.
Can a plugin or an overlay make a site accessible?
Plugins and scanners help you find problems, and some fix specific ones, such as adding a skip link. They cannot write meaningful alt text, restructure headings or rebuild a custom dropdown so it works with a keyboard. A toolbar that changes font size or colors does not repair the markup underneath.
Add worldwincoder.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.
