Skip to main content
Skip to content

Accessibility

Accessibility Statement

Omniflux wants Elevate ERP to be usable by everyone who has to use it — students, teachers and office staff alike, whatever they are reading it with. This page records how far that has actually got, including the parts that are not there yet.

What this statement does and does not claim

Elevate ERP works toward the Web Content Accessibility Guidelines 2.1 at Level AA. It does not claim to conform to them, and nothing on this page should be read as a conformance claim, a partial conformance claim or a substitute for one.

There is no VPAT, no Accessibility Conformance Report and no independent accessibility evaluation. None has been commissioned. The gaps listed below were found by our own review, which means the list is a floor and not a ceiling — a formal audit would find more.

What is in place today

Each of these is a specific mechanism rather than a general intention, and each is verifiable in the served page or the stylesheet.

Skip link and one main landmark

Every public page begins with a "Skip to content" link that becomes visible on focus and moves you past the navigation to a single <main> element. Marketing chrome is imported per page, so before this existed a keyboard user tabbed through the whole navigation on every route.

One focus indicator, site-wide

A 2px outline with a 2px offset is drawn on :focus-visible for every focusable element on the public site, from one rule rather than per component. The offset is what keeps it visible where an element sits on a surface close to its own colour. It is deliberately specific enough to survive a component that sets outline-none.

Reduced motion is honoured

Under prefers-reduced-motion the shared transition and card utilities collapse to 1ms, so hover lifts and reveals stop rather than merely shortening.

The site is readable with JavaScript off

Scroll reveals park their content at zero opacity until an observer fires. A noscript rule forces every revealed section visible, so content does not depend on scripting to exist for a text browser, a crawler or a reader with scripting disabled.

Text colours come from a measured ramp

The public palette is a fixed set of ink and brand steps, each annotated in the stylesheet with its measured contrast ratio against the page surface, and three of them are marked as never valid for text. Body copy is specified at 8.97:1 and headings at 17.38:1. That is a constraint on the palette, not a guarantee that every element on every page draws from it correctly.

Touch targets are stated in pixels

The root font size is 15px rather than 16px, so a rem-based target lands about 6% short of its nominal size — a 2.75rem control measures 41.25px, not 44px. Minimum target sizes are therefore written in literal pixels wherever they are set. This has been applied as pages are reworked; it is not yet true of every control in the product.

Six interface languages, including a right-to-left one

The signed-in application ships English, Hindi, Marathi, Tamil, Arabic and Chinese, each with a real dictionary behind it, and sets the document direction to right-to-left for Arabic. These public marketing pages offer no language control and are English only.

A dark theme in the signed-in product

The application follows the operating system light or dark preference, which helps readers with light sensitivity. These public pages are pinned light and do not follow it.

Known gaps

These are open. They are listed because a statement that named no specific failure would be describing a product that had never been looked at.

  • Charts are not usable with a screen reader. Dashboard and analytics charts are drawn as SVG with no text alternative and no guaranteed tabular equivalent, so the data in them is unavailable to anyone not reading it visually.
  • Generated PDFs are untagged. Report cards, receipts, datesheets, ID cards and the brochure are produced by a library that writes no document structure, so an exported PDF is not navigable by heading, table or reading order.
  • Two embedded third-party components carry their own limitations that this project does not control: the rich-text editor used for paper authoring, and the live map used for transport tracking.
  • The review behind this page has covered the public marketing pages. The signed-in application has not been through the same pass, so contrast, focus visibility and target size are less consistent there.
  • Nothing has been tested against a screen reader as a matter of routine. There is no assistive-technology test matrix and no automated accessibility check in the build.

Report a barrier

If something on Elevate ERP is unusable for you, tell us and it goes on the list above until it is fixed. Email [email protected] with the page address, what you were using to read it, and what happened. A description of the barrier is more useful to us than a guess at the cause.

There is no support rota and no overnight cover, and mail is answered in the order it arrives. The one response time that is committed to is the statutory one: a grievance raised with the Support & Grievance Contact at [email protected] is answered within 48 hours.