Policy and ownership
An accessibility policy, named owners and the checks each team runs before release.
Service offering
Accessibility programme
Accessibility built into how every team works, not fixed after each audit.
We set up accessibility as an ongoing programme, not a one-off audit: a policy based on WCAG 2.2, ownership in each team, a remediation backlog and training for designers, developers and content authors. Progress is reported against the national digital accessibility expectations that apply to you.
Programmes in the region cover Arabic content as well as English, including plain-language Arabic, screen reader pronunciation and accessible PDFs, which audits often miss.
What the work involves
Remediation backlog
Known issues ranked by their impact on users, with fixes scheduled into product roadmaps.
Training
Practical sessions for designers, developers and content authors, in Arabic and English.
Decisions grounded in evidence
Every design choice traced back to research, testing or an agreed constraint.
Bilingual by default
Arabic and English designed together, with right-to-left layouts and content reviewed in both languages.
When accessibility needs a programme
A programme is needed when audits keep finding the same issues because no team owns them.
- Accessibility is checked only before launch, if at all.
- Audit findings are fixed once and return in the next release.
- Designers and developers have had no accessibility training.
Talk to us about accessibility programme
Share your constraints, compliance themes and timeline. We will return a phased approach, a staffing model and a risk register for your stakeholders to review.