Dallas–Fort WorthAccessibility statement

Target: WCAG 2.2 level AA

What we test, and what we have not.

Most accessibility statements claim conformance and stop. This one lists the checks included in the test suite, and then lists the gaps, because a statement that only contains good news is not evidence of anything.

Last updated 6 September 2026

Using this site

Four things that work, on every page.

These instructions describe the intended interactions. Automated tests and sampled browser checks help catch regressions, but do not replace manual assistive-technology testing.

Tab
Press Tab from the top of any page and the first stop is a link straight to the main content, past the whole navigation.
Escape
On a narrow screen, Escape closes the navigation panel and puts focus back on the button that opened it.
Headings
Headings run in order and never skip a level, so a screen reader's heading list is a usable outline of the page rather than a flat pile.
Reduced motion
If your operating system is set to reduce motion, every scroll animation on this site is off. Content never depends on an animation finishing.
Hands holding a phone photographing step flashing where a shingle roof meets a brick wall.

Alt text

What a screen reader is told about that photograph.

Every image on this site is declared in one registry with its alt text written alongside it, and nothing can render a photograph that is not in it. The text is the content of the frame, not a note about the file: a reader who cannot see the image needs to know what is in it, and “image of” tells them nothing they had not already worked out.

Hands holding a phone photographing step flashing where a shingle roof meets a brick wall.

That is the exact string, read verbatim from the registry rather than retyped here — so this page cannot drift away from what the image actually announces. The same rule covers every frame in the gallery and every plate on a Knowledge Centre page.