ADA website accessibility for Florida small businesses: a 15-minute self-check
Ten checks you can run on your own site, what scanners miss, and who fixes what: owner, designer, developer or vendor. Not legal advice.
Most owners hear about ADA website accessibility for a small business in one of two ways: a customer says they could not use the site, or a letter arrives. Neither is a good moment to learn what the term means. This guide gives you a short, practical self-check you can run on your own site today, explains what the results mean in plain English and shows who is normally responsible for fixing each kind of problem.
It is written for businesses in St. Augustine, Palm Coast and Flagler County, where many customers are visitors on phones or older residents who rely on larger text and simple navigation. It is not legal advice. For questions about your legal obligations, talk to an attorney.
What accessibility covers, briefly
An accessible website is one that people with disabilities can use: people who are blind or have low vision, people who cannot use a mouse, people who are deaf or hard of hearing, and people who need more time or simpler layouts. The Americans with Disabilities Act is the law most often cited. The Web Content Accessibility Guidelines, known as WCAG, are the technical benchmark most developers and auditors work to.
We explain the background, including how the ADA and WCAG relate, in our longer plain-English ADA and WCAG guide for Florida small businesses. This post picks up where that one stops: with hands-on checks and a clear split of who fixes what.
Ten quick checks you can run yourself
You do not need special software for these. Use your own site, a laptop and your phone.
- Put the mouse away. Press Tab repeatedly from the top of your homepage. Can you reach the menu, every link, every button and the contact form, in a sensible order?
- Watch for the focus outline. While tabbing, you should always see which item is selected. If the highlight disappears, keyboard users are lost.
- Open and close the menu with the keyboard. Dropdowns and mobile menus are a frequent failure point.
- Zoom the browser to 200 percent. Text should reflow and stay readable. Nothing should overlap or get cut off.
- Read the page in bright sunlight on your phone. Pale gray text on white, or text laid over a busy photo, fails for many people.
- Check images for alt text. Right-click an important image, choose Inspect and look for a meaningful alt description.
- Fill out your own form. Every field needs a visible label, not only placeholder text that vanishes when you type. Submit it empty and see whether the error messages say what to fix.
- Play your videos with the sound off. Are there captions? Does anything start playing on its own?
- Open your PDFs. Menus, brochures and intake forms saved as scanned images cannot be read by a screen reader.
- Read your link text out of context. A page with six links that all say “click here” tells a screen reader user nothing.
Write down what failed and on which page. That list is the start of a real plan, and it makes any conversation with a developer shorter and clearer.
What automated scanners catch and miss
Free browser tools such as WAVE and Google Lighthouse flag missing alt text, low contrast, unlabeled form fields and missing page language. They are worth running. They cannot tell you whether alt text is accurate, whether the tab order makes sense or whether a booking flow can be completed without a mouse. A clean scan is a good sign, not proof.
The same caution applies to accessibility overlay widgets, the small toolbar icons that promise to fix a site with one line of code. They can add helpful controls, but they do not repair the underlying code, and a widget on its own should not be treated as a finished job.
Who fixes what
Accessibility problems fall into four groups, and each has a different owner. Sorting your list this way stops everything from landing on one person.
Content: the business owner or whoever updates the site
- Alt text for new photos.
- Headings used in order, as an outline rather than for decoration.
- Descriptive link text.
- Captions for videos you publish.
- Real text instead of flyers and menus posted as images.
Design: your designer
- Color contrast between text and background.
- Text size and spacing.
- Buttons and links large enough to tap.
- Visible focus styles.
Code: your developer
- Keyboard access to menus, sliders, pop-ups and accordions.
- Form labels, error messages and field instructions.
- Proper page structure, landmarks and page titles.
- Pop-ups that can be closed from the keyboard and do not trap the user.
Third-party tools: the vendor, with your developer
- Online booking and reservation widgets.
- Scheduling, payment and chat tools.
- Embedded maps, review feeds and social feeds.
Third-party tools deserve a second look. A restaurant in the historic district of St. Augustine may have an accessible site and a reservation widget that cannot be used with a keyboard. A medical office in Palm Coast may have a clean site and an intake form that is a scanned PDF. A vacation rental manager in Flagler Beach may depend on a booking engine they do not control. In each case, ask the vendor for their accessibility documentation, and offer a phone number or email as an alternative way to complete the task.
A sensible order for fixes
You do not have to fix everything in a week. Work in the order that removes the biggest barriers first.
- First: anything that blocks a task entirely, such as a contact form, booking flow or menu that cannot be used with a keyboard.
- Second: contrast, text size and alt text on your most-visited pages.
- Third: PDFs, videos and older blog posts.
- Ongoing: a short check whenever you add a page, a plugin or a new tool.
Add an accessibility statement with a phone number and email address, so anyone who hits a barrier can reach a person. It does not replace the fixes, but it gives customers a way through while the work is under way.
When a self-check is not enough
A self-check finds the obvious problems. A full audit tests with screen readers, reviews templates and code, and produces a prioritized list of issues against WCAG. Consider one if your site handles bookings, payments or patient information, if you have received a complaint, or if the site is due for a rebuild anyway. No one can guarantee that a website will never draw a complaint, and no honest provider will promise it. What an audit and remediation do is remove real barriers and show a good-faith, documented effort.
Our ADA website compliance and accessibility services page explains how we audit and remediate. If the site is older, it is often more practical to build accessibility into a new design than to patch an old one. Our website redesign in St. Augustine page and our Palm Coast website design page describe that route. Ongoing care matters too, because plugin updates and new content can undo earlier fixes; see website maintenance and hosting.
Every project is scoped individually. If you would like help reading your self-check results, request a quote and send us the list.
Frequently asked questions
Does the ADA apply to my small business website?
Courts and regulators have treated websites of businesses open to the public as covered in many cases, but how the law applies to a specific business is a legal question. This article is not legal advice; an attorney can advise you on your obligations.
What is WCAG?
WCAG stands for Web Content Accessibility Guidelines. It is a published set of technical standards for making web content usable by people with disabilities, and it is the benchmark most audits and developers work to.
Can I check my website for accessibility myself?
Yes, for the basics. Keyboard-only navigation, zoom, contrast, alt text, form labels, captions and PDFs can all be checked without special tools. A full audit goes further and tests with screen readers and against the complete guidelines.
Will an accessibility plugin or overlay make my site compliant?
Not on its own. Overlay widgets can add helpful controls, but they do not repair the underlying code or content. Real fixes are made in the site itself.
Who is responsible for accessibility, me or my web developer?
Both. Developers and designers handle code, structure and contrast. Whoever updates the site handles alt text, headings, link text and captions. Vendors are responsible for the tools they supply, and you choose which tools to use.
Can anyone guarantee my website will not receive an ADA complaint?
No. No one can guarantee that. Auditing and fixing barriers reduces real problems for real customers and documents a good-faith effort.