Accessibility statement

What we built in

• A "Skip to main content" link as the first item on every page.
• Labelled landmarks for the header, main navigation, breadcrumb, main content and footer.
• One main heading per page and a logical heading order.
• Navigation that keeps the same order on every page, with the current page marked.
• A small-screen menu that uses a button with its state announced, following the W3C disclosure navigation pattern, and stays fully visible when JavaScript is off.
• Visible focus outlines on every interactive element, with a contrast of at least 3:1 against the background they sit on.
• Text contrast of at least 4.5:1.
• Controls at least 24 by 24 CSS pixels, and main buttons at least 44 pixels tall.
• Forms with visible labels, hints linked to each field, and error summaries that receive focus and link to the fields that need attention.
• Tool results that receive focus when they appear, with a status message announcing the change.
• No moving or flashing content, and layouts that reflow at narrow widths without horizontal scrolling.
• Decorative graphics hidden from assistive technology; meaningful diagrams given a text alternative.

How we tested

Testing so far has been automated, run in a headless Chromium browser with scripts we wrote for this site:

• Keyboard focus: every page was loaded and tabbed through from start to end, recording each focused element, its focus outline and the contrast of that outline against the background behind it.
• Contrast: text colour against background colour was checked on every page at four screen widths.
• Layout: every page was checked at widths of 1440, 768, 390 and 320 pixels for horizontal scrolling, and the home page was compared with its design.
• Without JavaScript: every page was loaded with scripts disabled to confirm that navigation and content remain available.
• Forms and tools: each tool and the contact form were completed using only the keyboard, including deliberate errors, to check focus movement and messages.
• Structure: every page was checked for one main heading, heading order, unique element ids, labelled form controls and image alternatives.

Testing still to come

No one has yet tried the site with a screen reader (NVDA, JAWS, VoiceOver or TalkBack), with voice control software, or as part of sessions with disabled people. Automated checks cannot find every problem, so there may be barriers we have missed. Testing with screen readers and with disabled people has not been done yet. This statement will change when it has.

Known limitations

• The draft files produced by the planning tools (CSV, XML and plain text) have no formatting beyond what those formats allow.
• External sites we link to have their own accessibility, which we cannot control.

Reporting a barrier

If something on the site does not work for you, please tell us through the contact page or by email to hello@navarchiva.online. Name the page and the task, and mention your browser or assistive technology if you are happy to.

Standards

WCAG 2.2 became a W3C Recommendation on 5 October 2023. We use it as our reference, together with the W3C ARIA Authoring Practices for interactive patterns. We have not had the site formally audited or certified.

Sources checked 4 November 2026 for accessibility

1. Disclosure menu, W3C
2. WCAG 2.2 changes, W3C