Accessibility Statement

At Fylix, we believe that everyone should have equal access to our tax filing platform, regardless of their abilities or the technologies they use. We are committed to providing an inclusive experience that empowers all users to manage their taxes independently.

Accessibility is not a one-time project but an ongoing effort. We continuously evaluate and improve our platform to ensure it meets the needs of users with diverse abilities, including those who:

• Use screen readers or other assistive technologies
• Navigate using only a keyboard or alternative input devices
• Have visual, auditory, motor, or cognitive impairments
• Use mobile devices, tablets, or older browsers
• Experience temporary limitations or situational disabilities

Fylix aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines are developed by the World Wide Web Consortium (W3C) and are the international standard for web accessibility.

WCAG 2.1 Principles

WCAG 2.1 is organized around four principles, often referred to as POUR:

• legal.accessibility.sections.standards.principles.perceivable
• legal.accessibility.sections.standards.principles.operable
• legal.accessibility.sections.standards.principles.understandable
• legal.accessibility.sections.standards.principles.robust

We also consider the UK Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 and the Equality Act 2010 in our design and development practices.

Fylix includes accessibility measures that are being expanded and verified. Where verification is incomplete, this is stated below:

3.1 Keyboard Navigation

• Shared controls use standard keyboard interactions such as Tab, Enter, Space and Arrow keys; complete keyboard-only testing of every workflow is still in progress
• Shared controls include visible focus indicators; end-to-end focus visibility is still being manually reviewed
• Pages are designed to follow a logical tab order, with manual verification of authenticated workflows still in progress
• Skip links allow users to bypass repetitive navigation on public, authenticated application and administration layouts

3.2 Screen Reader Support

• Shared layouts use semantic HTML landmarks and headings; legacy pages remain under review
• Shared complex controls use ARIA through established component patterns, with authenticated workflows covered by expanding automated checks
• Meaningful imagery is intended to have text alternatives and decorative imagery is hidden from assistive technology; a complete manual inventory is pending
• Most links use descriptive destination or action text; link-purpose review is ongoing
• Shared form fields provide associated labels, with legacy and authenticated forms being audited

Automated accessibility checks are in place. A complete manual screen-reader pass with NVDA, JAWS, VoiceOver and TalkBack has not yet been completed.

3.3 Visual Accessibility

• Automated contrast checks cover public and selected authenticated pages; remaining states and themes are still being verified
• Shared status components use text or icons in addition to colour; a full product-wide audit is ongoing
• Layouts are designed to support browser text resizing, but 200% zoom remains part of the manual test plan
• Readable fonts with appropriate sizing and spacing
• A high-contrast theme is available; complete workflow validation in that theme is still in progress

3.4 Forms & Error Handling

• Shared forms use associated labels and instructions; remaining legacy fields are being audited
• Core forms provide descriptive error messages, with error association and announcement being expanded
• Core forms identify required information, but product-wide programmatic verification is incomplete
• Input validation provides feedback in core workflows; consistent live announcement is still being reviewed

3.5 Responsive Design

• Responsive layouts adapt to common screen sizes; compact and legacy screens remain under review
• Shared controls are designed for touch use, but a product-wide 44 by 44 CSS pixel target-size audit is pending
• Core layouts are designed to reflow at narrow widths; tables use labelled scrolling regions where reflow is not practical, and 320px manual verification is ongoing
• Portrait and landscape orientations both supported

3.6 Time & Motion

• A consistent user-facing warning and extension control for authentication expiry has not yet been verified
• Fylix does not impose a task-completion timer on core forms; HMRC or third-party session constraints may still apply
• Reduced-motion preferences are supported, and moving marquee content pauses on pointer hover or when keyboard focus enters it

While we strive for full accessibility, we acknowledge the following current limitations:

• legal.accessibility.sections.limitations.items.pdf
• legal.accessibility.sections.limitations.items.charts
• legal.accessibility.sections.limitations.items.third
• legal.accessibility.sections.limitations.items.legacy

We are actively working to address these limitations in upcoming releases.

We are continuously enhancing accessibility. Our roadmap includes:

• legal.accessibility.sections.improvements.items.q1
• legal.accessibility.sections.improvements.items.q2a
• legal.accessibility.sections.improvements.items.q2b
• legal.accessibility.sections.improvements.items.q3
• legal.accessibility.sections.improvements.items.ongoing

Our current validation and planned assurance work includes:

• legal.accessibility.sections.testing.items.automated
• legal.accessibility.sections.testing.items.manual
• legal.accessibility.sections.testing.items.user
• legal.accessibility.sections.testing.items.third

This accessibility statement was last reviewed on 2026-08-25 and reflects the current state of Fylix.

We welcome your feedback on the accessibility of Fylix. If you encounter accessibility barriers, have suggestions for improvements, or need assistance using the platform, please contact us:

When reporting an accessibility issue, please include:

• The page or feature where you encountered the issue
• A description of the problem and how it affects you
• The assistive technology or browser you were using (if applicable)
• Any error messages or screenshots (if relevant)

We aim to respond to accessibility inquiries within 2 business days and will work with you to provide a suitable alternative or fix the issue as quickly as possible.

If you require information about Fylix in an alternative format (large print, audio, braille, etc.), please contact our accessibility team. We will work with you to provide the information in a format that meets your needs, typically within 5 business days.

If you are not satisfied with our response to your accessibility concerns, you may escalate the matter to:

• legal.accessibility.sections.enforcement.items.eass www.equalityadvisoryservice.com
• legal.accessibility.sections.enforcement.items.ehrc www.equalityhumanrights.com

These organizations provide independent advice and support on disability rights and accessibility under the Equality Act 2010.