Accessibility

MOLOTOK aims to meet WCAG 2.2, Level AA. On 20 September 2026 every page and every shared part of the app was reviewed against it. This page says what that review covered, what it changed, and — at least as importantly — what it did not test.

What has not been tested

The review read the application’s source code and measured its colours. It did not open a browser. Four things follow from that, and they are the reason this page does not use the word “conformant” on its own:

No screen reader has been run

Not one, on any platform. What this page says about how things are announced comes from reading the markup and knowing how it is specified to behave. That is a good prediction and it is not a test.

No page was measured as it renders

Zooming to 200%, narrowing to a phone-width column, and increasing letter and line spacing are all things you do to a page on screen. The review read the source instead.

No automated checker was run

No axe, no Lighthouse. Those find a different class of problem than reading does, and neither substitutes for the other.

Nobody who relies on assistive technology has tried it

This is the one that matters most and the one least within reach of a review. Everything above was checked by somebody who does not need it to work.

What the review checked

Every route in the application and every shared component, read rather than sampled — sixty-eight pages. The criteria that can be settled by reading markup and by measuring colour were settled. Each finding was confirmed by opening the file before anything was changed, because a search result is a candidate and not a fault.

What it changed

• —Every page now has its own title. Sixty-five of them did not, so a row of browser tabs all read the same word.
• —Four controls had no name a screen reader could read — including the tick box on every row of the inquiries list, which announced twenty identical “checkbox, not checked” above a button that discards them.
• —The printable quote and invoice, and the copy a client is sent by link, had no heading of any kind.
• —The lightest grey used for secondary text was too faint to read against the page, and is now dark enough to pass at every size it is used.
• —The outline of a text box was too faint to find. Forms were boxes only if you could already see them.
• —The panel that slides in from the right told screen readers it was a dialog without behaving like one. It now takes keyboard focus, keeps it, closes on Escape and gives focus back.
• —Pressing “use this device’s time zone” changed a setting silently. It now says what it did, out loud.

What was already right

The application can be operated by keyboard throughout, and shows a clear outline on whatever has focus. Every page has one main heading and no skipped levels. Every form field has a label, every image has a description, and every table names its rows and columns. Errors are reported in words that name the field, not by turning it red. Nothing anywhere depends on telling two colours apart. There is a skip link before the navigation, and the page declares its language.

If something here does not work for you

Tell the business you are dealing with. If you work for them, or you are their client, they hold the installation and can raise it with whoever set it up — and they can do it today, which is not true of us.

There is no support address on this page because there is no support desk behind it, and an address nobody reads would be worse than none. The same is true on the privacy notice, for the same reason.

About this statement

Prepared on 20 September 2026 by the people who build MOLOTOK. It is a self-assessment: nobody independent audited it, no certification was issued, and it was not reviewed by anyone who uses assistive technology. It describes the application as it stood on that date, and anything shipped since is outside it.