Accessibility statement

Built to WCAG 2.2 AA, in English and Arabic

We design remote-pro.ai to WCAG 2.2 Level AA, in English and Arabic. This statement says where we stand, what is not fully accessible yet and how to reach us.

In this document

  1. 1What this statement covers
  2. 2Arabic that works with assistive technology
  3. 3How we check
  4. 4What is not fully accessible yet
  5. 5Tell us about a barrier

In short

Remote Pro Ai designs its website to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, in English and Arabic. WCAG 2.2 is the W3C Recommendation of 12 December 2024; Level AA conformance means meeting its 55 Level A and AA success criteria. This statement says where we stand, what is not fully accessible yet and how to reach us.

Our target is WCAG 2.2 Level AA. Today we are partially conformant, and this page lists what is not fully accessible yet.

Key terms at a glance

  1. Standard

    WCAG 2.2 Level AA.

  2. Conformance status

    partially conformant. Some content does not yet fully conform; the known limitations are listed below.

  3. Basis

    self-assessment by Remote Pro Ai, October 2026. No independent audit has been carried out yet.

  4. Scope

    remote-pro.ai in English and Arabic, including the booking-flow preview and the free tools, and the public Trust Center pages.

  5. Not yet in scope

    Client OS, Talent OS and the status page, which are covered from the day each goes live.

  6. Languages

    English (left to right) and Arabic (right to left), checked separately.

  7. Checks

    automated accessibility checks on every build, and a manual keyboard and screen-reader checklist in release QA.

  8. Feedback

    we acknowledge a reported barrier within 2 working days and send a fix plan or workaround within 10.

Conformance status
Partially conformant with WCAG 2.2 Level AA (self-assessed, October 2026).

Statement version 1.1 · prepared October 2026 · reviewed at least every 12 months and after major releases

What this statement covers

The public website first; each portal joins the statement when it goes live.

AreaWhat it isCovered today
remote-pro.aiMarketing site, booking-flow preview and free tools, in English and ArabicYes
trust.remote-pro.aiTrust Center pages and document requestsYes
Client OS (app)Client portal, in product-tour previewFrom its live launch
Talent OS (talent)Engineer portal, in product-tour previewFrom its live launch
status.remote-pro.aiService status pageFrom its live launch

Documents we publish as PDF, such as contract templates, are produced with tags and a logical reading order. Any document can be sent as accessible PDF, plain text or Arabic on request.

Arabic that works with assistive technology

Arabic pages are built right to left from the start, not mirrored afterwards.

  • Correct language and direction attributes on every page and on mixed-language content
  • Logical reading order and focus order in right-to-left layouts
  • Icons with direction, such as arrows, mirrored where meaning depends on direction; the logo is never mirrored
  • Western digits in Arabic text for consistent screen-reader output
  • Form errors and status messages announced in the page language

How we check

Automated checks catch some issues; people catch the rest.

CheckHowWhen
Automated rules (axe-equivalent)Every template, English and Arabic, at phone and desktop widthsEvery build
Colour contrastComputed contrast of text and controls against WCAG 2.2 AAEvery build
Keyboard onlyEvery journey can be completed without a mouse, with a visible focusRelease QA
Screen readersVoiceOver (macOS, iOS) and NVDA (Windows) on the main journeysRelease QA
Zoom and reflow200% text zoom and 320 px width (400% zoom) without loss of contentRelease QA

An independent audit against every WCAG 2.2 AA success criterion is planned before the platform leaves preview. We will publish the auditor’s name, the date and an accessibility conformance report (VPAT 2.5 INT) here when it is complete.

What is not fully accessible yet

Known limitations from our October 2026 self-assessment, each with its WCAG criterion and the fix.

LimitationWhereWCAG 2.2 criterionWorkaroundFix
The menu button can fall outside the screen at 320 px width or 400% zoomEnglish pages, smallest phones1.4.10 ReflowUse the sticky “Build my squad” bar or the footer linksOctober 2026 release
Some Arabic headings with long product names scroll sideways at 320 pxTwo Arabic pages1.4.10 ReflowRotate the phone or zoom outOctober 2026 release
Low contrast on the booking-summary total and on squad composition linesBooking flow; hire page1.4.3 Contrast (Minimum)The same figures appear in the quote PDF and in the line itemsOctober 2026 release
Some chips and small links are below 24 by 24 pixelsHome practice chips; pricing links2.5.8 Target Size (Minimum)The same destinations are in the main menuOctober 2026 release
Generic “Read more” linksNot-found page2.4.4 Link PurposeLink destinations are in the main menuOctober 2026 release
Some “Download PDF” buttons open the browser print dialog instead of a fileTools and quote preview4.1.2 Name, Role, ValueChoose “Save as PDF” in the dialog, or email us for the documentWith the live platform

Third-party components that are not connected yet: payment, e-signature and identity-verification screens run only in the live platform. Before launch we will list any limitation they have here, with an assisted alternative (bank transfer, assisted signing, assisted verification).

Roadmap line
An item moves off this list only after its fix ships and passes a retest.

Tell us about a barrier

If something blocks you, we want to know, and a person will answer.

  • Email

    info@remote-pro.ai, subject line “Accessibility”

  • Phone or WhatsApp

    +20 109 277 6977

  • Security issue found while testing

    security@remote-pro.ai

  • Personal data in a report, or a privacy question

    privacy@remote-pro.ai

  • Response

    acknowledgement within 2 working days, and a fix plan or workaround within 10 working days

  • Assisted alternative

    if a barrier stops you completing a task, such as booking a call or signing, we complete it with you by phone or email straight away

  • Alternative formats

    ask for any document as accessible PDF, plain text or Arabic

Sources, accessed 9 October 2026
W3C, Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation 12 December 2024: w3.org/TR/WCAG22 · Directive (EU) 2019/882 (European Accessibility Act): eur-lex.europa.eu/eli/dir/2019/882/oj

Frequently asked questions

Book a scoping call

20 minutes with a solutions architect. No sales script.

Today this statement covers remote-pro.ai in English and Arabic, including the booking-flow preview and the free tools, and the public Trust Center pages. Client OS, Talent OS and the status page join the statement from the day each goes live, and we will update this page when they do.

Arabic pages are checked on their own, not assumed to work because English does. We check reading and focus order in right-to-left layouts, mixed Arabic and English content, and screen-reader output with Arabic voices in VoiceOver and NVDA. Issues found in Arabic are tracked separately from English ones.

Not yet. Our conformance status is self-assessed (October 2026). An independent audit against every WCAG 2.2 AA success criterion is planned before the platform leaves preview, and we will publish an accessibility conformance report (VPAT 2.5 INT) with it. Until then, ask for our self-assessment by email.

A person acknowledges your report within 2 working days and, within 10 working days, sends a fix plan or a workaround. If the barrier stops you completing a task, such as booking a call or signing, we complete it with you by phone or email straight away while the fix is built.

We design to WCAG 2.2 AA, which the harmonised European standard EN 301 549 builds on. The European Accessibility Act, Directive (EU) 2019/882, has applied since 28 June 2025. We review this statement at least every 12 months and after major releases, and we publish the audit date and status here.

Start today

4 working days

Your team can be working within 4 working days of signature.