As a small business, basestep is not legally required to meet the European accessibility requirements. We build towards them anyway: WCAG 2.2 AA, tested automatically on a fixed set of screens. The conformance status has not been formally established yet; this page shows where it is not good enough yet and how to report a problem.
the statement
Six parts, in the form the W3C recommends.
part 1
Our commitment
Accessibility is part of how we build, not a check afterwards. A set of gates runs with every delivery, and if one is red, the build does not get through. They calculate the contrast of every text colour against every surface it may sit on, in both colour modes. They require an h1 with a heading order without gaps on every page, a language attribute on sentences in another language, a decision on every SVG, and motion that stops under the system preference.
Those gates calculate with the colour values and with the built HTML, not with the pixels a browser draws. So they catch the errors that are in the code, and not everything a person sees. Where that difference hurts is in part 4.
The site does not need JavaScript for its content: text stays in place and accordions keep working if scripts fail.
part 2
The standard and the status
We work towards WCAG 2.2 AA. The status is partially conformant: parts of the site meet that level and parts do not yet.
That status has not been formally established yet. The first full manual test round is planned and has not been carried out, and until that round is complete, WCAG 2.2 AA remains a commitment and not an established fact. That is why nowhere on this site does it say that basestep.io meets the standard.
part 3
What this statement covers
This statement covers the website basestep.io: all pages you can view without logging in.
The app at app.basestep.io is not covered yet. It gets its own statement when it goes live; until then we say nothing about the app that we have not tested.
part 4
What is not good enough yet
On 5 September 2026 the site was reviewed for accessibility. The built HTML of all pages was checked for landmarks, roles, labels, aria attributes and SVGs, and the styles for focus, high contrast and motion. The target sizes were measured in a browser, at 390 and at 1180 pixels wide.
Below is what that review found. First what is still open, then what has been done since, with the date. With every fix this list should move along, and that is exactly why it has dates in it.
open
No page has been tested with a real screen reader, with switch access, or with people who rely on them. Reading code and measuring does not replace that. Until that test has happened, WCAG 2.2 AA remains a commitment and not an established fact.
open
If you set Windows to high contrast, the fill of the ring in the API comparison disappears. The circle stays and the number next to it carries the same value, but you no longer see the ratio at a glance.
open
The primary button in the top bar is 32 pixels high on a wide screen and 40 on a phone. That comfortably meets the 24 that WCAG 2.5.8 asks for, but not the 44 of 2.5.5. Taller does not fit next to the eight menu items right now without the bar wrapping.
open
If you zoom to 400 percent on a wide screen, the top bar takes up about a quarter of the height. It scrolls along with you, so you can reach everything; it does take up space.
fixed
The source links in the API comparison were 28 by 16 pixels and sat three per row right above each other, where WCAG 2.5.8 asks for 24 by 24. They are now 24 high.
fixed
The mode switch, the sort buttons, the clear button and the small footer links were between 25 and 40 pixels high. They are now all at least 44, the size that WCAG 2.5.5 and both platform guidelines ask for.
fixed
On this page, the same colour cloud drifted as on every other page header: sixteen seconds per loop, forever, with no button to stop it. WCAG 2.2.2 asks for that button for motion that lasts longer than five seconds and sits next to other content. The cloud is no longer on this page.
fixed
Fifty-seven of the 366 drawings on the site carried no decision about what a screen reader does with them, and were therefore announced as an unnamed image in the middle of a sentence. All 366 now carry that decision, and a gate stops the build as soon as one is added without it.
fixed
In high contrast, the meters, the columns and the bars in the illustrations disappeared: their fill is a background, and the browser replaces that with a system colour. They now keep a border or the colour you chose yourself for highlighting.
fixed
The source list under each knowledge base article had lines 22.4 pixels high, again below the 24 of WCAG 2.5.8. Those articles did not exist yet when the review ran. The lines are now 24.5 high.
part 5
Reporting a problem
If you run into something, mail info@basestep.io. Write which page it is, which assistive technology or browser you use, and what went wrong; a screenshot helps. If you cannot reach something, just ask: we will send the information in a form that does work for you.
We do not state a response time here, because there is no time limit that we have published and keep. A dedicated reporting address will follow once the role addresses exist; until that day, info@basestep.io is the way.
part 6
How and when we test
Automatically with every delivery: if a gate is red, the build does not get through. A regular manual round with keyboard and screen reader across all pages does not exist yet; when it does, the date will be here.
We calculate contrast from the colour values and the transparency that the styles specify, also at the weakest point of every gradient and in both colour modes. That is not a measurement of the pixels a browser draws, and it does not replace one.
This is version 1.0 of this statement, drawn up on . It is updated with every review, and then the version number goes up. A full evaluation has not been carried out yet; once it has, the date will be here.
why this page is voluntary
Not required, and written anyway.
the thresholdfewer than 10 employees
the thresholdat most €2 million annual turnover
basestep falls under the microenterprise exemption for services in the European Accessibility Act: Article 4(5) of Directive 2019/882 exempts businesses with fewer than 10 employees and an annual turnover of at most €2 million from the requirements for services. So this statement is voluntary.
The exemption has no transition period when a business grows: if we pass a threshold, it lapses immediately. That is why we look at that threshold every quarter, and why the homework is already on paper now instead of later under time pressure.
If something does not work for you, we want to know.