Skip to main content

    Accessibility Statement

    Our commitment to making Y.O.D.O. accessible and usable for everyone.

    Version 2.4.0Last Updated

    Y.O.D.O. Ltd

    Company No. 15736034

    42 Mayfair Gardens, Southampton, SO15 2TW, United Kingdom

    Contact: info@yodo.ltd

    UK and EEA scope

    Y.O.D.O. is established in the United Kingdom and actively offers the Service to consumers in the United Kingdom and across the European Economic Area. Because we actively target EEA consumers, we treat the Service as in scope of the European Accessibility Act 2025 (Directive (EU) 2019/882), which is enforceable in EU Member States from 28 June 2025. We commit to meeting WCAG 2.2 AA and align with EN 301 549 as the harmonised standard for accessibility of ICT products and services. We also comply with the Equality Act 2010 in the United Kingdom. EEA users who experience an accessibility barrier can use the same reporting route as UK users (info@yodo.ltd, subject "Accessibility"), or contact our EU Representative listed above.

    Y.O.D.O. Ltd ("Y.O.D.O.", "we", "us", "our") is committed to making our website and web application (together, the Service) accessible and usable for as many people as possible. We have a duty under the Equality Act 2010 to make reasonable adjustments to ensure disabled people can access our Service. If you need an adjustment, please contact us and we will do our best to help.

    This Accessibility Statement explains:

    • What we are doing to improve accessibility
    • What standards we aim to meet
    • Known limitations
    • How to report issues and request support

    1. Scope

    This statement applies to:

    • The public website (marketing pages), and
    • The logged-in web application (the Service)

    Some content or features may be provided through third parties (for example identity verification through Persona). Third-party components may have their own accessibility features and limitations.

    2. Our accessibility aim and standard

    We aim for the Service to be accessible in line with WCAG 2.2 AA (Web Content Accessibility Guidelines) as a practical target for a consumer-facing digital product. This includes readers with dyslexia, cognitive impairments, low vision, and other access needs.

    Where we cannot meet this standard immediately for a particular feature, we aim to:

    • Provide an alternative way to complete the action, and
    • Prioritise improvements based on user impact and risk

    3. What we are doing

    We design and build the Service to support accessibility, including (where applicable):

    • Keyboard navigation and visible focus states
    • Meaningful page structure and correct heading hierarchy
    • Sufficient colour contrast for text and interactive elements
    • Atkinson Hyperlegible Next, a typeface developed by the Braille Institute for readers with low vision and dyslexia, used consistently for all text
    • Generous line height, spacing, and a single typeface approach to reduce visual fatigue
    • Labels and instructions for form fields
    • Error messages that explain what to fix
    • Scalable text and layout that works on mobile
    • Alternative text for meaningful images (where applicable)
    • Avoiding content that flashes in a way likely to trigger seizures
    • Periodic audits using automated tools and manual review against WCAG 2.2 AA
    • An accessibility badge in the site footer for quick access to this statement

    We also try to keep language clear and calm, especially where the Service relates to sensitive circumstances.

    We use a combination of automated tools and manual review to assess accessibility. We test across common browsers and assistive technologies where practicable.

    4. Known limitations

    Accessibility can be affected by:

    • Users' device settings, browser extensions, and assistive technologies
    • Third-party services embedded in the Service (for example identity verification flows)
    • Parts of the Service that are new or labelled "coming soon" and are still being refined

    If you find an accessibility barrier, please tell us. We would rather know than guess. If you encounter an accessibility barrier in a third-party component such as our identity verification flow, please contact us. We will explore alternative verification arrangements where reasonably possible.

    5. How to report an accessibility issue

    Email us at info@yodo.ltd with the subject line "Accessibility".

    Helpful details (if you can share them):

    • The page or feature you were using
    • What you were trying to do
    • What went wrong
    • Your device and browser
    • Any assistive technology you are using (optional)
    • Screenshots (optional, and only if you are comfortable)

    Please do not send one-time codes, identity documents, death certificates, passwords, or payment details by email. If documents are needed, we will direct you to the secure in-app flow.

    6. Requesting information in an alternative format

    If you need content from the Service in another format, contact info@yodo.ltd and tell us what you need. We aim to respond within 3 business days and will assess what is feasible.

    7. What we will do when you report a problem

    We will:

    • Acknowledge your message within 3 business days
    • Try to offer a workaround where possible, aiming for within 10 business days
    • Prioritise fixes based on severity and frequency of impact
    • Keep you informed of progress

    Fix timelines depend on complexity, but we take accessibility issues seriously.

    8. If you are not satisfied

    If you are not satisfied with our response to an accessibility concern, you may wish to contact the Equality Advisory and Support Service (EASS) or seek independent advice about your rights under the Equality Act 2010.

    9. Updates to this statement

    We may update this statement as the Service evolves. We will update the "Last Updated" date when we do. This statement was last reviewed on . We aim to review it at least annually and after any material change to the Service.

    10. Conformance status and EAA-aligned disclosures

    Conformance status: Y.O.D.O. is partially conformant with WCAG 2.2 AA. "Partially conformant" means that some parts of the Service do not yet fully conform to the standard. We are working to remediate identified issues on the timeline described below.

    Standards we measure against:

    • Web Content Accessibility Guidelines (WCAG) 2.2, Level AA;
    • EN 301 549 V3.2.1 as the harmonised European standard for accessibility of ICT products and services, treated as the closest practical reference under the European Accessibility Act 2025 (Directive (EU) 2019/882);
    • the Equality Act 2010 (United Kingdom).

    Non-conforming and exempt content (known to us):

    • Third-party identity verification flows provided by Persona Identities, Inc. are subject to that provider's own accessibility conformance. Where a user cannot complete a Persona flow, we offer an alternative verification route on request (see section 4).
    • Embedded third-party content (for example payment processor pages) is governed by the third party's own accessibility statement.
    • Pre-recorded media, where used, may not always include captions or audio description at first publication; we add them on request and aim to add them by default for new media from 2026 onwards.
    • PDF documents downloaded from this site (for example policy PDFs generated via browser print) reflect the live page structure but may not always carry tagged-PDF semantics; an HTML version is always available on the same URL.

    Preparation of this statement: this statement was prepared by Y.O.D.O. Ltd based on a self-assessment combining automated testing (axe-core, Lighthouse) and manual review against WCAG 2.2 AA. We have not yet commissioned an independent third-party audit and are working to schedule one as part of our ongoing conformance programme.

    Feedback and enforcement procedure: if you contact us under section 5 and are not satisfied with our response, UK users may contact the Equality Advisory and Support Service (see section 8). EEA users may complain to the market surveillance authority designated under the European Accessibility Act in the Member State where you reside; a directory is maintained by the European Commission. EEA users may also contact our EU Representative under Article 27 GDPR for routing of accessibility queries (Christina-Eloiza Kouraki, Marasli 29, Athens 10676, Greece, eloizakouraki@yahoo.gr).

    Report an accessibility issue

    For accessibility queries or to report an issue: