Accessibility Statement
Last updated: August 26, 2026
Cities are public institutions, and their vendors should hold themselves to the standard they would expect from a public website. This site is built to meet WCAG 2.1 Level AA.
Conformance status
Conformant with WCAG 2.1 Level AA. The site was audited against the Web Content Accessibility Guidelines 2.1 and the known issues found in that audit have been fixed. Accessibility is not a one-time task, so we re-check after changes.
What we've built in
- A skip-to-content link as the first focusable element
- Full keyboard operation — every link, button, and form field is reachable and usable without a mouse, with a visible focus outline that is never removed
- Semantic landmarks (
nav,main,footer) and a heading order that does not skip levels - Text and background colors that meet or exceed a 4.5:1 contrast ratio
- Font sizes in relative units, so the page reflows rather than clipping when you zoom to 200%
- Visible labels on every form field, with required fields marked in words rather than by color or an asterisk alone
- Form results announced to screen readers, with errors announced as alerts
- Touch targets of at least 44×44 pixels in navigation and controls
- Respect for your
prefers-reduced-motionsetting - Content that reflows to a single column down to a 320-pixel-wide screen
No accessibility overlay
This site deliberately does not use an accessibility overlay widget (AccessiBe, UserWay, AudioEye, or similar). Overlays load after screen readers have already read the page, interfere with the assistive technology people already know how to use, and have been the subject of repeated litigation. We fix accessibility in the code instead.
Known limitations
None currently known. This site uses no third-party embeds, booking widgets, or payment processors, so there is no vendor code outside our control.
Tell us about a problem
If any part of this site is difficult to use, we want to hear about it — that report is more useful than any audit. Email kelsey@mymediamatters.com with the page and what went wrong. We aim to respond within two business days and to fix confirmed issues promptly.
Technical details
Accessibility of this site relies on HTML and CSS. JavaScript is used only to enhance the contact form and the mobile menu; both work without it.