Our Commitment to an Accessible Site

The standard we aim at

This site aims at the Web Content Accessibility Guidelines, a widely used standard for contrast, keyboard access, alternative text on images, and clear structure for screen readers. Aiming at a standard is different from meeting it everywhere, on every page, at every level. Some parts were built earlier, some content comes from outside sources, and testing is ongoing rather than finished.

What has actually been done: text and background colors checked for contrast, images given alternative text describing what they show, pages built so a keyboard alone can reach every link and form field, and headings structured so a screen reader can jump between sections in a sensible order rather than reading top to bottom with no map.

• Text and background contrast checked against the standard, not eyeballed
• Alternative text written for images that carry real information
• Every link and form field reachable using a keyboard alone
• Headings structured so a screen reader can navigate by section
• Known gaps in third-party embedded tools listed, not hidden
• Older pages flagged for review rather than assumed compliant
• A feedback route that leads to an actual fix, not a form letter
• Phone and email offered as a standing alternative, not a last resort
• Skip links so keyboard users reach main content fast
• Descriptive alternative text on informational images site-wide

What we have done so far

What has not been done yet, stated plainly rather than glossed over: some embedded third-party tools, like scheduling widgets or map displays, may not meet the same standard, because they are built and maintained outside this site. Older archived pages may use patterns that predate the current approach. Neither is an excuse. Both are on the list to fix.

A standard like this is never finished the way a paint job is finished. New pages get built, old ones get revised, and each one gets checked again. A conformance claim that never changes is usually a sign nobody is actually looking. This page gets updated when something is fixed or when a new gap is found and confirmed.

Where the gaps still are

Feedback is the part that actually moves this forward, more than any internal audit does. A person using a screen reader, a switch device, or a keyboard alone will find a barrier that automated testing tools miss every time, because those tools check code, not lived experience of trying to get something done on the page.

So the ask is specific: tell us what you were trying to do, on which page, and what happened instead. Not a general complaint that the site is hard to use, but the actual point where it broke. That is the difference between a report that gets fixed and one that gets filed and forgotten.

How to report a problem to us

None of this replaces getting help another way. If the site itself is the barrier, right now, call or email and get the same outcome: a scheduled visit, an answer to a question, a price range for a job. The standard is something to work toward. Getting you help today does not wait on that work finishing.

This statement will be revised as fixes land and as new gaps get reported and confirmed. It is not a legal filing and it does not promise a certification. It is a plain account of where things stand, written so a person deciding whether this site will work for them can actually tell.