Skip to main content
(714) 823-3164
Online Website Marketing, experts in local website marketing strategies, Chino California

Legal

Accessibility Statement

We want every page on this site to work for everyone who visits it. This statement explains our target, what we have actually done, where we still fall short, and how to tell us when something breaks.

Call (714) 823-3164 or ask a question. Clear recommendations, even if we never work together.

Online Website Marketing targets WCAG 2.2 Level AA on this website. We build with semantic HTML, keyboard navigation, visible focus indicators, sufficient color contrast, descriptive alt text, and reduced motion support. If any page blocks you, email terrysr@online-website-marketing.com or call (714) 823-3164 and we respond within two business days.

Last updated

Our Target and Why It Matters

This site is built to conform with the Web Content Accessibility Guidelines version 2.2 at Level AA. WCAG is the standard courts, regulators, and most procurement teams point to when they talk about website accessibility, and Level AA is the commonly accepted bar. We treat it as a design requirement, not a cleanup task at the end of a build. Accessibility matters here for a practical reason on top of the ethical one. Roughly one in four adults in the United States lives with a disability. Many of them are the exact customers our clients want: the homeowner who needs an HVAC repair, the patient looking for a dentist, the family member searching for in home care. A site that a screen reader cannot navigate is a site that loses those calls. The same choices that make a page accessible also make it faster, clearer, and easier for search engines to understand. We apply this standard to our own website first, because it would be strange to recommend something to clients that we had not done ourselves. This statement was last reviewed in August 2026 and gets revisited whenever the site changes in a meaningful way.

What We Actually Built In

These are the specific measures in place on this site rather than a general promise to care about the topic. Every page uses semantic HTML, which means headings are real headings in order, lists are real lists, and buttons are buttons instead of styled div elements. That structure is what lets a screen reader build a usable outline of the page. All functionality can be reached with a keyboard alone, without a mouse or trackpad, and a skip link at the top of each page lets keyboard users jump past the navigation to the main content. Focus indicators are visible and have enough contrast to be seen, so you always know where you are on the page. Body text meets or exceeds a 4.5 to 1 contrast ratio against its background, and large text and interface components meet 3 to 1. Images that carry meaning have descriptive alt text, and decorative images are marked so screen readers skip them. Forms have labels tied to their inputs, and error messages say what went wrong in words rather than only turning a field red.

  • Semantic HTML with correct heading order and landmark regions
  • Full keyboard operation, logical tab order, and a skip to content link
  • Visible focus indicators on every interactive element
  • Color contrast meeting or exceeding WCAG AA ratios
  • Descriptive alt text on meaningful images, empty alt on decorative ones
  • Reduced motion support that respects the prefers-reduced-motion setting
  • Labeled form fields with clear, text based error messages

How We Test

Automated tools catch roughly a third of accessibility problems, which is useful and nowhere near enough. We run automated checks on every page as part of our build process, using standard tooling to flag contrast failures, missing alt attributes, unlabeled form controls, and broken heading order. Those checks run before anything ships, so regressions get caught rather than discovered by a visitor months later. On top of that we test by hand. We navigate key pages using only a keyboard to confirm that every link, button, form field, and menu can be reached and operated in a sensible order. We test with screen readers, primarily VoiceOver on macOS and iOS and NVDA on Windows, on the pages that matter most: the home page, service pages, contact forms, and the main navigation. We check the site at 200 percent browser zoom and at narrow viewport widths to confirm that content reflows without horizontal scrolling or lost text. We also review with system level reduced motion and increased contrast settings enabled. Manual testing is where the real problems show up, because a page can pass every automated rule and still be confusing to move through.

Known Limitations

We would rather list our gaps than claim a clean sheet nobody can verify. As of the last review in August 2026, these are the areas we know need work. Some video content on the site does not yet have full captions or an audio description track, and older videos are being captioned in order of how often they get viewed. Certain third party content, including embedded maps and any embedded review widgets, is rendered by outside services whose accessibility we do not control. We can choose whether to use them, and we do check them, but we cannot fix their internal markup. A small number of older blog and resource pages published before this standard was adopted have not been fully re-audited, and they are being reviewed on a rolling basis as we update them. Complex data tables in a few reporting explainers may be difficult to navigate with a screen reader, and we are rewriting those to use simpler structures. PDF documents offered for download may not be fully tagged for accessibility. If you need any PDF on this site in an accessible format, ask and we will provide the content another way at no cost.

Tell Us When Something Breaks

If you run into a page you cannot use, we want to hear about it, and we would rather hear it directly than have you give up and go somewhere else. Email terrysr@online-website-marketing.com with Accessibility in the subject line, or call (714) 823-3164 during business hours, seven days a week, 10:00 AM to 6:00 PM Pacific. You can also write to us at 16379 E Preserve Loop Unit 2193, Chino, CA 91708. It helps if you can tell us the page address, what you were trying to do, what happened instead, and what browser, device, or assistive technology you were using. Even a rough description is useful, so send what you have rather than waiting until you can write a perfect report. Here is our commitment. We acknowledge every accessibility report within two business days. We give you an assessment and a plan within 10 business days, including a realistic date. If a fix will take longer than that, we say so and we offer another way to get the information or complete the task in the meantime, whether that is by phone, by email, or in a different format.

Frequently asked questions

What standard does this site follow?

WCAG 2.2 at Level AA. That is the version and level most regulators, courts, and procurement teams reference for website accessibility in the United States. We treat it as a build requirement rather than a final cleanup step, and we re-check pages whenever the site changes in a meaningful way.

Is this site fully compliant right now?

We conform to WCAG 2.2 Level AA on the pages we have audited, with the exceptions listed under Known Limitations. Claiming total compliance with no gaps would be a claim nobody can honestly make about a site that keeps changing. We publish what still needs work instead.

How fast will you fix a problem I report?

We acknowledge every report within two business days and give you an assessment with a plan within 10 business days. Simple fixes usually ship in that same window. If a fix takes longer, we tell you the date and offer another way to get what you needed in the meantime.

Do you build accessible websites for clients too?

Yes. Accessibility is part of how we build, not a paid add on. We use semantic markup, keyboard operable interfaces, contrast checked color systems, and labeled forms as the default. For clients who need a formal audit or remediation of an existing site, that is scoped as its own project.

Do accessibility overlay widgets solve this?

No, and we do not use them. Overlay scripts that promise instant compliance often interfere with the assistive technology a visitor already uses, and they have been named in lawsuits rather than preventing them. Real accessibility comes from the underlying markup and design, which is where we put the effort.