Accessibility at Hubby

Touch and interaction

Every primary action meets or exceeds the minimum touch-target sizes recommended by both Apple and Google (at least 44px). Interactive elements are real buttons, so assistive technology recognises and announces them correctly, and consent switches report their on/off state programmatically, not by appearance alone. Every Android screen has an explicit back control, so you are never dependent on system gestures, and step indicators are tappable, so you can move between steps rather than being forced through a fixed sequence.

Colour and contrast

Our core text and button combinations meet the WCAG AA contrast threshold, and help and support entry points keep the same high-contrast treatment in partner-branded versions of the app, so the way out is always findable regardless of theme.

Motion

The app respects your device's reduced-motion setting: animations resolve immediately to their end state instead of playing. Nothing blinks or pulses; only intentional loading indicators repeat.

Legibility

No text is set below 12.5px, body copy runs 14 to 17px with headings from 18px, and line lengths are constrained rather than running edge to edge, which helps readers with dyslexia and low vision.

Comprehension

Installation instructions pair every written step with a real screenshot of your device family, so Samsung, Pixel, Xiaomi and iPhone users each see their own interface with the terminology their own settings actually use, following each device's real behaviour. Progress is always explicit, with numbered stages, completion checkmarks and a stated next step. Advanced troubleshooting sits behind plain-language prompts, available when needed and out of the way when not, and if an installation fails, a guided recovery path lets you copy the activation code with a single tap instead of typing it by hand. Consent and legal information is disclosed progressively, separating what is required from what is optional instead of presenting a wall of text.

Web application

Accessibility was taken into account during development of the web application. The web application is a single-page application. On 28 July 2026 we tested it with the automated testing tool axe against WCAG 2.1 level AA. The views tested were entry, eSIM installation, data balance, checkout and the withdrawal function.

The automated test identified issues that have not yet been resolved. These are described in the known limitations section below. We plan to have them resolved by 1 December 2026.

We have not yet carried out a manual assessment or testing with assistive technologies. Automated testing tools detect only a portion of possible barriers. A manual assessment, including keyboard operation and testing with screen readers, is also planned for 1 December 2026.

Website

Assessed with automated accessibility testing alongside the web application.

Web application (identified by axe on 28 July 2026)

The automated test of 28 July 2026 identified issues in the web application that we are currently resolving. We plan to have them resolved by 1 December 2026. As no manual assessment has yet taken place, we cannot rule out further barriers that automated testing does not detect. A manual assessment, including keyboard operation and testing with screen readers, is also planned for 1 December 2026.

Screen readers

Instruction screenshots are currently marked as decorative, so a screen-reader user hears the written step text but no description of what the screenshot shows. Some decorative icons are not yet hidden from assistive technology and may be announced as unlabelled elements. Progress and completion, for example when your eSIM finishes installing or activates, are currently conveyed visually only and not announced.

Keyboard and focus

We have not yet defined custom focus indicators, so keyboard users rely on the platform's defaults, which are hard to see against some of our darker buttons.

Colour

Some status indicators rely mainly on colour to distinguish states. Icons help in some places, but state is not yet reliably distinguishable without colour perception.

Text size

Text sizes in the app are fixed within the ranges described above and do not yet follow your device's system text-size setting. At larger accessibility text sizes, some cards and buttons would clip or overflow, which is why scaling support requires layout work rather than a switch.

Video

Our walkthrough videos are silent and visual-only, without captions, transcripts or audio description. The numbered step text alongside them covers the same ground in writing, but is not a full substitute. The floating video player's behaviour is also not yet explained in the app, so some of its features may go undiscovered.

Device settings screens

Part of eSIM installation happens in your device's own settings, which are controlled by Apple, Google, Samsung or Xiaomi rather than Hubby. Our instructions mirror those screens, but their accessibility is determined by the device maker.