Accessibility

Our commitment

We are working to make Magemcy usable by everyone, and we treat accessibility as part of building a feature rather than something audited afterwards. Where we fall short, we would rather write it down than leave you to discover it.

Conformance status

We measure against the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the standard most accessibility law refers to.

Magemcy is partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the standard is met, but not every part of the product has been verified against every criterion. We have not commissioned an independent audit, and we do not have a VPAT. Saying we are “fully compliant” would be easier and would not be true.

What we have done

• Semantic HTML with proper headings, landmarks and lists, so the structure is real rather than visual.
• Keyboard operation throughout the public site, including a skip-to-content link, visible focus indicators, and Escape to close dialogs and menus.
• Form fields with real labels, help text linked by aria-describedby, and errors announced rather than only coloured.
• Status messages and streaming assistant replies announced through live regions.
• Decorative illustrations, the product mockups, the knight’s animations, the cursor effect, hidden from assistive technology, so a screen reader gets the words and not a fake table.
• Every animation respects prefers-reduced-motion, including the scroll effects and the assistant.
• Text resizes and reflows; content does not depend on colour alone.
• Navigation that works on a phone, not just on a desktop.

Known limitations

Honestly, these are the things we know are not right yet:

• Colour contrast. Some secondary and muted text sits close to the 4.5:1 minimum rather than comfortably above it. We are working through it.
• Complex data tables. The bid comparison and evaluation tables carry a lot of information; their header associations and screen-reader narration have not been fully verified.
• Uploaded documents. Tender documents, certificates and specifications are uploaded by other users. We cannot control whether a supplier’s PDF is accessible, and most are not. Ask the supplier for an accessible version, and tell us if that fails.
• Generated PDFs. Purchase order and invoice print templates have not been tested for tagged-PDF accessibility.
• Screen reader coverage. Testing has been with VoiceOver on macOS and keyboard navigation. NVDA and JAWS have not been covered systematically.

Tell us what we missed

If something is hard or impossible to use, we want to know, a specific report is worth more than any checklist we could run ourselves.

Write to our accessibility contact or use the contact form. Tell us the page, what you were trying to do, and what assistive technology and browser you were using, if you know.

We aim to acknowledge within 3 business days and to tell you what we are going to do about it within 10. If something blocks you from work, say so and we will look for a way through in the meantime.

How this was assessed

By self-evaluation: automated checks, keyboard-only testing, and screen-reader spot checks. Not by an independent third party. When that changes, this page will say so, and if you need formal documentation for a procurement process, tell us what it has to cover.