Report date: June 6, 2026 · Standard evaluated: WCAG 2.1 Level AA
This report uses the conformance terms from the Voluntary Product Accessibility Template (VPAT®): Supports, Partially Supports, Does Not Support, and Not Applicable. It reflects the state of the website following manual screen-reader and keyboard testing and automated contrast and accessibility scanning. It is a good-faith self-assessment and is not a legal certification or guarantee.
Evaluation methods: manual keyboard and screen-reader review (NVDA, VoiceOver), automated accessibility scanning (axe-core), and automated color-contrast checks. For how to report a barrier, see the Accessibility statement.
1. Perceivable
| Criterion | Success criterion | Conformance | Remarks |
|---|---|---|---|
| 1.1.1 | Non-text Content (A) | Supports | Meaningful images include descriptive alt text; decorative icons are marked aria-hidden. |
| 1.2.1 | Audio-only / Video-only (A) | Supports | The site hosts no audio-only or video-only-as-information media. |
| 1.2.2 | Captions (Prerecorded) (A) | Supports | Every published recording includes an attached text transcript and is hosted with platform captions enabled. The website blocks posting a recording without a transcript, so none is published uncaptioned. |
| 1.2.3 | Audio Description or Media Alternative (A) | Supports | A full text transcript is attached to every recording as the media alternative, providing equivalent information; the transcript is also offered as accessible HTML. |
| 1.3.1 | Info and Relationships (A) | Supports | Semantic HTML, landmarks, headings, and programmatic label/error associations on forms. |
| 1.3.5 | Identify Input Purpose (AA) | Supports | Common form fields use appropriate input types and labels. |
| 1.4.3 | Contrast (Minimum) (AA) | Supports | Text and UI meet the 4.5:1 (and 3:1 for large text) ratio; verified by automated contrast checks. |
| 1.4.4 | Resize Text (AA) | Supports | Content reflows and remains usable at 200% zoom; an on-page toolkit also adjusts text size and spacing. |
| 1.4.10 | Reflow (AA) | Supports | Responsive layouts reflow to a single column without loss of content or horizontal scrolling. |
| 1.4.11 | Non-text Contrast (AA) | Supports | Interactive controls and focus indicators meet the 3:1 contrast minimum. |
2. Operable
| Criterion | Success criterion | Conformance | Remarks |
|---|---|---|---|
| 2.1.1 | Keyboard (A) | Supports | All interactive elements, menus, and dialogs are operable by keyboard. |
| 2.1.2 | No Keyboard Trap (A) | Supports | Focus can move into and out of all components, including the chat assistant and dialogs. |
| 2.4.1 | Bypass Blocks (A) | Supports | A skip-to-content link and consistent landmarks let users bypass repeated navigation. |
| 2.4.2 | Page Titled (A) | Supports | Each route sets a descriptive document title. |
| 2.4.3 | Focus Order (A) | Supports | Focus order is logical; on navigation focus moves to the main content region. |
| 2.4.4 | Link Purpose (In Context) (A) | Supports | Links describe their destination; links opening a new tab announce it to assistive technology. |
| 2.4.7 | Focus Visible (AA) | Supports | Visible focus indicators are present on all focusable elements. |
| 2.5.3 | Label in Name (A) | Supports | Visible labels match the accessible name of controls. |
3. Understandable
| Criterion | Success criterion | Conformance | Remarks |
|---|---|---|---|
| 3.1.1 | Language of Page (A) | Supports | The page language is declared; accessible documents offer on-demand translation. |
| 3.2.3 | Consistent Navigation (AA) | Supports | Navigation and layout are consistent across pages. |
| 3.3.1 | Error Identification (A) | Supports | Form errors are identified in text and associated with their fields. |
| 3.3.2 | Labels or Instructions (A) | Supports | Inputs have explicit labels; required fields are indicated visually and to screen readers. |
| 3.3.3 | Error Suggestion (AA) | Supports | Validation messages describe how to correct the entry. |
4. Robust
| Criterion | Success criterion | Conformance | Remarks |
|---|---|---|---|
| 4.1.2 | Name, Role, Value (A) | Supports | ARIA is used appropriately; custom controls expose correct roles, names, and states. |
| 4.1.3 | Status Messages (AA) | Supports | Dynamic updates (chat responses, alerts, form errors) use live regions to announce changes. |
Known limitations
- Third-party or legacy PDF documents may not be fully tagged. The City provides an automatically generated accessible HTML version of posted PDFs and will supply an alternative format on request.
- Because content is updated continually, new issues can appear between reviews. Please report anything you encounter so we can correct it.
Questions or a request for this report in another format? Contact us through the Accessibility statement.