Accessibility
If this site blocked you, that is a defect with a deadline.
This is a statement of what we do, how each claim is tested, and how to report a barrier. Every target below is checked by something that blocks a merge or blocks a release, and the check is printed next to the target it covers.
The bars we hold ourselves to
| Area | Target | How it is checked |
|---|---|---|
| Site and apps overall | WCAG 2.2 level AA | Automated scan on every pull request, blocking the merge |
| Purchase critical text | WCAG 2.2 level AAA for contrast and reading level | Contrast at 7 to 1, reading level checked on every copy change |
| Text scaling | 200 percent with no truncation or overlap | Layout tests at 100, 150 and 200 percent on three viewport widths |
| Keyboard | Every function reachable, focus always visible | A manual pass through every purchase and install flow each release |
| Screen readers | Full flows on VoiceOver, TalkBack and NVDA | An annual audit with assistive technology users, not only tooling |
| Motion | Reduced motion honoured, nothing moving over five seconds | A preference query test in the automated suite |
| Right to left | Mirrored layouts for Arabic, Hebrew, Persian and Urdu | Reviewed by native speakers on every release that touches layout |
| Offline | Profile, balance, plan details and install steps with no connection | An airplane mode run through before every app release |
Where a check is automated it blocks a merge. Where it is manual it blocks a release. Neither is advisory.
Text, contrast and colour
Body text meets a contrast ratio of 4.5 to 1 as a floor, and purchase critical text meets 7 to 1.
Colour never carries meaning on its own. A coverage tier is a label as well as a colour. An error is a word as well as a red border. A plan that has run out says so in text rather than only turning grey. That rule matters most on the pages where money changes hands.
Dynamic type scales to 200 percent. Nothing on the site is laid out with fixed heights that clip at large sizes, and tables scroll horizontally within their own container rather than forcing the page sideways.
The fair use threshold on the buy button stays legible at every size. If you use a browser or system font size larger than the default, the site respects it rather than overriding it.
Keyboard, focus and screen readers
Every function has a keyboard route. The list below is the standard we test against on every release rather than a description of our intentions.
- A skip to content link is the first item in the tab order on every page
- Focus indicators are visible against every background we use and meet the focus appearance rules in WCAG 2.2
- Dialogs trap focus while open, return it to the trigger on close, and close on the escape key
- Form errors are announced, associated with their field, and describe the fix rather than only the fault
- Every image that carries meaning has alternative text, and decorative images are hidden from assistive technology
- Diagrams are inline vector graphics with a role and a label, so the mechanism is described rather than announced as a graphic
- Headings are a real hierarchy, so heading navigation gets you around a country page in seconds
Motion
The reduced motion preference is honoured across the site and both apps.
The brand motif is drawn as a vector with stylesheet keyframes rather than shipped through an animation runtime. It stops completely rather than falling back to something half animated, and it costs a few hundred bytes rather than a quarter of a megabyte of code.
Nothing auto plays with sound, nothing flashes more than three times a second, and nothing moves for longer than five seconds without a control to stop it.
Right to left, properly
Arabic, Hebrew, Persian and Urdu are right to left languages and we treat them as layouts rather than as translations.
Navigation, progress indicators, directional icons, table reading order, form flow and the direction of the install steps all mirror. Numerals, Latin product names and speed figures sit inside the sentence correctly, because the text is handled bidirectionally rather than reversed.
This matters commercially as well as ethically. The throttle number, the refund rule and the fair use threshold are the sentences most likely to be misread, and a broken right to left layout is exactly where a person stops trusting a page.
Twelve languages ship today and every one of them carries the same numbers in the same places.
Offline is an access need
Tested before every release
These four run on real assistive technology rather than on a scanner alone, each has a named owner in the repository, and each blocks a release when it fails.
- VoiceOver, TalkBack and NVDA run the full purchase and install flows, with an annual audit by people who use them every day
- The offline screens are checked in airplane mode before every app release, because that is the state they were built for
- Payment and refund wording is read at 200 percent text on a narrow screen before it ships, because that is where money is at stake
- Persian and Urdu carry the help and legal content in full, and native speakers review every release that touches layout
Report a barrier
Write to accessibility at orbislo.com. Tell us the page, the device, the assistive technology and what happened.
A human replies inside two working days with a severity and a target date. Anything blocking a purchase, an install or a refund is handled as a production incident rather than a backlog item.
You are not filing feedback. You are filing a bug, and we will treat it that way.