Skip to content

Home / Blog / Website Accessibility Checklist

Web Development

Website Accessibility Checklist for Small Business: WCAG Basics You Can Check Today

An accessible website works for people who use screen readers, keyboards, zoom or voice control, and it is easier for everyone else too. This checklist covers the basics a small business can check without being a developer. This guide on website accessibility checklist covers what website accessibility means, in plain terms, colour contrast, text size and readability and alt text, images, video and audio.

By Ragnar Studio's18 October 20269 min read
Abstract illustration of a website on a laptop with a checklist, colour contrast swatches, a keyboard and a magnifier

A website accessibility checklist for small business starts with a simple idea: every visitor should be able to read your pages, move around them and complete the actions you care about, such as calling, booking or buying. Accessibility is about real people, including those with low vision, hearing loss, motor difficulties, dyslexia or a temporary injury, and also anyone using a phone in bright sunlight.

A website accessibility checklist helps you check whether people with different abilities can use your site. Working through a website accessibility checklist is a practical step even for a small business.

This guide uses the Web Content Accessibility Guidelines, usually called WCAG, as its reference. We stay general on legal points, since rules differ by country and business type. Related reading and services: website launch checklist, UI and UX design mistakes to avoid, Core Web Vitals for small business websites, website redesign and website design and development.

What website accessibility means, in plain terms

Accessibility means designing and building a site so that people with different abilities can use it. WCAG, published by the W3C, organises this around four ideas, often shortened to POUR: content must be perceivable (people can see or hear it), operable (people can use it with a mouse, keyboard, touch or voice), understandable (the language and behaviour are clear) and robust (it works with assistive technology like screen readers).

WCAG has levels of conformance, commonly called A, AA and AAA. Many organisations aim for AA as a practical target. You do not need to memorise the guideline numbers. The checks below turn those ideas into things you can look at on your own site.

Start your website accessibility checklist with text: use readable font sizes, strong colour contrast and clear headings. These basics solve many problems quickly.

Accessibility also overlaps with good practice you may already want: readable text, clear navigation, fast pages and well-labelled forms. Improvements often help search engines and conversions as well, though we would never promise ranking or sales from accessibility work alone.

Finally, accessibility is a process, not a badge. Sites change, content gets added and plugins update. Plan to re-check after major changes rather than treating it as a one-off job.

Images need alternative text. Every website accessibility checklist includes adding short, descriptive alt text for meaningful images.

Why it matters, and a note on the law

Millions of people live with some form of disability, and many more have temporary or situational limits. If your site is hard to use, those visitors leave, and you may never know why. For a small business, that can be lost bookings or orders.

Many countries have laws or guidance that refer to accessible digital services, and customers or advisers sometimes raise the question with businesses of all sizes. Which rules apply to you depends on where you operate, what you sell and who your customers are. We are not lawyers and this article is not legal advice. If you are worried about obligations, ask a qualified adviser in your country, and treat the checklist below as a practical starting point.

One caution: no tool, plugin or agency can honestly guarantee legal compliance. Automated overlays that promise instant fixes are controversial among accessibility specialists, and they do not replace correct page structure. Fix the underlying site first.

Keyboard access is another item on any website accessibility checklist. Check that you can reach menus, links and buttons using only the Tab key.

A sensible attitude is to make visible, steady improvements, record what you changed and invite feedback. A clear way for visitors to report problems, such as an email address on your contact page, helps you find issues you would miss.

Colour contrast, text size and readability

Low contrast is one of the most common problems on small business sites. Light grey text on white, white text on a pale photo and pastel buttons are hard to read for many people.

  • WCAG AA asks for a contrast ratio of at least 4.5 to 1 for normal body text, and at least 3 to 1 for large text and key interface parts such as button borders.
  • Check your brand colours with a contrast checker. If a colour fails, darken the text rather than abandoning the brand.
  • Do not use colour alone to carry meaning. If errors are red, also say "Error" in words. If links are coloured, underline them or make them clearly different.
  • Keep body text at a comfortable size, commonly 16 pixels or larger, with generous line spacing and short lines.
  • Avoid text inside images. It does not scale, cannot be selected and is invisible to screen readers unless described.
  • Check that the page still works when zoomed to 200 percent, and that text does not overlap or get cut off.

Buttons deserve special attention, since they drive enquiries. Make sure button text is readable against its background, and that the button looks clickable at a glance.

Forms should have visible labels and clear error messages. A good website accessibility checklist treats forms as critical, since they are where enquiries happen.

Want this done for you? Ragnar Studio's builds websites with accessibility basics included, from contrast and alt text to labelled forms. See our website design and development service or get a free quote.

Alt text, images, video and audio

Every meaningful image needs a short text alternative so that screen reader users know what it shows. Good alt text describes the purpose, not just the picture. For a product photo, name the product and key detail. For a photo of your team at work, say who and what. For a logo that links to your home page, "Company name, home" works.

Decorative images, such as background flourishes, should have empty alt text so screen readers skip them. Avoid starting with "image of" or stuffing keywords. Alt text written for people tends to be fine for search engines too.

Link text should make sense out of context. Replace click here with a description, a small fix that belongs on every website accessibility checklist.

For video and audio:

  • Add captions to videos with speech, so deaf and hard-of-hearing visitors, and people watching without sound, can follow.
  • Offer a transcript for important audio.
  • Do not autoplay sound. If a video autoplays, make it muted and easy to pause.
  • Avoid flashing content, which can be harmful to some people.

For charts and infographics, add a text summary nearby that gives the key point, since a picture alone may not be readable to everyone.

Keyboard use and visible focus

Many people cannot use a mouse. They navigate with the keyboard, a switch device or voice control. A simple test: put your mouse aside and try to use your site with the Tab key, Shift plus Tab, Enter and Space.

Video and audio need captions or transcripts. Add that to your website accessibility checklist if you publish media.

As you tab through the page, check that:

  • You can reach every link, button, menu and form field.
  • The order of movement follows the visual order and makes sense.
  • You can always see where you are. A visible outline or highlight on the focused item is essential, so do not remove it with CSS unless you replace it with something clear.
  • Dropdown menus and pop-ups can be opened, closed and escaped with the keyboard, and you are never trapped inside one.
  • A "skip to main content" link lets keyboard users jump past a long menu.

Touch targets matter too. Buttons and links should be large enough to tap accurately on a phone, with spacing so neighbouring targets are not hit by mistake. Sliders and carousels that only work with a swipe or hover are a common problem, and each one should have buttons that work by keyboard as well.

Headings, links and page structure

Screen reader users often scan a page by jumping from heading to heading, much as sighted users skim. Use one main heading (H1) that names the page, then H2s for the main sections and H3s for subsections, without skipping levels for visual effect. Style size with CSS, and use the heading level to describe structure.

Links need meaning out of context. "Click here" and "Read more" repeated ten times tell a screen reader user nothing. Use link text such as "Read our returns policy" or "Book a free consultation".

Use proper heading order, with one H1 and logical H2 and H3 levels. A website accessibility checklist should include structure, because screen readers rely on it.

Other structural basics:

  • Give each page a unique, descriptive title.
  • Set the page language in the code so screen readers pronounce text correctly.
  • Use real lists for lists and real tables for data, with header cells marked.
  • Use landmarks such as header, navigation, main and footer, which most modern themes provide.
  • Write in plain language, with short sentences and defined jargon.

Good structure also helps your page speed, readability and SEO, so this is work that pays off in several ways.

Forms, errors and checkout

Forms are where businesses make money, and where inaccessible sites lose it. Every field needs a visible label placed near it, not just placeholder text that vanishes when typing starts. Programmatically linked labels also let screen readers announce the field name.

Check these points on your contact, booking and checkout forms:

  • Required fields are marked in text, not only with a colour or asterisk with no explanation.
  • Error messages are specific, such as "Enter a phone number with area code", and appear next to the field as well as in a summary.
  • The form can be completed and submitted using only the keyboard.
  • Autocomplete is enabled for name, email, phone and address so browsers can fill them.
  • CAPTCHAs have an alternative, since image puzzles can block users with visual or cognitive difficulties.
  • Time limits are avoided or can be extended.

For online stores, test the whole path: product, basket, address, payment and confirmation. Payment widgets from third-party providers are often reasonably accessible, but test them on your own site, and check that discount codes and shipping choices can be used by keyboard.

How to test your site, with free tools

Combine automated tools with manual checks. Automated scanners find only some issues, often cited as roughly a third to half, so a clean report does not prove accessibility. They are still a good first pass.

CheckWhat you can use
Automated scanBrowser extensions such as WAVE or axe DevTools, and Lighthouse in Chrome
Colour contrastAny contrast checker that reports WCAG ratios
KeyboardTab, Shift plus Tab, Enter, Space and Escape on your own pages
Screen readerNVDA on Windows, VoiceOver on Mac and iPhone, TalkBack on Android
Zoom and reflowBrowser zoom to 200 percent, and a narrow window or phone
Reading levelRead the text aloud and cut long sentences

Even ten minutes with a screen reader on your home page, contact page and checkout teaches a great deal. Test on a real phone, not just a desktop window. If budget allows, ask people with disabilities to try key tasks and tell you what is hard. Paid audits by accessibility specialists are worth considering for larger or regulated sites. Not sure where to start with website accessibility checklist? Email info@ragnarstudio.com and we will point you to the right option.

Common mistakes to avoid

  • Relying on an accessibility plugin or overlay alone. It cannot fix poor structure, missing labels or bad contrast.
  • Removing focus outlines because they look untidy.
  • Putting key information in images, such as opening hours or prices in a banner graphic.
  • Using placeholder text as the only label.
  • Autoplaying video or music, or sliders that move too fast to read.
  • Writing vague link text like "Click here".
  • Testing only on your own laptop, with a mouse, in good light.
  • Treating it as a one-time task and forgetting to check new pages, banners and plugins.

Most of these are cheap to fix when caught early and costly to retrofit across a large site. Building accessibility into design and content from the start is cheaper than repairing it later.

A simple plan for the next month

  1. Week 1: Run WAVE or Lighthouse on your home page, contact page and one product or service page. List the issues.
  2. Week 1: Fix contrast and text size in your brand styles, then add missing alt text.
  3. Week 2: Tab through the site. Restore focus outlines, fix menus and add a skip link.
  4. Week 3: Review headings, link text, page titles and language setting. Label every form field and improve error messages.
  5. Week 4: Test checkout or booking with a keyboard and a screen reader, add captions to videos and publish an accessibility contact email.
  6. Ongoing: Re-check after redesigns or new plugins, and keep a short log of changes.

If you would like help, we can review an existing site and suggest fixes as part of a website redesign or build accessibility basics into a new project from the start. Ask a qualified adviser about any legal requirements that apply to you.

Frequently asked questions

What is WCAG?

WCAG stands for Web Content Accessibility Guidelines, published by the W3C. It sets out how to make web content perceivable, operable, understandable and robust. Many organisations aim for level AA as a practical target, though legal requirements differ by country.

Is my small business website legally required to be accessible?

It depends on your country, sector and customers, so we cannot say for you. Ask a qualified adviser. Whatever the law says, an accessible site is easier for more people to use, and basic fixes are usually inexpensive.

Can an accessibility plugin fix everything?

No. Plugins and overlays can help with small adjustments, but they cannot fix missing labels, poor headings, low contrast or keyboard traps in the underlying site. Fix structure and content first, then consider tools as a supplement, not a replacement.

How do I check colour contrast?

Use a contrast checker that reports WCAG ratios. Enter your text and background colours. For normal text, WCAG AA asks for at least 4.5 to 1, and 3 to 1 for large text. Adjust the text colour if it fails.

What should alt text say?

Describe what the image shows and why it is there, in a short phrase. Skip words like image of, and leave alt empty for purely decorative images. For a linked logo, describe the destination, such as Company name, home page.

How often should I test accessibility?

Test before launch, then after any redesign, new template, plugin change or major content addition. A quick keyboard and automated check each quarter is a sensible habit. Larger sites may benefit from a periodic specialist audit.

Does accessibility help SEO?

Some practices overlap, such as clear headings, descriptive links, alt text and fast, stable pages. These can help search engines understand content, but we cannot promise ranking changes. The main reason to do it is to serve more visitors well.

Accessibility is built from many small, ordinary decisions, and a small business can make real progress in a few weeks. If you would like a second pair of eyes on your site or a new build with these basics included, send us a message and we will reply with a custom quote.

Free quote

Tell us about your project

Fill this short form and send it on WhatsApp. We reply with questions or a quote. Nothing is charged on the website.

  • Takes about two minutes
  • Goes straight to Ragnar Studio's on WhatsApp
  • Prefer email? Write to info@ragnarstudio.com

By sending, you agree that Ragnar Studio's may reply on WhatsApp about this enquiry.

Ready to start your project?

Tell us what you need. We reply on WhatsApp with questions, next steps and a quote.