Accessibility statement

This platform aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1, level AA for the pages the park's staff and vendors use. Last reviewed October 10, 2026.

What is in place

• A "Skip to main content" link is the first thing a keyboard reaches on every console, field and vendor page. Checked by the page audit (ui:audit-aria) fails if a shell lacks it or its target.
• Every field, selection and text box has a name a screen reader can read, and every error is tied to its field. Checked by ui:audit-aria, for every control the screens are built from.
• Table headings say whether they head a column or a row, images carry a text alternative (or say they are decoration), and nothing takes the page out of its natural tab order. Checked by ui:audit-aria, across every page template.
• Status is never colour alone: badges, alerts and tones always carry words. Checked by the component library, which has no colour-only status.
• The cards of a board and the rows of an ordered list (the steps of a procedure) can be moved with buttons as well as dragged, and the list says what moved. Checked by the component library and its tests.
• The field app uses large touch targets. Checked by the field shell's own style rules.
• The layout follows the width of the screen and the browser's own zoom. Checked by the layouts every shell is built on.

What is not yet as good as it should be

• The park map, the utility schematic and the charts are pictures first. Their figures are available in the tables beside them and in the reports, but a person who cannot see the picture has less than a person who can.
• Moving things on the utility schematic and in the map editors is done by dragging; those two have no keyboard alternative yet.
• The platform has not had an independent accessibility audit. This statement is the platform's own reading of itself, backed by automatic checks that run before every release; automatic checks find some problems, not all.

Tell us about a barrier

If something on a page is hard to use with your keyboard, screen reader, magnifier or voice control, tell the park. Signed in, use the "Report a problem" button at the top of the page and say what you were trying to do and what you use; it reaches the people who maintain this platform with the page you were on. Not signed in, tell the park's office directly.

We aim to answer within five working days and to say when a fix is planned.