A visitor lands on your website looking for office hours, a service, an event registration, or a way to make a donation. If the menu cannot be used without a mouse, the text disappears into a low-contrast background, or the contact form provides no clear error message, that visitor may never reach the information they need.
Learning how to test website accessibility is one of the most practical ways to protect the usefulness of your website. It helps more people navigate your content, supports stronger usability on mobile and desktop, and catches problems that can quietly cost your organization inquiries, registrations, sales, and trust. For Northern California businesses and nonprofits, accessibility is not a separate technical project. It is part of providing professional, reliable service online.
Start with the pages people rely on most
You do not need to inspect every page at once. Begin with the journeys that matter most to your visitors and your organization: the home page, primary navigation, service or program pages, location and contact details, donation or checkout flows, event registrations, and forms.
Test these pages in the same order a real visitor would use them. Can someone understand what you offer, find the next step, and complete it without unnecessary friction? This approach keeps the work connected to business and mission goals instead of turning accessibility into a disconnected checklist.
Accessibility standards such as the Web Content Accessibility Guidelines, commonly called WCAG, provide a useful framework. Many organizations use WCAG 2.1 or 2.2 Level AA as a practical target. The exact requirements and legal considerations can vary by organization, industry, funding source, and public-facing role, so legal compliance questions should be discussed with qualified counsel. From a website management perspective, the goal is clear: remove barriers before they affect people.
How to test website accessibility with a keyboard
A keyboard test reveals a surprising number of common website issues. Some visitors cannot use a mouse because of mobility limitations. Others use keyboards by preference, assistive technology, or circumstance. If a page only works with a mouse or touch screen, it excludes people.
Open your site in a browser and set the mouse aside. Press the Tab key repeatedly to move through links, buttons, form fields, and other interactive elements. Use Shift + Tab to move backward. On many sites, Enter activates a selected link or button, while Space activates buttons, checkboxes, and certain menu controls.
As you test, look for three things. First, a visible focus indicator should show where you are on the page. It may be an outline, border, color change, or other clear treatment. A focus state that is invisible against the page background leaves keyboard users guessing.
Second, the focus order should make sense. It should generally follow the visual and reading order of the page, moving from the header to main content and then the footer. If the cursor jumps unpredictably into a sidebar, hidden menu, or footer element, visitors can lose their place quickly.
Third, every interaction needs to work. Open drop-down menus, submit forms, close popups, operate sliders, and dismiss cookie banners using only the keyboard. A common failure is a popup that opens but cannot be closed without clicking a small X with a mouse.
Check color contrast and visual clarity
Polished design and accessibility support each other when visual decisions are tested in real conditions. Text that looks subtle on a large desktop monitor may be hard to read outdoors, on a phone, or for visitors with low vision.
Use a contrast checker to review text against its background. For normal-sized body text, WCAG AA commonly calls for a contrast ratio of at least 4.5:1. Large text has a lower threshold, but do not use that as an excuse for faint headings or hard-to-read calls to action. Buttons need enough contrast between their labels and backgrounds, and form errors should remain understandable even for people who cannot distinguish red from green.
Also check whether color is the only way information is communicated. An availability calendar, required form field, chart, or validation message should include text, icons, patterns, or other cues in addition to color. “Fields marked in red are required” creates a barrier when no other indicator is present.
Zoom the browser to 200 percent and review the page again. Content should remain readable and usable without horizontal scrolling for standard page layouts. Watch for clipped buttons, overlapping text, or navigation that becomes impossible to operate. This test often exposes responsive design problems that are easy to miss during everyday review.
Review headings, links, images, and page structure
A well-structured page is easier for everyone to scan, and it is especially useful for people navigating with screen readers. Headings should describe the content that follows and progress in a logical hierarchy. A page title followed by major section headings and supporting subheadings gives visitors a meaningful outline.
Avoid choosing headings only because their font size looks right. In WordPress, use the actual heading settings rather than styling a normal paragraph to resemble a heading. The visual result can be similar, but the underlying structure is very different for assistive technology.
Link text should communicate the destination or action. “Learn more” can work when the surrounding context is unmistakable, but a page with six identical “Learn more” links is difficult to navigate out of context. More specific wording such as “View estate planning services” or “Read the annual impact report” helps visitors make confident choices.
Every meaningful image needs useful alternative text. Alternative text should explain the image’s purpose, not simply list what appears in it. A photo supporting a nonprofit’s volunteer program might be described as “Volunteers sorting donated food at the San Rafael distribution center.” A decorative background flourish does not need that treatment and should be ignored by assistive technology. The difference matters: too little context is unhelpful, while repetitive or overly detailed descriptions create noise.
Test forms as if you have never seen them before
Forms often sit at the point where interest becomes action. A contact request, appointment inquiry, membership signup, or donation form must be clear and forgiving.
Each field needs a visible label that remains available when someone starts typing. Placeholder text inside a field is not a substitute for a label because it can disappear and often has poor contrast. Required fields should be identified before submission, and instructions should be specific when a format is expected, such as a phone number or date.
Submit the form with missing or invalid information. Do errors explain what needs to be fixed? Are they placed near the affected fields and announced in a way screen-reader users can find? Generic messages like “Something went wrong” leave visitors with no path forward. A useful error message says what happened and how to correct it.
Finally, verify the successful submission state. A visitor should receive a clear confirmation, know what will happen next, and be able to access that message without being unexpectedly redirected or trapped in a popup.
Use a screen reader for a reality check
Automated tools can flag code-level concerns, but they cannot tell you whether a page makes sense when heard aloud. A basic screen-reader test adds valuable perspective. On Windows, Narrator is built in, and many people also use NVDA. On Apple devices, VoiceOver is built into macOS and iOS.
Start with one key page rather than trying to become an expert user immediately. Listen to the page title, navigate by headings, move through links, and complete a form. Pay attention to whether buttons have meaningful names, images are announced appropriately, and expanding menus communicate their state.
You may hear confusing labels such as “button, button” or “link, click here.” Those are signs that the visual interface is not giving assistive technology enough information. You may also find that content is read in a strange order, which can point to problems in the page markup or layout.
A screen-reader check is not a replacement for testing with people who use assistive technology daily. If your website supports a broad community audience, public services, or a high-volume transaction process, user testing can reveal barriers that no internal review will catch.
Combine automated scans with human review
Accessibility scanning tools are useful for finding repeatable issues such as missing alternative text, empty links, heading skips, and insufficient contrast. Run a scan on key templates and use the results to create a repair list. They are particularly helpful after a redesign, plugin update, or content migration.
But automated results are a starting point, not a pass or fail certificate. A tool may confirm that an image has alternative text without knowing whether that text is meaningful. It may identify a form label while missing confusing instructions, a broken keyboard interaction, or an unclear customer journey.
For the most dependable results, combine automated scans with keyboard testing, visual review, and screen-reader checks. Document what you find, prioritize barriers on high-traffic pages and conversion paths, then retest after each fix. Avoid trying to solve everything through an overlay or quick-install widget. Those tools may offer limited assistance, but they do not repair underlying content, design, or code issues.
Make accessibility part of regular website maintenance
Websites change constantly. A new staff member uploads an image without alternative text. A campaign page uses an on-brand color that does not meet contrast requirements. A plugin update changes how a menu behaves on mobile. Accessibility needs ongoing attention for the same reason security, speed, and SEO do.
Build a short accessibility review into your publishing process. Before a page goes live, check headings, links, images, contrast, keyboard behavior, and forms. Review key site journeys after major WordPress, theme, or plugin updates. Keep a simple record of fixes so recurring problems can be addressed at the source.
A fast, well-designed website should also be a website people can use. Treat every accessibility improvement as a practical way to make your organization easier to find, easier to understand, and easier to choose.