Website Accessibility Basics for a Small Business Site

Website accessibility means people can perceive, understand, navigate, and interact with the site, including people with vision, hearing, movement, speech, or cognitive disabilities. A badly built page creates barriers the way a step at a door does. The useful part for a small business is that the same fixes also help people on a phone, in bright sun, or on a slow connection [1].

What does website accessibility cover?

The W3C describes web accessibility as design that works across hardware, software, language, and ability. It includes auditory, cognitive, neurological, physical, speech, and visual disabilities, and it also helps people with a temporary limit such as a broken arm or lost glasses [1]. It is not a plugin you add the week before launch. WAI's own advice is to build it in from the start, because fixing it later means redoing work.

Which standard are people referring to when they say WCAG?

WCAG 2 is the shared technical standard from the W3C Web Accessibility Initiative. WCAG 2.2 has 13 guidelines under four principles: perceivable, operable, understandable, and robust. Conformance is decided by testable success criteria at levels A, AA, and AAA. Later versions add criteria. They do not rewrite the old ones, and W3C encourages using the latest version [2]. WCAG is the standard for people who need a technical bar. It is not the beginner introduction.

Does this apply to an ordinary shop or clinic, or only to government sites?

In the United States, the Department of Justice has long said the ADA applies to state and local government services on the web and to businesses open to the public, including retail, banks, hotels, medical offices, and restaurants. The March 2022 guidance says a site with inaccessible features can block access to those goods and services. The Department does not, in that guidance, set one detailed technical regulation, and it points to WCAG and the Section 508 standards as helpful guidance while still requiring access [3]. This is not a substitute for legal advice about your own business.

What are the barriers that show up on a normal small-business page?

The Justice Department lists the ones that keep appearing: poor color contrast, using color alone to mark a required field, images with no text alternative, videos without captions, forms without labels or error messages, and controls that only work with a mouse [3]. WAI uses the same short list in plainer language. An image without alt text is invisible to a screen reader. A control that needs a mouse locks out anyone using a keyboard or speech input. Audio without a transcript leaves out anyone who cannot hear it, and it also leaves the words out of search [1].

• Contrast — light gray text on a light background fails people with low vision.
• Color alone — a red border with no word like "required" fails anyone who cannot see that red.
• Alt text — say what the image is for, in a short line, not a keyword list.
• Captions — synchronized captions that name the speakers.
• Keyboard — every action that a mouse can do should have a key path.

Is alt text an SEO trick or an access fix?

It is an access fix that search engines also read. WAI says equivalent alt text makes the image available to people who cannot see it and to technologies that cannot see images, including search engines [1]. Google's image guidance says alt text is the most important metadata for an image, and stuffing it with keywords is a bad experience that can look like spam [4]. Write the sentence you would say if you had to describe the picture to a customer on the phone.

Can a scanner or an overlay finish the job?

No. WAI says evaluation tools help, and no tool alone can decide whether a site meets the guidelines. A person who knows what they are looking at still has to evaluate it [5]. The Justice Department says the same thing in plainer terms: a clean automated report does not mean the site is accessible, and a few reported errors do not always mean a real barrier. Pair the tool with a manual check [3].

When should you check?

Early, and again while the site is being built. WAI's evaluation overview says finding problems during design is cheaper than repairing them after launch [5]. You can do a rough pass yourself even if you are not technical. Their Easy Checks are written for that first look. A full conformance evaluation, using something like WCAG-EM, is a heavier pass for when you need to know whether the site actually meets the criteria.

What should you not do to "hide" an unfinished accessible version?

Do not block the real pages in robots.txt and call that a fix. Google's robots.txt introduction says a disallow does not keep a page out of search results if other sites link to it. The URL can still show up, just without a description [6]. To keep a page out of results you use a different method, such as noindex or a password. Accessibility and indexing are different jobs. The public page still has to work for people.

Where does this sit in a normal website project?

Put it in the build, not in a later retrofit. Headings that are real headings, labels on fields, alt text on photos, and a keyboard path through the menu are ordinary website development work. The same pages still have to be usable on a phone, and the photos still need the care described in which photos a small site needs. If the site is already up and brittle, maintenance is where those fixes keep from sliding backward.

What is a sensible first pass this month?

Tab through the homepage, the menu, and one form using only the keyboard. Look at one photo and ask whether the alt text would make sense read aloud. Play one video with the sound off and see if the captions carry it. Zoom the text and see if it still fits. Those are the checks WAI and the Justice Department both describe as understandable without a specialist [3]. A full WCAG audit can follow. The first pass tells you whether the obvious doors are shut.