Skip to content
Sebairo

Company

Accessibility at Sebairo

What works today, what does not work yet, and what we are not going to pretend about. Sebairo has not been audited for accessibility, and this page says so before it says anything else.

Last updated: 2 September 2026

The short answer

If you use a screen reader on Android, Sebairo will not work well for you today. That is not a caveat buried at the bottom of the page — it is the first thing you are entitled to know, because downloading an app that turns out to be unusable wastes your time and your patience.

Other things do work, and work properly rather than approximately: the whole product exists in Arabic with real right-to-left layout, and the website is usable by keyboard and respects a reduced-motion setting. The sections below separate the two honestly.

Sebairo does not

claim WCAG conformance. There has been no accessibility audit and no testing with assistive technology, so a conformance badge here would be a decoration — and it would mislead exactly the people this page is for.

Language and direction — this part is solid

Sebairo is fully bilingual. Every screen in the app and every page on this site exists in Arabic and English — every string in both languages, with none missing — not a partial translation with English leaking through at the edges.

Arabic is laid out by direction rather than mirrored after the fact. Spacing, alignment and icon placement are written in logical terms — start and end, not left and right — so the Arabic build is a first-class layout rather than an English one flipped over.

The website

Keyboard navigation
Every page starts with a skip link, so you are not forced through roughly twenty header controls to reach the content. Menus open on click rather than hover, close on Escape, and report their open state to assistive software.
Reduced motion
If your system asks for reduced motion, the site stops animating. This is honoured, not merely softened.
Works without JavaScript
Every destination in a fold-out menu is also a plain link in the footer, so the site is navigable with scripting disabled.
What is untested
Colour contrast has not been measured against a standard, and no page has been walked through with a screen reader. Both are real gaps, listed here rather than left for you to discover.

The Android app

This is where Sebairo falls short, and the shortfall is specific rather than vague. Interface elements in the app carry almost no descriptions for assistive software to read. A screen reader will reach a button and be unable to say what it does. Buttons that show an icon and no text are the worst case, and there are many of them.

System text size is honoured in one place in the app and not generally, which means enlarging text at the system level will help you in some screens and not in others. Inconsistency of that kind is arguably worse than a clean absence, because it is unpredictable.

Be careful

If you rely on TalkBack, do not install Sebairo expecting it to work. We would rather lose the download than waste your time.

What happens next

  1. Descriptions on every control

    Every icon-only button gets a description an assistive reader can announce. This is the change that moves the app from unusable to usable, so it comes first.

  2. Text size everywhere

    System text scaling honoured across every screen, so the setting means the same thing wherever you are in the app.

  3. Contrast measured

    Colour pairs checked against a standard rather than by eye, on both the app and this site.

  4. Tested with real assistive tech

    Nothing above counts as done until someone has actually driven the app with a screen reader. Until that happens, this page will keep saying so.

Worth knowing

Accessibility work is prioritised in the order above, and this page will be updated when a gap closes rather than when it is planned to close.

Tell us what blocked you

A specific report is worth more than a general one: the screen you were on, what you were trying to do, and the assistive technology you use. Write to support@sebairo.com in Arabic or English — both are read.

An accessibility report is not treated as a feature request. It is a report that someone cannot use the product, which is a different and more urgent category.

Questions people actually ask

Short answers. If yours is not here, the Help Centre answers in more depth.

  • Is Sebairo WCAG 2.1 AA compliant?

    No, and nobody has assessed whether it is close. Claiming otherwise would be easy and dishonest.

  • Does the app work with TalkBack?

    Not adequately. Controls lack the descriptions TalkBack needs, so it will announce many buttons without being able to say what they do.

  • Is there an iPhone version I could use with VoiceOver?

    Not yet — Sebairo ships on Android today. When an iOS build exists, this page will say what does and does not work there too.

  • Can I use the website instead of the app?

    This site is the marketing site and the Help Centre, not the product. Sebairo itself runs in the app, so the website is not a way around the app's gaps.

  • Why publish this before fixing it?

    Because you can decide today whether Sebairo is usable for you, and a page that appears only after the work is done leaves you guessing until then.

Back to top