The standard we target
WCAG 2.1 Level AA, for this site and for the console behind it. That is the level most regulations converge on, and it is the level our own agents grade your product against.
What is measured, and how often
The check is part of the test run that gates changes to the console and the engine, and a failure there stops the change. Edits to this site’s own pages go live without waiting for it, so a new barrier here is caught by the next of those runs rather than before it ships. The tool is axe-core 4.13.0, the same engine the product uses on your product, driven through a real Chromium rather than read off the markup.
- This site: 12 page views, desktop and mobile, at the reduced-motion setting, which is the steady state a screen reader user is most likely in.
- The console: 16 views, in both light and dark, at two widths.
- Alongside axe, a separate pass checks contrast on every text and background pair, the type and weight scales, tabular numerals, hit-target sizes, keyboard reach and focus states.
The result on the day this page was last updated: no accessibility violation on any of the pages of this site it checked, and none in the console views it checked. That is an automated result on a fixed date, not a guarantee about later versions, which is why the date is at the top.
Known limitations
- Automated checks find a minority of real barriers. Every published study of tools like axe puts the share it can catch well under half. A clean run means no machine-detectable violation. A clean run does not mean the site is usable by everyone.
- 2,924 elements sit on top of an image and were not measured for contrast, because contrast against a photograph is not a single number. Those are unmeasured, not passing.
- No screen reader has been run over this site by a person, and no user with a disability has tested it. That is a gap, and it is the next thing worth fixing.
- The checks run at two widths and two themes, not at every zoom level, and not with a braille display or a switch device.
Reporting a barrier
Write to support@nthlabs.dev and say what you were trying to do and what stopped you. You will get a reply within five working days, from somebody who can change the code. A barrier you report is treated as a defect: it goes in the same queue as everything else, and the fix ships with a check that keeps it fixed.
If you need anything on this site or in the console in a different format (a report, a policy, an invoice), ask, and it will be provided in a format you can use, at no cost. That is an obligation under the accessibility law of Ontario, where nth Labs is operated from.
Legal status
Under Ontario’s AODA, the requirement to meet WCAG on a website applies to organisations with fifty or more employees, and the European Accessibility Act exempts micro-enterprises on much the same grounds. nth Labs is under both thresholds, so neither obligation binds it yet. We publish this statement anyway, because nth Labs grades the accessibility of other people’s products.