AppWT ADA/WCAG Accessibility
Check your own site for accessibility barriers in 10 minutes
This page is a manual self-check, not an automatic scanner, so nothing is uploaded or stored. You use your own keyboard, your browser and the screen reader that is already built into your computer or phone. Each step tells you what a problem looks like when you find one.
01/05Contrast
Text people can read in any light
Every text color gets measured against the 4.5 to 1 ratio WCAG sets for body copy.
02/05Keyboard
Every menu and form, reachable without a mouse
A tester sets the mouse aside and presses Tab through the pages your customers use most.
03/05Screen readers
Buttons that say what they do
Each control is checked out loud with NVDA on Windows and VoiceOver on Apple devices.
04/05Before and after
The barrier, the fix and the re-test
Your report shows what failed, what changed in the code and what the second test found.
05/05Everyone
Built for the way people really browse
Zoom, captions, reduced motion and clear labels help visitors with and without a disability.





The short answer
Is there an automatic accessibility checker on this site?
There is not, by design. This page is a step-by-step guide you run yourself with a keyboard, browser zoom and a built-in screen reader, and it finds many common barriers in about ten minutes. It does not replace a full review, which tests every task in scope against WCAG 2.2 AA and records each result.
01Process
Seven checks you can run right now
Open your home page and your contact form in a second tab. Write down anything that fails, so a reviewer can start there.
Step 1: Put the mouse away and press Tab
Tab moves forward and Shift plus Tab moves back. Can you see where you are every time? Can you reach the menu, open it and send the contact form?
Step 2: Zoom to 200 percent
Press Control and the plus key, or Command and plus on a Mac, until the browser shows 200 percent. Text should not overlap, get cut off or hide behind other content.
Step 3: Shrink the window to phone width
Drag the browser window as narrow as it will go, or open the site on a phone. You should never need to scroll sideways to read a line of text.
Step 4: Turn on a screen reader
On a Mac, press Command and F5 to start VoiceOver. On Windows, press the Windows key, Control and Enter to start Narrator. Then listen as you Tab through the page.
Step 5: Listen to the buttons and links
Each one should say what it does, such as Search or Book an appointment. Hearing only button, link or a file name means that control has no usable name.
Step 6: Send a form with a mistake
Leave a required field empty and press submit. A written message should name the problem near the field, not just a red outline.
Step 7: Play a video
If your site has video with speech, turn on captions. They should match the spoken words and appear in time with them.
02Overview
What a self-check cannot tell you
These steps catch the obvious barriers. A full review goes further in four ways.
Every page and template
A reviewer tests each template and user task in scope, not just the home page and one form.
Exact measurements
Contrast is computed from the rendered colors, and each failure is tied to a specific WCAG success criterion.
Deeper screen reader testing
Passes with NVDA and VoiceOver cover headings, tables, pop-ups and live updates that a quick listen can miss.
A record you can share
The written report shows the state before, the fix and the re-test result for each finding.
03Next step
Found something? Send your notes
Self-check notes give a review a head start. Send them along with the pages you tested.
- Notes are welcome
- Written scope first
04Questions
Questions about the self-check
Do I need special software for this self-check?
Most people need no download at all. Mac computers, iPhones and iPads include VoiceOver, and Windows includes Narrator. Many testers also use NVDA, a free screen reader for Windows from NV Access, which is one of the tools AppWT uses in a full review.
My site passed every step. Does that mean it is accessible?
Passing these steps is a good sign, but it is not proof. The self-check covers a small part of WCAG 2.2 AA and only the pages you tried. A full review tests every task in scope and measures each result against the success criteria, then writes it down.
Why is this a guide and not an automatic scanner?
An automatic scanner can only test what the code reveals, and many real barriers depend on context, such as whether alt text makes sense. A guided manual check teaches you what to look for, and it works on any site, including pages behind a login.