Quiet small-town main street with brick storefronts and the Gabilan hills beyond
Accessibility

Built to be used by everyone.

We hold this site and every site we build to WCAG 2.1 Level AA. Below is what our most recent audit found, what we changed, and exactly how to reach us if something on this site gets in your way.

Our standard

What we commit to on every page.

  • Semantic HTML with a single H1 and a logical heading outline on every page
  • Full keyboard operability with visible focus indicators
  • Descriptive alt text on meaningful images; decorative graphics hidden from screen readers
  • Labeled form fields with errors described in text, not color alone
  • WCAG AA color contrast on body text, headings, and interactive elements
  • Responsive layouts and tap targets that stay usable at 200% zoom
Latest audit — 2026

What the audit found, and what we fixed.

We ran automated axe-core scans across 9 core pages of this site, plus a manual keyboard-navigation pass. Every reported violation was corrected and re-scanned to confirm zero remaining issues.

Color contrast

What we found
Our accent amber failed 4.5:1 against cream backgrounds, and several low-opacity text styles sat under the AA threshold.
What we changed
We deepened the primary accent, added a lighter gold variant for dark sections, and raised muted text opacity across 29 files. All text now meets WCAG AA contrast.

Heading order

What we found
One industry grid skipped a heading level, which breaks screen-reader outlines.
What we changed
Headings now run in strict H1 → H6 order on every page, with exactly one H1 per page.

Landmarks

What we found
The contact page rendered its content outside a main landmark.
What we changed
Every page now wraps its primary content in a single <main> landmark, so skip-to-content and rotor navigation work.

Images and icons

What we found
Some decorative icons were announced as meaningful content.
What we changed
Meaningful images carry descriptive alt text; decorative icons are marked aria-hidden so screen readers skip them.

Controls and forms

What we found
Icon-only buttons and a few inputs lacked accessible names.
What we changed
Every button has a visible label or aria-label, and every form field is tied to a label. Focus indicators are visible on keyboard navigation.
Known limitations

Where we're still working.

Our example sites are intentionally designed in a wide range of styles — modern, vintage, editorial, utilitarian — to show what's possible. They meet our contrast and keyboard standards, but a few use decorative textures and display type that we continue to review. Third-party embeds such as maps and video players are governed by their providers, and we replace any that fall short.

Automated scanning also has limits. It catches structural problems, not every real-world barrier — so your report is genuinely the most useful signal we get.

Get help

How to request assistance.

If any page here is difficult or impossible for you to use, email hello@hollisterwebsites.com with the page address and what went wrong. We acknowledge reports within 2 business days and either fix the issue or give you a timeline within 10 business days. We'll also send you the information you were after in whatever format works — email, plain text, large print, or a phone call — at no charge.

Accessibility questions

Standards, audits, and getting help.

What accessibility standard does Hollister Websites follow?

We build to WCAG 2.1 Level AA. That's the standard referenced by the ADA and California's Unruh Act for public-facing websites, and it's the target we hold both this site and the sites we build for clients to.

When was this website last audited for accessibility?

Most recently in 2026. We ran automated axe-core scans across 9 core pages, fixed every reported violation, and re-scanned to confirm zero remaining issues. We re-run the scan whenever we ship significant page changes.

What did the audit actually find and fix?

The main issues were color contrast on our amber accent and low-opacity text, one skipped heading level, a missing main landmark on the contact page, and a handful of icon-only buttons without accessible names. All of those were corrected.

Are automated scans enough to guarantee accessibility?

No. Automated tools catch roughly a third to a half of real barriers. We supplement them with keyboard-only navigation checks and manual review of headings, alt text, and focus order. If something still trips you up, we want to hear about it.

How do I report an accessibility barrier on this site?

Email hello@hollisterwebsites.com with the page address and a short description of what happened. We aim to acknowledge within 2 business days and to resolve or give you a timeline within 10 business days. If you'd rather talk, call us and we'll take the details by phone.

Can you get the information to me another way if a page isn't usable?

Yes. If any page or document on this site is a barrier for you, tell us what you were trying to find and we'll send the same information by email, plain text, large print, or over the phone at no charge.

Do you build accessible websites for Hollister businesses too?

Yes. Semantic headings, keyboard-navigable menus, labeled forms, alt text, and AA color contrast are part of every build we deliver in Hollister and San Benito County — not a paid add-on. For regulated clients like medical practices, government, and non-profits, we also run a manual keyboard and screen-reader pass before launch.