Skip to main content
SEGHU

Legal

Accessibility Statement

Last reviewed: 4 August 2026 · Next review due: 4 August 2027

This statement applies to the Seghu platform at seghu.org and seghu.vercel.app. Seghu is a product of hibretOne CIC.

We want as many people as possible to be able to use this platform. That includes being able to change text size and contrast, navigate using only a keyboard, and use a screen reader.

How accessible this platform is

We know that parts of this platform are not yet fully accessible. We are working to WCAG 2.2 Level AA and are not there yet. We have audited the platform and are fixing what we found, in priority order.

The following are known not to conform:

  • Some text has insufficient colour contrast. Smaller grey text does not meet the 4.5:1 contrast ratio required at AA. Turning on High contrast in the accessibility menu resolves this.
  • Some controls cannot be reached with a keyboard. A number of interactive elements respond to a mouse click but not to keyboard input.
  • Some controls are not correctly announced. Certain buttons and form fields lack an accessible name, so a screen reader may not describe them usefully.
  • Generated documents are not tagged. The PDFs the platform produces (Articles of Association, CIC36, IN01, filing packs and reports) do not currently carry the structural tagging a screen reader needs. See Alternative formats below.

What we have done so far

  • An accessibility menu offering text size, contrast and saturation options, an easier-to-read font, line spacing and letter spacing, link and heading highlighting, stopped animation, a reading guide and a larger cursor. It is available in 76 languages.
  • A Calm mode button at the top of that menu, which stops movement, softens the colour and opens up the line spacing in one press — so you do not have to work through the individual settings to get a quieter page.
  • A skip link so keyboard users can bypass the navigation.
  • Automated accessibility checks that run whenever our code changes, so new problems are caught before release.
  • Animation and video respect your operating system's reduce motion setting.

Alternative formats

If you need a document in a different format — accessible PDF, Word, large print, plain text or easy read — contact us and we will produce it for you at no cost. We aim to respond within 5 working days.

Email: info@hibretone.org

Reporting accessibility problems

We want to hear about anything that does not work for you. If you find a problem, or need content in a format we do not currently offer, please tell us:

Please tell us the page address and what went wrong. We aim to reply within 5 working days.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) enforces the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this platform's accessibility

hibretOne CIC is committed to making the Seghu platform accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status: this platform is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, because of the non-compliances listed above.

How we tested this platform

We use automated accessibility testing on every code change, and audit colour contrast against the WCAG contrast formula. A full manual audit, including keyboard-only and screen-reader testing across all pages, is planned and has not yet been completed. We will update this statement when it has.

What we are doing to improve accessibility

Our current priorities, in order:

  1. Fixing colour contrast across the platform.
  2. Making every interactive control keyboard operable.
  3. Giving every control a clear accessible name.
  4. Completing a full manual audit, including screen-reader testing.
  5. Making generated documents properly tagged and readable.

This statement was prepared on 4 August 2026 and will be reviewed at least annually, or sooner if the platform changes significantly.