Accessibility Tracking

This document is to capture what each service team has done to comply with accessibility standards. You can enter as many as you recall from the beginning of the program but at least since the beginning of 2024.

Since the start of the ACCESS project all tracks have been implementing WCAG 2.1 AA standards.
https://www.w3.org/WAI/standards-guidelines/wcag/
https://www.w3.org/WAI/WCAG22/quickref/?versions=2.1

In brief:

User can navigate the site with keyboard instead of mouse and includes visible focus indicators
Website has sufficient contrast between text/background
Information conveyed with color can be conveyed without color
Ability for user to increase font size without loss of functionality
Descriptive link text for each link
Form controls and fields have associated text elements
Use of alt tags

Beginning in 2025:

Each track should run accessibility scans quarterly (Jan, Apr, Jul, Oct) on their internal pages to identify any new issues and remediate

Accessibility scanning tools used:
https://accessibleweb.com/
https://www.deque.com/axe/devtools/
https://www.freedomscientific.com/products/software/jaws/

ACO:

Provided accessible color, type, and design standards for the ACCESS-wide website style guide and continue to provide refinements as needed per individual use cases
Ran accessibility scans 2024 and Feb 2025

Allocations:

Provided site wide accessible universal header/menu and footer script in 2024

Support:

implemented universal header/menu and footer

Operations:

No accessibility improvements since 2024

Metrics:

No accessibility improvements since 2024