Accessibility.

What The Site Targets

The site is built toward the Web Content Accessibility Guidelines at level AA as a design target. Target is the accurate word. It describes the standard the construction decisions were taken against, not a tested result.

Practices Followed

• Semantic structure. Pages use real headings in order, real lists, real tables with captions and header cells, and landmark elements for the header, navigation, main content and footer. Each page has one first-level heading. Every page begins with a skip link to the main content.
• Native elements rather than hand-rolled controls. Expanding and collapsing sections use the browser's own disclosure element, so keyboard operation, focus handling and the state announced to a screen reader come from the browser rather than from our code. This applies to the navigation menu, the questions on the reference pages, and the legal information in the footer.
• Content does not depend on JavaScript. Every word of every page is present in the served HTML. Nothing is hidden until scrolled to, nothing is loaded after the fact, and no text requires a script to become visible. A reader with scripts disabled sees the complete page. The build fails if any scroll-triggered reveal is reintroduced.
• Keyboard operable navigation. The navigation works by hover, by focus and by click, and can be dismissed with the Escape key. Focus indicators are not suppressed.
• No external requests. No web fonts, no third-party scripts and no tracking. Text is set in the reader's own system fonts, so it inherits whatever font settings the reader has chosen.
• Motion respects the system setting. The single animation on the site, a one-off entrance on the hero of each page, is disabled where the operating system reports a preference for reduced motion.
• Text scaling. Layout is fluid rather than fixed, and no viewport setting prevents zooming.
• Images carry text alternatives. The site uses very few images. Those it uses have alternative text.

What Was Actually Measured

Two things were verified rather than assumed. Colour contrast ratios were computed for the text and background pairs used in the site's palette, rather than judged by eye. The rendered geometry of the numbered step lists was measured after a layout defect was found in them, to confirm that no badge overlapped the text that followed it.

Each build runs automated checks for broken internal links and anchors, unbalanced markup, and external resource requests. These are structural checks. They are not accessibility tests.

What Has Not Been Tested

Stating this precisely matters more than the list above.

• The site has not been tested with a screen reader. No page has been navigated with JAWS, NVDA, VoiceOver or Narrator.
• The site has not been tested with speech recognition, switch access, or screen magnification software.
• No automated accessibility auditing tool has been run against the pages as served.
• No user testing with disabled participants has taken place.
• No conformance audit has been carried out and no accessibility conformance report exists.

Until those things are done, the correct description of this site is that it was built with accessibility in mind and has not been proven accessible. Anyone procuring from Kempron who requires a tested conformance position should ask for one rather than infer it from this page.

Reporting A Barrier

If any part of this site is difficult or impossible for you to use, write to info@kempron.io and describe what happened. Tell us the page, what you were trying to do, and the browser and assistive technology you were using if you know it.

If you need information from this site in another format, ask at the same address and we will supply it.