Accessibility Statement

1. What this statement covers

It applies to everything we build and run ourselves:

• The OASIS HUB public website — the pages you are reading now.
• The OASIS HUB management dashboard — the platform used by charge point operators, mobility service providers and fleet managers.
• The GC EVCharging driver app for Android and iOS.

Charging hardware, and the sites our customers publish themselves on their own branding, are outside our control and are not covered here — although we will always pass a report on to whoever can act on it.

2. Conformance status

We measure ourselves against the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA — the standard referenced by EN 301 549 and by the European Accessibility Act.

OASIS HUB is partially conformant with WCAG 2.2 level AA. Partially conformant means that most of the standard is met and that the exceptions we know about are listed in section 4. We do not claim full conformance, and we will not claim it until the product has been tested by people who use assistive technology every day.

The assessment is our own: an automated check that runs over the platform's screens on every test run, plus a manual review of markup, colour contrast and keyboard operation. An independent audit is planned.

3. What we have done

Accessibility is applied across every screen at once rather than page by page, so a fix reaches the whole platform — including screens added by add-ons and interfaces the browser builds after the page has loaded.

• Every button and link that shows nothing but an icon now has a name a screen reader can read out. 170 of them had none.
• Every table says which column and which row a cell belongs to. 1,188 header cells across 231 tables carried no such marking.
• Every page declares the language it is written in, so a Portuguese page is not pronounced with English phonetics.
• Form fields have names, say when they are required, say when they are wrong and why, and tell the browser what they are for so it can fill them in.
• Every field carries a plain-language explanation that is read out when the field is reached, rather than being locked inside a hover.
• Dialogs are announced as dialogs and carry their own title. Notices that flash in a corner are spoken instead of merely being seen.
• Each page has a main landmark and a skip link, so keyboard users do not walk through fifty navigation links to reach the content.
• Focus is always visible, in a colour derived to stand out against whichever theme is in use.
• Colour contrast was measured across all nine themes we ship. Body text was never the problem; button labels, links and field borders were. All of them now meet the AA thresholds, on every theme, without repainting anybody's brand colours.
• Every word the platform speaks to assistive technology is translated, so a Portuguese screen reader says Eliminar, not Delete.

4. Known limitations

We would rather list these than let you find them:

• No testing with real assistive technology yet. What is described above is structurally correct and automatically verified, but it has not been walked through with NVDA, JAWS or VoiceOver. That test is being commissioned.
• Reading order and keyboard traps in the heaviest screens — the dashboard designer and the visual query builder — have not been fully reviewed.
• Chart colours, status dots and gauges have not been measured for contrast, and a few tables still tell rows apart mainly by colour.
• Maps and payment provider windows come from third parties. Their accessibility is theirs, but we raise every problem you report with them.
• The PDFs we generate — invoices and reports — are not tagged for screen readers. Any of them can be supplied in another format on request, and tagging them is on the list.

5. If something is unusable, we will do it another way

If any part of OASIS HUB is unusable for you, we will get you the same information or complete the same transaction another way — by email, by telephone, or with a member of our team doing it with you. There is no charge, and you do not have to explain why.

A high contrast theme is among the themes the dashboard ships. It is an option, not a substitute: the default theme is expected to be usable on its own, and is measured as such.

6. Tell us what did not work

Reports from people who depend on assistive technology are the most useful thing we receive, and they are acted on. You do not need to know the standard or the terminology — describing what happened is enough.

If you can, tell us the page or screen, what you were trying to do, the browser and assistive technology you were using, and what happened instead.

7. If our answer does not satisfy you

You may refer the matter to the accessibility enforcement body in your country. In Portugal that is the Agência para a Modernização Administrativa (AMA). Every European Union Member State designates its own; tell us where you are and we will point you to the right one.

8. How this statement was prepared

• It was prepared on 26 August 2026 by Global Charging Lda.
• It rests on a self-assessment: an automated check that runs over the platform's screens on every test run, and a manual review of markup, colour contrast and keyboard operation.
• It is reviewed whenever the platform changes materially, and at least once a year.