Accessibility

Last updated: 10 September 2026

Our target

Xiliro aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Accessibility is treated as an ongoing responsibility rather than a task that is ever finished once and for all. Pages are reviewed and improved as issues are found. Xiliro does not claim full or certified conformance with WCAG 2.2 AA, or with any other accessibility standard.

What is already in place

• Xiliro is designed so that interactive controls can be operated by keyboard alone, without a mouse or touchscreen.
• A visible focus outline is designed to appear on the control currently in use.
• A skip link lets keyboard and screen-reader users jump straight to the main content.
• Form fields have programmatically associated labels, and related fields are grouped with a fieldset and legend where appropriate.
• Validation errors are shown next to the relevant field and announced to screen readers.
• A calculated result is announced to screen readers as it appears.
• Text and interface colours are checked against WCAG contrast requirements.
• Pages are responsive and usable at a range of screen sizes and zoom levels.
• Motion and transitions are minimal, and are disabled for anyone whose system is set to reduce motion.

Known limitations

Some tools produce results (a long number, a generated QR code, a block of text) that may be easier to work with visually than by screen reader in certain browsers or assistive technology combinations. If you find a specific barrier of this kind, please report it; a targeted report against a real tool is far more useful than a general check we might otherwise never think to make.

Reporting a barrier

If you find something on Xiliro that is difficult or impossible to use with a keyboard, screen reader, or other assistive technology, contact help@xiliro.com. It helps to say which tool or page you were using, what you were trying to do, and what happened instead. See the Corrections Policy for how reports are investigated.