Built So Anyone Can Use It

The Standard, and What We're Not Claiming

Our target is the Web Content Accessibility Guidelines, version 2.1, Level AA -- the level most public bodies and large organizations hold themselves to, and a reasonable bar for a small local site as well.

Working toward a standard and conforming to it are two separate claims, and we're only making the first. This site hasn't gone through a formal accessibility audit, carries no certificate, and won't be publishing a compliance score. Anyone claiming a site is fully accessible on the strength of an automated scan is describing what a tool measured, not what a real person experiences using the page.

We'd rather lay out plainly what's been done and what hasn't than print a claim we can't actually back up.

What's Already Built In

None of this is impressive on its own -- it's simply what a page ought to do, listed here so you have something concrete to hold us to.

• Headings that describe the page's structure, in the correct order, not just its visual style
• Menus you can open, navigate and close using only a keyboard
• A visible focus outline at all times, so you always know where you are on the page
• Text and background color combinations checked against WCAG contrast ratios
• Alt text on any image that actually conveys information
• Form labels properly tied to their fields, so a screen reader announces the right one
• No information conveyed by color alone, so a warning still reads as a warning without it
• Reduced-motion preferences honored, with animation turned off when you've requested that
• Text that can be resized without breaking the layout or hiding content
• Link text written to make sense on its own, never just click here

What Hasn't Been Tested Yet

Full conformance can't be confirmed from markup alone -- it takes manual testing with actual assistive technology: screen readers across more than one platform, magnification tools, voice control, switch access, and a review by someone who does this work for a living. This site hasn't been through that process.

So there are almost certainly things we've gotten wrong, most likely in the busiest spots: a long table read aloud by a screen reader, a form error announced in a confusing order, or a focus position that jumps somewhere unexpected once a menu closes.

If you run into one of those, you're not doing anything wrong, and it's worth telling us about it. A specific report from someone actually using assistive technology is worth far more to us than another automated scan result.

Content We Don't Control

A handful of pages include content served by another company -- a map is the obvious case. Those embeds arrive with their own markup, their own keyboard behavior and their own contrast choices, none of which we can change from our end.

Anywhere an embed appears, the same information is also available as plain text on that page -- the address spelled out, a phone number, hours written in text. If you ever find a spot where the embed is the only way to get something you need, that's a gap on our end and we want to know about it.

Reporting a Problem, or Getting a Page Read Aloud

The phone is the fastest route. Call the number at the top of any page, tell us which page you were on and what happened, and you'll reach a person, not a form.

From there, two things happen. We'll fix what we can, and tell you honestly if we can't or if it'll take some time. Meanwhile, we'll get you the content over the phone right then -- a full page read aloud, a price range explained, an inspection booked, a form filled out on your behalf while you're on the call.

You never actually have to use this website to get service. Everything on every page can be handled instead through a phone call, and asking for that is never an imposition on anyone here.