Accessibility Statement

These documents apply now and are pending final solicitor review. We update them as the Service changes. If anything here does not match what the product does, please tell us at info@eiportal.com.

Operated by: EI Portal Ltd ("we", "us", "our")
Applies to: the Service — eiportal.com, beta.eiportal.com and related EI Portal websites, tools and services
Last updated: 7 August 2026
Defined terms: capitalised terms used but not defined in this document (including "Service", "Tools", "Output" and "Content") have the meaning given in our Terms of Use

1. Our commitment

1.1 We want EI Portal to be usable by as many people as possible, including people who rely on assistive technologies. We aim to meet the internationally recognised Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA as our target standard, and to keep improving as the platform develops.

2. What we do

2.1 We design and build the Service with accessibility in mind, including:

• semantic HTML and a logical reading/heading structure;
• keyboard operability for interactive controls;
• support for light and dark themes, and reasonable colour-contrast targets;
• responsive layouts that adapt to mobile, tablet and desktop screens;
• text alternatives for meaningful images, and labels for form controls that are programmatically associated with the control, so assistive technologies can announce them — an automated build check verifies that every form control in the tools carries an accessible name; and
• respecting your browser/OS preferences (such as reduced motion) where practical.

3. Current status and known limitations

3.1 EI Portal is in active development (beta), and we are working towards full WCAG 2.2 AA conformance. We are aware that some areas need further work, which may include:

• complex engineering charts, plots, schematics and visualisations, which are inherently visual and may not yet have full non-visual (e.g. screen-reader or data-table) equivalents;
• some interactive tool controls and dynamic results that may need improved announcements for assistive technologies; and
• areas still being built or refined.

4. How we test

4.1 We check accessibility manually as we build — keyboard operation, responsive behaviour across screen sizes, and design review in both light and dark themes.

4.2 To be straightforward with you about where we are: we do not yet run automated accessibility testing, and we have not yet carried out a formal screen-reader audit or a full WCAG 2.2 AA assessment. When we do, we will state here the assistive technologies and browsers used and the date of the review.

5. Getting help and giving feedback

5.1 If you have difficulty using any part of EI Portal, or need information in a different format, please contact us — we want to help and to hear about problems so we can fix them:

• Email: info@eiportal.com
• We aim to respond within 5 working days.

6. Enforcement

6.1 If you contact us about an accessibility problem and are not satisfied with our response, you can contact the Equality Advisory and Support Service (EASS) (equalityadvisoryservice.com). Note: the public-sector accessibility regulations (PSBAR 2018) generally do not apply to private companies, but this statement is good practice and supports our duties under the Equality Act 2010.

7. Changes

7.1 We will update this statement as we make improvements and as our testing progresses. The "Last updated" date shows the latest version.