Accessibility statement

What is implemented

• Semantic landmarks and a logical heading order on every page.
• A visible skip link to the main content, and visible focus outlines that are never removed without an equal replacement.
• Keyboard operation for navigation, forms, dialogs and the quote editor, with focus moved into dialogs and returned when they close.
• Form fields with associated labels, instructions and error text that is identified in text rather than by colour alone.
• Status communication using words and icons as well as colour, so a margin warning is never signalled by red alone.
• Touch targets at least 44 pixels high on primary controls.
• Respect for the operating system reduced motion preference, with no motion that delays access to content.
• Text alternatives for meaningful images and decorative elements hidden from assistive technology.

Colour contrast

Body text and interface text are chosen to meet the AA contrast ratio against their backgrounds. Where a colour is used to indicate scope status, such as a matched or unmatched catalogue item, a text label accompanies it.

Known limitations

• The proposal PDF has a tagged text order that follows reading order, but it is not a fully accessible PDF/UA document.
• Large quote tables are usable with a screen reader, but the inline editor is optimised for keyboard focus order rather than for complex table navigation commands.
• Charts and diagrams do not exist in the product, so no chart alternative text is required. If that changes, an accessible summary will be added.

How we test

Accessibility is checked with keyboard-only navigation, browser zoom to 200 percent, a screen reader on at least one platform, and automated checks as part of the build. We also test at phone, tablet, laptop and wide desktop widths.

Reporting a problem

Email hello@myevent-labs.io or use the contact page. Tell us the page, your browser or assistive technology, and what happened. We treat accessibility issues as defects and will tell you when a fix is released.