Accessibility statement

What is built in

Accessibility requirements were written into the design system rather than retrofitted, so they apply across every screen rather than the ones somebody remembered:

• Status is never colour alone. Every status carries a colour, a shape and a text label together, so it is readable without colour perception.
• Every interactive element has a visible focus ring. It is a defined style in the system, not a browser default that a reset removed.
• Minimum 44×44px targets for controls, which is above the WCAG 2.2 AA requirement of 24×24px.
• Contrast was corrected during design. The original amber measured about 2.2:1 and was replaced; secondary text was darkened. Body text and interface colours were chosen to meet AA contrast ratios.
• Reduced motion is respected. Animation is disabled for anyone whose system requests it.
• Semantic structure. Real headings, lists, tables and landmarks; buttons that are buttons and links that are links.
• Right-to-left support. The layout mirrors properly for RTL languages, with numbers and currency staying left-to-right.
• The marketing site works without JavaScript. Content is server-rendered; scroll animations are progressive enhancement, not a prerequisite for reading the page.

What has not been done

Stated plainly, because a procurement team needs to know:

• No independent accessibility audit. No third party has assessed the product against WCAG 2.2.
• No formal screen-reader testing. The product has not been systematically tested with JAWS, NVDA or VoiceOver.
• No VPAT or Accessibility Conformance Report is available yet.
• No testing with users who have disabilities. This is the gap that matters most, and automated checks are not a substitute for it.

Known limitations

• Dense data tables — timetable grids, the marks entry grid and the ageing report carry a lot of information in two dimensions. They are usable with a keyboard, but the experience with a screen reader has not been validated.
• Drag-to-reorder controls have keyboard alternatives (arrow keys and up/down buttons) because native drag-and-drop is not keyboard operable. Those alternatives have not been tested with assistive technology.
• The product interface is not yet responsive for small screens; it is designed for tablet and desktop. This marketing site is fully responsive.
• PDF output — report cards and receipts are generated for printing and have not been checked for tagged-PDF accessibility.

Telling us about a barrier

If something prevents you using the service, tell us — it is the most useful accessibility input we can get.

Email info@axurs.com with the page or screen, what you were trying to do, and the assistive technology and browser you were using if relevant. We aim to acknowledge within 5 working days and to tell you what we intend to do and roughly when.

If you are unhappy with our response, you can escalate to the accessibility enforcement body in your country — in the UK, the Equality Advisory and Support Service.

What happens next

The honest position is that accessibility has been designed for but not verified. Closing that means an independent audit against WCAG 2.2 AA, screen-reader testing of the dense grids, and publishing a VPAT. When that work is done this page will be updated with the results — including whatever it finds that we did not expect.

Contact

info@axurs.com, or the privacy contact at ▲Privacy contact address — to be supplied for anything that overlaps with data protection.