Accessibility

The standard

Standkeep targets WCAG 2.1 level AA. It has not been through a formal third-party audit, so this is a statement of the work done and the results measured, not a certification.

What has been done

• Contrast is measured, not eyeballed

  Every colour pair in the interface was measured against the background it actually sits on, in both light and dark mode, and the ratios are recorded beside the values. The measuring has found and fixed three real failures — a missed deadline rendering at 2.75:1 in dark mode, which had made the single most important state in the product close to unreadable; and, on 9 September 2026, the horizon's missed and due markers, at 2.1:1 and 2.4:1 in dark mode, now 7.2:1 and 8.5:1. A test now refuses the mistake behind all three: a fill colour, chosen to carry white text, painted as a dot or a marker against the page.

• Measured by machine, across the whole product

  On 9 September 2026 every public page and every signed-in page — the dashboard, all five tabs of a corporation, the next-30-days book, the members page and the administrative console — was run through the axe-core rule set, in light and dark mode, at desktop and phone widths. It found three things, all fixed the same day: a table that scrolled sideways but could not be reached from the keyboard, action columns whose headers were empty, and the navigation rail's account block sitting outside any landmark. Nothing at level A or AA that the rules can see remains. On 14 September 2026 the invoicing pages — the invoice list, clients, taxes and items, settings, tax season, an issued invoice, a credit note and the draft editor — were run through the same rules in both languages, light and dark, at both widths: 176 page loads. It found two things, both fixed the same day: a heading that skipped a level in the editor, and a payments table whose name repeated its section's. On 17 September 2026 the page for the mobile apps, and the three pages the store badges were added to, were run through the same rules in both languages, light and dark, at both widths: 24 page loads, and nothing found.

• A visible focus ring on everything

  Every interactive element shows a clear focus outline, so the whole product can be used from the keyboard. There was none before; the browser default was all that stood behind keyboard navigation, and it disappeared against a filled button.

• Form controls with a real boundary

  Input borders meet the 3:1 contrast that WCAG asks of a control whose boundary carries meaning, while purely decorative hairlines stay soft.

• Structure and landmarks

  One skip link to the main content, headings in order, labelled form fields, landmarks on the header, navigation, main and footer, and errors announced rather than only coloured.

• The corporation page's tabs are links

  Statutory calendar, Records, Vault, Templates and Calendar feed are ordinary links, each with its own address and the current one marked. They sit in the tab order once, work from the keyboard, and a screen reader announces which is open. Only the open tab is on the page; nothing is hidden behind the others.

• The horizon is a picture of the table beside it

  The twelve-month axis with the deadlines set on it is hidden from assistive technology on purpose: every marker on it is a row of the calendar, in words, with the date, the obligation and the status. The readout that appears over a marker is set on the deep field at 9.6:1 for the date and 15.6:1 for the titles.

• Type that scales

  Everything is set in relative units on one fluid scale, so it responds to your browser's font size instead of ignoring it, and prose keeps a comfortable reading width even on a wide screen.

• Reduced motion is respected

  Transitions are effectively removed for anyone whose system asks for reduced motion.

• Language is declared

  Each page declares its language, and the link to the other language declares the language it leads to — so a screen reader switches voice correctly between English and French.

Known limitations

Being honest about these is more useful than claiming none exist.

• Wide tables scroll sideways

  The calendar and the administrative log carry more columns than a narrow screen holds, so they scroll horizontally inside their own container. Each container is a named region in the tab order, so the keyboard can reach the columns past the edge, but a wide table is still harder work on a small screen than on a large one.

• The horizon's readout needs a pointer

  Hovering a marker on the horizon shows its date and what is due that day. Nothing opens it from the keyboard or by touch, and nothing will: the same date and titles are in the calendar table under it, which is the version assistive technology reads.

• No formal audit yet

  Nothing here has been verified by an independent accessibility auditor or tested end to end with every combination of assistive technology. An automated rule set catches a fraction of what a person using a screen reader would. Reports from real use are therefore genuinely valuable.

• Generated documents

  The resolutions and register-review records Standkeep generates are ordinary word-processor and PDF files. Their accessibility depends on the tool you open them in.

Reporting a barrier

If something here stops you doing what you came to do, open a support ticket and say what happened, on what device, and with what assistive technology if you use one. Accessibility problems are treated as defects, not as feature requests, and you will get a reply about what is being done.

If you cannot use the site at all

Support can take your question by email without you ever signing in, in English or French.

Support