Accessibility statement.

01 Standard and approach

This site aims to conform to WCAG 2.1 Level AA. It has not been formally certified by a third party. AA is the same standard we hold client work to, and holding our own site to a lower one would make the claim worthless.

Accessibility here is a build gate rather than an audit that happens at the end. An axe scan against WCAG 2.1 AA runs in CI on every route, at a desktop and a mobile viewport, alongside keyboard and heading-structure checks, on every change.

02 What has been verified

• Text colours are measured against the darkest ground each one is used on, not only the page background. Secondary text measures 8.1:1 and tertiary text 5.5:1 on the page ground, and tertiary text 4.9:1 on the darkest ground it appears on
• Every interactive element is reachable and operable by keyboard, with a visible focus indicator that is never removed
• Motion respects prefers-reduced-motion: entrance animations and illustration drawing do not run
• Headlines and content visible on arrival are never hidden in order to animate in; motion only applies to content entering from below the fold, and its resting state is always the finished page
• Headings descend in order, one h1 per page, with semantic landmarks throughout
• Colour is never the only carrier of meaning — every status also has an icon or a text label
• Every form field has a visible label, and errors are written out beside the field they refer to and announced to assistive technology, not only shown in colour
• Buttons, navigation links and form controls give a touch target of at least 44 by 44 pixels
• Drawn illustrations, including the product interface drawings, are decorative: they are hidden from assistive technology, and the point each one makes is stated in the text beside it. On phone-width screens they are not shown at all, so they never push content down
• Content reflows to 320 pixels wide without horizontal scrolling

03 Known limitations

Stated plainly, because a conformance claim with no exceptions is either untrue or untested.

• Product pages show drawn interfaces rather than real screenshots. Because the drawings are decorative, no description of the figure itself is offered; the product is described in the text.
• Inline text links inside paragraphs are sized by the text around them rather than to 44 pixels, which WCAG 2.1 AA permits.
• The journal has not yet been tested end to end with a screen reader on a long article. Code blocks and callouts are the likely problem areas.
• We have not yet completed structured testing with screen readers or voice control software across the whole site.

04 Testing methods

05 Reporting a barrier

If something here does not work for you, please tell us. Write to hello@mobilebytesensei.com and describe what you were trying to do, what happened, and the assistive technology you were using if that is relevant.

We will acknowledge within two working days and tell you what we intend to do and by when. If a fix will take time, you will get an interim way to reach the same outcome — usually a person.

You will not be asked to prove the problem or to fill in a form to report that a form does not work.

06 Alternative formats

Any content on this site is available another way on request — plain text, larger print, or read to you over a call. Ask at hello@mobilebytesensei.com. There is no process and no cost.

07 Scope of this statement

This statement covers mobilebytesensei.com, operated by Mobilebytesensei Private Limited. It describes our aims and current state and is not a warranty. Products we build for clients are covered by their own statements, and the accessibility standard for that work is agreed in each contract.

Third-party content embedded here — currently none — would be outside our control and named explicitly if it existed.