Accessibility

The standard we work to

We build to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We have not commissioned a third-party audit, so we do not claim conformance — a claim without an audit behind it is worth nothing. What follows is what we have built and tested ourselves.

What this site does

• Keyboard. Every interactive element is reachable and operable by keyboard, focus is visible with a high-contrast outline, and a skip link lets you jump straight to the main content.
• Structure. Pages use real headings in order, real lists, and real tables with row and column headers, so a screen reader can navigate by structure rather than by guesswork.
• Motion. The reveal animations are decorative and switch off entirely under the operating system's reduce-motion setting. No content depends on motion to be readable.
• Colour and contrast. Body text and interface text are tested against WCAG AA contrast ratios. Colour is never the only way a status or a label is conveyed — availability labels, relationship labels and statuses all carry text.
• Zoom and reflow. Layouts are built in relative units and reflow to a single column on a narrow screen or at high zoom, without a horizontal scrollbar. Wide data tables scroll within their own container rather than pushing the page sideways.
• Decorative interface samples. The illustrative interface mock-ups are hidden from assistive technology and labelled as samples, so they are not read out as real data.
• No external dependencies. Fonts are bundled with the site, so pages render fully without waiting on a third-party service.

Known limitations

Stated plainly, because you would find them anyway:

• Data tables are wide. The coverage tables carry eight columns and scroll horizontally within their container on a small screen. That is usable but not comfortable. If you need this content in another format, ask and we will send it.
• Maps in the workspace are visual. Geographic views convey location graphically. Every map is backed by a list or table of the same records, which is the accessible path to the same information.
• Source documents are not ours. Records link out to agency systems, and scanned notices are images published by the agency. We cannot make a third party's PDF accessible, and we will not pretend those links meet a standard they do not.
• No formal audit yet. We have not had an independent accessibility audit or produced a VPAT. If you need one for a procurement process, tell us and we will discuss what is realistic and by when.

Reporting a barrier

If something on this site or in 718 Interchange stops you getting to information you need, email hello@718systems.com with the page and what happened. We will acknowledge it, tell you whether it is something we can fix and roughly when, and in the meantime get you the information another way.

If you need a record, a coverage table, or anything else in an alternative format, ask. That request is never a nuisance.