Blog
Accessibility basics for a small-business website
October 23, 2026 · 5 min · Neil Black
- accessibility
- WCAG
- small business
Someone reaching a local business may be on a phone, reading enlarged text, or listening to the page. The W3C introduction to web accessibility (opens in a new tab) says people with disabilities can perceive, understand, navigate, interact, and contribute. It also lists people on a small screen, older people, a broken arm, bright sunlight, and a slow connection, and it says many sites still have barriers that make them difficult or impossible for some people to use. It also says the law requires web accessibility in many situations.
WCAG 2.2 (opens in a new tab) is the latest version W3C encourages. Content that meets it also meets WCAG 2.1 and 2.0. Easy Checks (opens in a new tab) is a short first review, and it says a page can seem to pass while serious barriers remain. The introduction says no tool alone can decide that a site meets the guidelines. Check the homepage and the page where someone calls or writes.
Name the page
Page Titled (opens in a new tab) (2.4.2, level A) says each title describes that page's topic or purpose. Easy Checks says a screen reader announces it on arrival, and that the tab, bookmarks, and search results show it. Make the homepage, services, and contact titles different, with the unique words first. Easy Checks' better inner pages start with About or Contact. A visible heading has to be a real heading. Easy Checks wants one on the page, and it strongly suggests an outline that starts at the top and does not skip levels. See Info and Relationships (opens in a new tab) (1.3.1, A) and Headings and Labels (opens in a new tab) (2.4.6, AA).
Describe the image
Non-text Content (opens in a new tab) (1.1.1, A) asks for a text alternative with the same purpose as the image. A screen reader reads it from the page code. Easy Checks gives a search button the text "search", and treats "magnifying glass" as a name for the icon. Put the business name in the logo's alternative when the logo shows it. A chart gets a short name, with the numbers written nearby. Decoration can use an empty alt="", so a screen reader skips it. Easy Checks asks whether removing the image would remove information. Skip "image of", "button", and "link".
Check contrast, then add a second cue
Contrast (Minimum) (opens in a new tab) (1.4.3, AA) requires at least 4.5:1 for ordinary text and images of text. Large text, 18 point or 14 point bold, can be 3:1. W3C says not to round: 4.499:1 fails 4.5:1. Logo text is exempt, and so is a street sign that happens to be in a photo. A brand color on a sentence still has to meet the ratio. Non-text Contrast (opens in a new tab) (1.4.11, AA) asks for 3:1 on a control or a meaningful icon. Inactive controls are exempt. W3C says 2.999:1 does not meet 3:1.
Use of Color (opens in a new tab) (1.4.1, A) says color cannot be the only cue. Its passing form explains required fields in words, uses red, and adds an icon. The WebAIM Contrast Checker (opens in a new tab) reports the ratio for two colors. WCAG 2.2 still uses those 4.5:1 and 3:1 ratios. Check the phone number and any words on a photo.
Let the text grow, on a phone too
Resize Text (opens in a new tab) (1.4.4, AA) says text can reach 200 percent without losing content or function. Captions and images of text are excepted. Easy Checks says the words should not disappear, overlap, or need sideways scrolling to finish a sentence. Reflow (opens in a new tab) (1.4.10, AA) says vertical content is readable at 320 CSS pixels wide without that sideways scroll. W3C equates 320 CSS pixels with a 1280 CSS pixel layout at 400 percent zoom. A map, video, or table may still scroll both ways.
Use the keyboard, and size the tap
Keyboard (opens in a new tab) (2.1.1, A) says functionality works from a keyboard, with no required timing on a keystroke. Freehand drawing is the exception. From the address bar, Tab through every link, field, and button in reading order. Easy Checks flags anything that works only on hover. No Keyboard Trap (opens in a new tab) (2.1.2, A) says you can leave each component again. If that takes more than Tab or the arrow keys, the page explains the exit. Focus Visible (opens in a new tab) (2.4.7, AA) requires an indicator you can see, one that stays visible, at the 3:1 contrast used for controls.
Target Size (Minimum) (opens in a new tab) (2.5.8, AA) asks for at least 24 by 24 CSS pixels. A smaller target can pass if a 24 CSS pixel circle around it misses other targets. Links inside a sentence are exempt, and the page lists more exceptions. It still recommends 24 CSS pixels. Call, the menu, and Submit can aim for the AAA size of 44 by 44 CSS pixels (opens in a new tab) (2.5.5).
Label the field, and name the error
Labels or Instructions (opens in a new tab) (3.3.2, A) covers every field that accepts input, optional ones included. The label is on the page for everyone, not only for a screen reader. The labeling tutorial (opens in a new tab) puts it left of or above a text field, and to the right of a checkbox, and says most users prefer or even need it visible. Easy Checks puts "required", and any unusual format such as a date pattern, in the label. Color alone is not the cue. Instructions go at the top of the form.
Error Identification (opens in a new tab) (3.3.1, A) says the error is identified and described in text. W3C's example "Email is not valid" does that. "Please provide a valid email address in the format name@domain.com" also meets Error Suggestion (opens in a new tab) (3.3.3, AA), which asks for a known correction unless it would jeopardize security or the field's purpose. Easy Checks calls it good practice to keep what was already typed, aside from sensitive data such as a card number.
Let people stop motion
Pause, Stop, Hide (opens in a new tab) (2.2.2, A) covers motion that starts by itself, lasts more than five seconds, and runs beside other content. Offer pause, stop, or hide, unless the motion is essential. Auto-updating content needs that control, or control of how often it updates. Designing for Web Accessibility (opens in a new tab) asks for a visible control on a carousel or on sound that starts alone. The accessibility principles (opens in a new tab) describe captions and a transcript for spoken or filmed material.
Run the pass
Open the homepage and the contact page in WAVE (opens in a new tab). WebAIM says it finds many WCAG errors and leaves the judgment to you.
Titles differ, unique words first
Informative images have a text alternative
Text is at least 4.5:1, controls at least 3:1
Text at 200 percent wraps, including at 320 CSS pixels
Tab reaches every control, and focus stays visible
Labels stay visible, and errors are written in textEasy Checks calls this a start. WCAG-EM (opens in a new tab) is W3C's method for a full review. How to Meet WCAG 2 (opens in a new tab) lists every criterion. The offer and the phone number still have to appear promptly, which is the check in Why page speed matters.
Where to read it
- Introduction to Web Accessibility (opens in a new tab), the WCAG 2 overview (opens in a new tab), and Easy Checks (opens in a new tab).
- Designing for Web Accessibility (opens in a new tab), the labeling tutorial (opens in a new tab), How to Meet WCAG 2 (opens in a new tab), WAVE (opens in a new tab), the contrast checker (opens in a new tab), and WCAG-EM (opens in a new tab).
The accessibility statement records the WCAG 2.2 AA aim for this site and the known limits. For a pass on a page you already publish, write to the studio and send the link.