Accessibility statement

Last reviewed: 23 October 2026

Our commitment

MechKit should be usable by as many people as possible, including people who use screen readers, keyboard-only navigation, screen magnification or voice control. We aim to meet WCAG 2.2 Level AA across the calculators and these policy pages.

What is in place

• Semantic HTML: landmark regions (header, nav, main, aside, footer), a single h1 per page and headings in order.
• A “Skip to tool” link as the first tab stop, and a main region that receives focus after you follow it.
• Visible 3 px focus outlines on every interactive element, shown for keyboard users.
• Every input has a programmatically associated label; unit pickers and icon-only controls have accessible names.
• Status messages (“Pinned…”, “Inserted…”, “Downloaded…”) are announced through a polite live region, and the results area updates as a polite live region.
• The current tool is marked with aria-current="page" in the tool list.
• The mobile menu button exposes aria-expanded and aria-controls.
• Light and dark themes follow your operating system setting, with contrast checked against the theme colours.
• prefers-reduced-motion is respected: transitions and smooth scrolling are disabled.
• Layout reflows to a single column on narrow screens and stays usable when text is zoomed to 200%.
• No time limits, no auto-playing media, no flashing content, and no interaction that requires dragging.
• Nothing relies on colour alone: pinning, errors and status messages all carry text as well.

Known limitations

• The calculators need JavaScript. These policy pages work without it, but no tool will run if JavaScript is disabled or blocked.
• Wide tables scroll sideways. Reference tables and multi-row result tables overflow horizontally inside their container. On small screens and at high zoom you may need to scroll sideways, and the scroll container is not reachable from the keyboard in every browser.
• Some table controls rely on tooltips. The “select all” checkboxes in table headers, and the value buttons inside result tables, get their extra explanation from a title attribute, which some screen readers do not announce.
• Dense result tables. Parameter sweeps that produce many rows create long tables; in that case the result area is deliberately not a live region, so new results are not announced automatically.
• Formula errors are plain text and are shown in the results area rather than being announced separately.
• Custom sources are user content. Tables and tools you add yourself are rendered with the same markup as the built-in ones, but we cannot guarantee the accessibility of third-party labels or data.

Feedback

If you hit a barrier, please tell us. We treat accessibility bugs as real bugs. Email [email protected] with the page you were on, what you were trying to do, the assistive technology and browser you use, and what happened. We aim to reply as soon as we can and will fix what we can.

How this statement was prepared

Self-assessment against WCAG 2.2 AA using browser developer tools, keyboard-only navigation and spot checks with screen readers. The site is plain HTML, CSS and JavaScript with no third-party frameworks or embedded widgets. This statement was last reviewed on 23 October 2026 and will be updated when the site changes materially.

Compatibility

The site is built with standard web technology and is intended to work in current versions of Chrome, Edge, Firefox and Safari on desktop and mobile, together with common screen readers and magnification tools. We have not yet completed testing across the full range of assistive technology, so combinations we have not tested may behave differently.