Accessibility
Everything on this site can be reached with a keyboard, read by a screen reader, and used one-handed on a phone. Where it falls short is written down below rather than glossed over. If a page here is getting in your way, ring the number and say which one: somebody will deal with the door over the phone, and the page gets fixed.
What Was Actually Built In
Contrast measured, not judged by eye
The cypress green and brass palette was tested as twenty-nine specific color pairs against the WCAG ratios, because a palette that looks fine in a mock-up routinely fails on a dark band or inside a table. Every pair clears. The two brass tones exist for that reason: the darker one on pale surfaces, the lighter one on the green, because no single mid-tone passes against both.
Readable on a phone in daylight
Body text sits at a size that does not need pinching, and line length is capped so a paragraph does not run the full width of a tablet. This site gets read on a driveway next to a door that will not shut, often one-handed, and that is the condition it was sized for.
Thumb-sized controls
Buttons, navigation items and the breadcrumb trail are all large enough to hit first time. Breadcrumbs are where this is most often got wrong, because they look like small print and get treated like small print.
Driven entirely from a keyboard
The navigation, the FAQ accordions, the map placeholder and the contact form all work without a mouse, and the element holding focus is always visibly outlined rather than relying on the browser default.
Structured for a screen reader
Heading levels run in order with none skipped. Every photograph has alternative text describing what is in the frame rather than repeating the page title. Tables carry real row and column headers. Form fields have actual labels, not a placeholder standing in for one.
Nothing moves unless you ask it to
No autoplay, no animation that loops, no carousel rotating under you mid-sentence. The coverage map stays a static placeholder until you deliberately open it, which also keeps it off the page weight for everyone who never does.
The Two Weak Points, Named
Claiming finished conformance would be overstating it, so here are the specific places this site is weakest, both of which are components built elsewhere.
The coverage map is an embed from a third party and nothing here controls how it behaves with assistive technology. That is why it never loads on its own, and why every place it would show you is also written out as plain linked text on the same page. You never need to open the map to get the information in it.
The spam check on the contact form is also somebody else's control. If it will not let you through, do not fight it. Ring the number instead: the phone reaches the same dispatch faster than the form does anyway, and no part of this site works better than a phone call when a door is stuck open.
Reporting a Problem With a Page
Three things are enough to reproduce almost anything: which page, what you were trying to do, and what happened instead. Say those on the phone. Nobody should end up living with a broken garage door because a website got in the way, and a page that fails somebody is a bug here rather than an inconvenience to be worked around.