Accessibility
This site should be usable by everyone in Baytown, including people who browse with a screen reader, a keyboard alone, magnification, or high-contrast settings. This page says what we have actually tested, what we know still falls short, and how to tell us when we have got it wrong.
The standard we build to
We aim to meet WCAG 2.1 Level AA. That is the benchmark the U.S. Department of Justice adopted in 2024 for state and local government websites, and the one courts and settlements use when the Americans with Disabilities Act is applied to websites. We are an independent publisher rather than a government body, but AA is the right bar and it is the one we hold ourselves to.
We say "aim to meet" deliberately. Claiming full conformance is a promise no site can honestly keep across thousands of pages, and overclaiming it helps nobody.
What has been tested
Every page on this site is checked automatically on each build. The checks are:
- Every image carries an
altattribute. - Every link has text a screen reader can announce, and no link says only "click here".
- Every form control has a label.
- Headings run in order — no page jumps from
h1toh3. - Every page has a
<main>landmark and a working skip link. - No duplicate
idattributes, and noaria-labelledbypointing at an element that does not exist. - Every page declares its language, including the Spanish pages.
- Tables have header cells.
- Links that open a new tab carry
rel="noopener".
Colour contrast was measured against the WCAG formula rather than eyeballed. Body text is 18:1 in light mode and 16:1 in dark; the lowest text pairing on the site is 6:1, against a requirement of 4.5:1. Focus indicators exceed the 3:1 requirement for non-text contrast in both themes.
The site also respects prefers-reduced-motion andprefers-contrast, works at 200% zoom without horizontal scrolling, and is usable by keyboard throughout. It does not depend on JavaScript: the calendar, the directory and every guide render as plain HTML. Only site search needs scripting, and there is a link to browse the directory instead.
Last reviewed 2026-09-15.
Known gaps
Stated plainly, because a list of only good news is not useful:
- Automated checks are not a substitute for real testing. The checks above catch machine-detectable problems. They cannot tell whether a page makes sense when read aloud. No screen-reader user has tested this site yet.
- Site search uses a third-party component (Pagefind). Its markup is not ours and we have not audited it to AA.
- Some listing content comes from open data and inherits whatever capitalisation and punctuation the source used. A name recorded in block capitals may be read out oddly.
- We link out to other organisations' sites — the city, venues, businesses. We have no control over their accessibility.
Tell us about a barrier
If something here stopped you, we want to know, and we would rather hear about it than not. Use the contact page. Please say which page, what you were trying to do, and what happened — and if you use assistive technology, which one, because that usually tells us exactly where to look.
We will acknowledge a report and tell you what we can do about it. If something cannot be fixed quickly, we will say so and offer another way to get the information.
This statement describes our own testing and intentions. It is not legal advice, and it is not a certification. If you need a formal accessibility conformance report for procurement or legal purposes, ask and we will tell you honestly what we have and have not assessed.