Accessibility Statement

Our commitment

We design and build for the whole audience, not the median user. Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across xperion.ai. Accessibility is treated as a first-class requirement in design reviews, code reviews, and quality assurance, not as a post-launch fix.

What we have implemented

Structure and navigation

• Semantic HTML5 landmarks (header, nav, main, footer) on every page.
• A visible "Skip to content" link as the first focusable element on each page.
• Heading levels used in logical order, never skipped purely for visual styling.
• Descriptive page titles and unique link text.

Keyboard and focus

• All interactive elements reachable and operable with the keyboard alone (Tab, Shift+Tab, Enter, Space, Arrow keys where appropriate).
• Focus indicators visible on every interactive element, with sufficient contrast against background.
• No keyboard traps. Dialogs and dropdowns can be dismissed with Escape.
• Focus order matches the visual reading order.

Screen readers and ARIA

• ARIA landmarks and roles applied where native semantics fall short.
• aria-label, aria-labelledby, and aria-describedby used for icon-only buttons, custom controls, and form fields.
• Decorative imagery marked aria-hidden="true" so screen readers do not announce noise.
• Dynamic content updates announced through ARIA live regions where appropriate.

Visual design

• Body text contrast of at least 4.5:1 against background, and 3:1 for large text and UI components, per WCAG 2.1 AA.
• Information never conveyed by colour alone; pairs with shape, label, or icon.
• Text resizable up to 200% without loss of content or function.
• Layouts reflow at 320 CSS pixels wide without horizontal scrolling, per WCAG 1.4.10.
• Touch targets at least 24x24 CSS pixels, with 44x44 preferred for primary actions.

Images and media

• Meaningful images carry descriptive alt text.
• Decorative images use empty alt="" and aria-hidden="true".
• SVG icons have accessible names where they convey meaning.
• Video content, where present, is provided with captions and a transcript.

Motion

• Animations and parallax effects respect the prefers-reduced-motion media query and are disabled or reduced when set.
• No auto-playing video, no flashing content above the WCAG 2.3.1 threshold.
• Marquees and tickers pause on hover and focus.

Forms

• Every input has a visible, programmatically associated label.
• Required fields are indicated in text, not by colour alone.
• Validation errors are announced to assistive technology and described in plain language.

Conformance status

Based on our most recent internal audit (May 2026), xperion.ai is substantially conformant with WCAG 2.1 Level AA. "Substantially conformant" means most of the site fully meets the standard, with a small number of known issues being actively worked on. No fully WCAG-conformant site is ever truly "done"; we treat this as an ongoing commitment.

Known limitations

We disclose what we know:

• A small number of legacy decorative assets are still in audit and may lack ideal contrast in their surrounding mesh gradients. Text overlays on those areas meet 4.5:1 against the darkest backing layer.
• One animated SVG signal trace on the home page does not yet expose a textual equivalent. The information it conveys is repeated in adjacent body copy.
• Embedded third-party content (for example, calendar booking widgets on the Book a Call page) is governed by third-party accessibility. We have raised conformance with the providers and review alternatives quarterly.

If you encounter another barrier, please tell us so we can fix it and credit the report.

Assistive technology compatibility

We test against current and previous major versions of the following combinations:

• Desktop: NVDA with Firefox and Chrome (Windows), JAWS with Chrome and Edge (Windows), VoiceOver with Safari (macOS).
• Mobile: VoiceOver with Safari (iOS), TalkBack with Chrome (Android).
• Browsers: latest two major versions of Chrome, Edge, Firefox, and Safari.
• Zoom and reflow: up to 400% browser zoom, plus operating-system text scaling.

Other assistive technologies may also work well. If something does not, we want to know.

Ongoing audits

• Automated checks run on every pull request through axe-core, with no high or critical issues permitted to merge.
• Manual reviews on every major release, covering keyboard navigation, screen reader walkthroughs, and zoom and reflow.
• Quarterly external review covering a sample of pages and flows.
• Annual independent audit against the current WCAG version, with a remediation plan published internally.

How to report a barrier

If you hit a problem using this site, please tell us. We take every report seriously and aim to acknowledge within 2 business days.

• Email accessibility@xperion.ai with the page URL, what you were trying to do, what happened, and (if you can share) the assistive technology and browser you used.
• For an urgent need, copy info@xperion.ai as well.

We will respond with a plan and a target fix date. If a complete fix will take time, we will offer an interim path to get the information or function you need.

Formal feedback and escalation

If our response does not resolve your concern, you may escalate to your local accessibility regulator. In the United States, that is typically the Department of Justice under the ADA; in the European Union and the United Kingdom, national enforcement bodies for the relevant accessibility regulations.

Standards we reference

• WCAG 2.1 Level AA (target conformance level for this site).
• WCAG 2.2 Level AA (we track new success criteria and adopt where applicable).
• Section 508 of the US Rehabilitation Act, by reference to WCAG.
• EN 301 549 for European public-sector procurement reference.

Contact

Accessibility lead: accessibility@xperion.ai. General enquiries: info@xperion.ai.