Skip to content
Inclusivity.org
Digital Accessibility

Website Accessibility Checklist for Inclusive Businesses in 2026

18 min read

A business can say it welcomes everyone and still accidentally lock people out.

That happens when a website has pale gray text on a white background. Or a contact form that cannot be completed with a keyboard. Or an event flyer posted as an image with no readable text. Or a “Book Now” button that looks beautiful but has no accessible name for screen reader users.

Accessibility is not a side issue for inclusive businesses. It is the front door.

In 2026, this matters even more because the web is getting heavier, more visual, more automated, and more complicated. WebAIM’s 2026 analysis of the top one million home pages found that 95.9% had detected WCAG 2 failures, and the most common issues were still basic problems: low contrast text, missing image alt text, missing form labels, empty links, empty buttons, and missing document language.

That is the opportunity. Most websites are not failing because accessibility is impossible. They are failing because simple things were skipped.

This guide gives inclusive businesses, directories, nonprofits, local organizations, and website teams a practical checklist they can use before launch, after launch, and before claiming a site is accessible.

What website accessibility means

Website accessibility means people with disabilities can perceive, understand, navigate, and use your website.

That includes people who are blind or have low vision, Deaf or hard of hearing, neurodivergent users, people with mobility disabilities, people with cognitive disabilities, people using screen readers, people using voice control, people using keyboards instead of mice, older adults, people with temporary injuries, and people on small screens or slow connections.

Accessibility is not only about screen readers. It is about whether real people can complete real tasks.

For a business website, that means people can:

  • Read your pages
  • Understand what you offer
  • Navigate without getting trapped
  • Use forms and filters
  • Contact you
  • Book, buy, donate, subscribe, or apply
  • Understand your prices, policies, and hours
  • Access important documents
  • Use the site on mobile
  • Recover when something goes wrong

The 2026 accessibility baseline

The practical baseline for most websites is WCAG Level AA. WCAG stands for Web Content Accessibility Guidelines. WCAG 2.2 is the current W3C recommendation and builds on WCAG 2.1 and 2.0.

A useful way to think about WCAG is not as a scary legal checklist, but as a shared language for accessible digital experiences.

Standard or framework What it means for a business website
WCAG 2.2 The current W3C accessibility standard to use when improving or updating a site.
WCAG 2.1 AA Still referenced in many policies, contracts, and rules.
ADA Title II web rule Applies to state and local governments; DOJ extended compliance dates in 2026.
ADA Title III Applies to many public-facing businesses, but does not yet have the same specific federal website technical rule as Title II. Legal risk still exists.
Section 508 Applies to federal agencies and certain federal digital content.
Human testing Essential because automated tools catch only part of the problem.

Important note: This article is not legal advice. For legal requirements, talk with a qualified attorney or accessibility specialist. For practical website improvements, start here.

The quick accessibility checklist

Use this table as the fast version. The deeper sections below explain each item.

Area What to check Good signal Risk signal
Color contrast Text against backgrounds Body text is easy to read in normal light Pale gray text, text over photos, low-contrast buttons
Alt text Meaningful images Images that add meaning have useful alt text Every image has generic alt text like “image” or “photo”
Headings Page structure One clear H1, logical H2/H3 sections Headings used only for visual size
Links Link text Links make sense out of context “Click here,” “read more,” empty icon links
Buttons Button labels Every button has a clear action Icon-only buttons without accessible names
Forms Labels and errors Every input has a visible label and helpful error Placeholder-only labels, vague errors
Keyboard access No mouse required Users can tab through and operate the page Menus, filters, popups, or sliders trap keyboard users
Focus states Visible keyboard focus Focus indicator is obvious Focus ring removed for aesthetics
Mobile Touch and zoom Tap targets are large enough and layout reflows Tiny buttons, horizontal scrolling, zoom blocked
Videos Captions/transcripts Captions for speech and transcripts for key content Auto-playing video with no captions
PDFs Accessible documents Important PDFs are tagged or converted to HTML Scanned PDFs, image-only menus, unreadable flyers
Language HTML language set Page language is declared Screen readers guess the wrong language
Motion Animations Motion can be paused or reduced Auto-moving content, flashing, no controls
Directory filters Search and filter controls Filters are labeled and keyboard-friendly Fancy filters that only work with a mouse
Testing Manual and automated Automated scan plus keyboard/screen reader review “We installed a widget, so we’re compliant”

1. Start with readable text

Readable text is the foundation. If people cannot read the page, the rest of the design does not matter.

Common problems include pale text, thin fonts, text over busy images, low-contrast buttons, and small body copy. These are often design choices, not technical failures.

Checklist

  • Use strong contrast between text and background.
  • Avoid light gray text for paragraphs.
  • Avoid placing important text directly over busy photos.
  • Make body text large enough to read comfortably.
  • Use generous line height.
  • Do not rely on color alone to communicate status, error, or category.
  • Check buttons, badges, form errors, captions, navigation links, footer links, and disabled states.

Better pattern

Instead of putting white text directly over a photo, use a dark overlay, solid content card, or gradient mask that gives the text enough contrast.

2. Write alt text that actually helps

Alt text is the text alternative for an image. It helps people who use screen readers understand what the image means or does.

The goal is not to describe every pixel. The goal is to communicate the image’s purpose in that context.

Image type What to do Example
Decorative image Use empty alt text: alt="" A background swirl or decorative divider
Informative photo Describe the meaning briefly “Owner Maria Chen standing inside her bakery.”
Product image Describe the product and key detail “Reusable tote bag with rainbow stripe design.”
Linked image Describe the destination or action “View Pride gift guide.”
Chart or infographic Provide short alt text plus nearby data/table “Bar chart comparing application approval rates by year.”
Logo Identify the organization “Inclusivity.org logo.”

Avoid these alt text mistakes

  • “Image”
  • “Picture of image”
  • Keyword-stuffed alt text
  • Alt text that repeats the caption word-for-word
  • Leaving meaningful images blank
  • Giving decorative images long descriptions
  • Using AI-generated alt text without checking it

Alt text is also a trust signal for inclusive directories. If a business profile has owner photos, storefront photos, product images, menus, and gallery images, those images should not be invisible to people using assistive technology.

3. Use headings as structure, not decoration

Headings help everyone scan a page. They are especially important for screen reader users, who often navigate by heading.

A page should have one clear H1 and then logical sections beneath it.

Good structure

H1: LGBTQ-Owned Restaurants Near Me
  H2: What counts as LGBTQ-owned?
  H2: How to find restaurants near you
    H3: Search local LGBTQ chambers
    H3: Check certified business directories
  H2: How to verify ownership respectfully
  H2: FAQ

Bad structure

H1: LGBTQ-Owned Restaurants Near Me
H4: What counts as LGBTQ-owned?
H2: FAQ
H5: Search tips
H1: Related guides

Headings should not jump around just because a designer likes a certain font size. Use CSS for styling and heading tags for structure.

4. Make links specific

People using screen readers can pull up a list of links on a page. If the links all say “click here,” “read more,” or “learn more,” the list becomes useless.

Weak link Better link
Click here Browse LGBTQ-owned business certification guide
Learn more Read the supplier diversity checklist
View View Black-owned restaurants near me
More See accessibility-forward business profile examples

This also helps SEO and conversions. Specific links are better for everyone.

5. Label every form field

Forms are where accessibility often breaks the business goal.

A person may be able to read your entire website and still be unable to submit a quote request, claim a profile, join a directory, RSVP to an event, or ask for help.

Checklist

  • Every input has a visible label.
  • Do not rely on placeholder text as the only label.
  • Required fields are clearly marked.
  • Error messages explain how to fix the problem.
  • Error messages are connected to the field programmatically.
  • Inputs use appropriate autocomplete attributes when helpful.
  • CAPTCHA has an accessible alternative.
  • Users can submit the form with a keyboard.
  • Confirmation messages are clear.

Better error message

Weak: “Invalid.”

Better: “Enter a phone number with area code, such as 407-555-0142.”

6. Test everything with a keyboard

Keyboard access is one of the quickest ways to find accessibility problems.

Unplug your mouse or trackpad. Use Tab, Shift + Tab, Enter, Space, and arrow keys.

Can you:

  • Open the navigation menu?
  • See where focus is at all times?
  • Use dropdown menus?
  • Close popups?
  • Submit forms?
  • Use filters?
  • Move through cards?
  • Open and close galleries?
  • Skip repeated navigation?
  • Avoid getting trapped?

If the answer is no, the site is not accessible enough.

7. Keep focus visible

Some websites remove the browser’s default focus outline because designers think it looks unattractive. That creates a major barrier for keyboard users.

A visible focus indicator is like a cursor for people who navigate without a mouse.

Better focus design

  • Use a clear outline or ring.
  • Make the focus state visible on buttons, links, form fields, cards, menus, and filters.
  • Make sure sticky headers, cookie banners, chat widgets, and popups do not cover focused elements.
  • Test focus on mobile menus and modals.

WCAG 2.2 added more attention to focus visibility, target size, dragging movements, and accessible authentication, which makes this especially timely for modern websites.

8. Make mobile accessible, not just responsive

A site can look responsive and still be inaccessible.

Mobile accessibility includes readable text, large tap targets, accessible menus, labels, focus order, zoom support, and avoiding gestures that require precision.

Checklist

  • Users can zoom without breaking the layout.
  • Tap targets are large enough and not crowded.
  • Menus work with screen readers and keyboards.
  • Sticky elements do not cover content.
  • Forms are not painful to complete on phones.
  • Error messages are visible near fields.
  • Filters and maps are usable without fine motor precision.
  • No important action requires dragging only.

This is especially important for directories. Many people search “near me” categories on phones while standing in a neighborhood, planning an event, or looking for a business immediately.

9. Caption videos and provide transcripts when needed

If your website uses video, make sure users who cannot hear the audio can still understand the content.

Checklist

  • Caption videos with speech.
  • Do not rely on auto-captions without review.
  • Provide transcripts for long informational videos, interviews, webinars, and tutorials.
  • Do not auto-play audio.
  • Give users controls to pause, stop, mute, or replay.
  • Make video players keyboard accessible.

For inclusive businesses, captions are not just a compliance issue. They also help people watching in noisy spaces, quiet spaces, classrooms, offices, and public places.

10. Do not hide important content inside images or PDFs

A common local business mistake is posting important information as an image: a menu, pricing sheet, event flyer, hiring notice, sale announcement, or service list.

That can exclude people using screen readers. It can also hurt SEO.

Better approach

  • Put the essential information in real HTML text.
  • Use the image as visual support, not the only source.
  • Add alt text if the image communicates meaning.
  • If a PDF is necessary, make it accessible.
  • Avoid scanned PDFs for critical information.

11. Use accessible language and content structure

Accessibility is not only code. It is also content.

Inclusive content should be easy to read, organized, and respectful.

Checklist

  • Use plain language where possible.
  • Explain acronyms on first use.
  • Break long sections into headings.
  • Use bullet lists for steps.
  • Avoid walls of text.
  • Use tables only for data, not layout.
  • Make calls to action specific.
  • Avoid shame-based language.
  • Avoid identity assumptions.
  • Define certification terms clearly.

A page can technically pass many automated checks and still be confusing. Good content is part of accessibility.

12. Make directory filters accessible

People should be able to filter by location, ownership type, certification status, accessibility features, business category, employer rating, price range, and service options without needing a mouse or perfect vision.

Directory filter checklist

Feature Accessibility requirement
Search field Clear label, helpful placeholder, keyboard accessible
Checkbox filters Visible labels, logical grouping, screen reader support
Sort controls Clear current state and options
Map/list toggle Works without relying only on map pins
Results count Announces or displays updated result count
Cards Structured headings, readable badges, clear links
Load more Keyboard accessible and preserves focus sensibly
No results state Gives helpful next steps
Location permission Does not require location sharing to search manually
Badges Explained with verification definitions

Maps can be helpful, but never make them the only way to browse results.

13. Explain accessibility claims honestly

Do not say “fully accessible” unless you have evidence and ongoing maintenance.

Better claims are more specific:

  • “Designed to follow WCAG 2.2 AA best practices.”
  • “Keyboard-tested main navigation and forms.”
  • “Captions provided for all original videos.”
  • “Accessibility review completed July 2026.”
  • “If you experience a barrier, contact us at...”

This is more trustworthy than vague badges.

14. Test with automated tools and real people

Automated tools are useful, but they cannot prove a site is accessible. They can catch many common issues quickly, especially contrast, missing alt attributes, missing labels, empty links, and structural problems.

Manual testing is still needed for meaning, usability, keyboard flow, screen reader experience, cognitive clarity, and whether people can actually complete tasks.

Minimum testing stack

Test What it catches
Automated scan Detectable WCAG issues like contrast, labels, empty links
Keyboard test Menus, focus, modals, forms, traps
Screen reader spot-check Reading order, labels, headings, buttons
Mobile test Tap targets, zoom, layout, sticky elements
Content review Plain language, headings, link clarity
User feedback Real barriers automated tools miss

Recommended recurring testing

  • Before launch
  • After major design changes
  • After adding plugins, ads, maps, forms, or chat tools
  • After new templates are created
  • Quarterly for important websites
  • Whenever users report barriers

15. Watch third-party tools

Your website may be accessible until a third-party script breaks it.

Common risky elements include:

  • Chat widgets
  • Popups
  • Cookie banners
  • Review widgets
  • Social embeds
  • Maps
  • Appointment schedulers
  • Payment widgets
  • Ad units
  • Sliders/carousels
  • Accessibility overlays

Ask vendors direct questions:

  • Is the widget keyboard accessible?
  • Has it been tested with screen readers?
  • Does it meet WCAG 2.1 or 2.2 AA?
  • Can users pause motion?
  • Does it trap focus?
  • Does it inject unlabeled buttons?
  • Can we test it before launch?

16. Create an accessibility statement

An accessibility statement helps users know what you are trying to do, how to report barriers, and when the site was last reviewed.

A good statement should include:

  • Your accessibility goal
  • The standard you are working toward
  • Date of last review
  • Known limitations, if any
  • Contact method for accessibility help
  • Response commitment
  • Alternative access option when possible

Avoid pretending everything is perfect. Honest, responsive accessibility is more credible than polished claims with no support.

17. Build accessibility into publishing workflows

Accessibility fails when it depends on one developer at launch.

Every person who touches the site needs a simple role-based checklist.

Role Accessibility responsibilities
Writer Headings, plain language, link text, alt text notes
Designer Contrast, focus states, layout, touch targets
Developer Semantic HTML, labels, keyboard support, ARIA only when needed
Editor Accessible tables, captions, embeds, source clarity
Business owner Accurate access details, contact options, document updates
Directory admin Verification labels, accessible filters, profile structure

Common accessibility mistakes to fix first

Start with the problems most likely to block users and hurt trust.

Priority Fix
1 Low-contrast text and buttons
2 Missing labels on forms
3 Empty buttons and icon-only controls
4 Navigation menus that do not work by keyboard
5 Missing alt text on meaningful images
6 Vague link text
7 Inaccessible PDFs and image-only flyers
8 Popups that trap users
9 Missing captions on videos
10 No accessibility contact path

FAQ

Is website accessibility only for large companies?

No. Small businesses, nonprofits, local directories, churches, schools, event teams, and independent professionals all benefit from accessible websites. Accessibility helps more people use your site and reduces avoidable friction.

Does installing an accessibility widget make my site accessible?

No. A widget may provide some user controls, but it does not replace accessible design, code, content, testing, or maintenance. If the underlying site has broken forms, missing labels, poor structure, or inaccessible documents, a widget cannot reliably fix everything.

What accessibility standard should a small business use?

A practical goal is WCAG 2.2 AA when updating or building a site. Some legal or contractual obligations may reference WCAG 2.1 AA. WCAG 2.2 is backward compatible with 2.1 and 2.0, so it is a good current target.

Can automated accessibility tools prove compliance?

No. Automated tools are helpful, but they only catch some problems. You still need manual testing, keyboard testing, content review, and ideally feedback from people who use assistive technologies.

What is the fastest accessibility improvement for most websites?

Improve color contrast, label forms, fix empty buttons and links, add useful alt text to meaningful images, restore visible focus states, and make sure navigation works with a keyboard.

Should accessibility be part of SEO?

Accessibility and SEO are not the same, but they overlap. Clear headings, descriptive links, readable content, alt text, fast pages, and crawlable HTML often help both users and search engines.

External sources and further reading

Own or know an inclusive business?

List it free so people can discover it year-round — with a source you control.

List your business