Service
Bilingual and accessible, or not finished.
Automated testing, Arabic and English quality, accessibility testing, performance and resilience work — treated as delivery requirements with acceptance criteria, not as a phase that gets compressed when the date moves.
Who this is for
- Organizations delivering to Arabic- and English-speaking users as equals
- Public-sector and public-benefit bodies with an accessibility obligation to meet and evidence
- Buyers whose acceptance process requires documented test results
- Teams whose systems face predictable seasonal peaks
The problems this addresses
- Arabic delivered as machine translation, with layout, sorting, numerals and forms untested right-to-left
- An accessibility statement written from a template, with no testing behind it
- A test suite that covers the code that was easy to test rather than the paths that matter
- Performance discovered in production, at the busiest period of the year
- User acceptance treated as a demonstration rather than as evidence
What changes
- Arabic is a tested product surface, not a translated afterthought
- Accessibility barriers are found by testing rather than reported by a user
- The critical operational paths have automated coverage that survives the next change
- Behaviour under peak load and under partial failure is known before it is needed
What Kerah can deliver
Capability, not a claim of past work. Final scope is established through discovery.
- Automated unit, integration and end-to-end test design
- Right-to-left layout, input, sorting and numeral testing
- Arabic and English content and terminology quality assurance
- WCAG 2.2 AA testing with assistive technology, keyboard and zoom
- Accessible document and report output testing
- Performance, load and soak testing against realistic profiles
- Resilience and failure-mode testing, including degraded connectivity
- User acceptance test design and evidence capture
What you receive
Artefacts, not activities. Each one is something you can hold, read or run after the engagement.
- Test strategy and acceptance criteria
- Automated test suites, run in the delivery pipeline
- Bilingual quality assurance report
- Accessibility test results, with severity and remediation status
- Performance and resilience test results
- User acceptance evidence pack
How the engagement runs
- Arabic as a product, not a translation
- Right-to-left layout, mixed-direction text, numerals, sorting and form behaviour are tested as product surfaces by people who read the language, because a translation pass finds none of those.
- Test the accessible path, do not assert it
- Keyboard operation, focus order, announcement, contrast and zoom are exercised against the running system. An accessibility statement written without testing is a claim, and claims get checked.
- Load before launch, not after
- Peak profiles are drawn from the organization's actual calendar — the month-end close, the enrolment window, the seasonal campaign — and tested against, rather than discovered in production.
Commercial shape. Included in every delivery engagement with defined acceptance criteria, and available as a standalone assessment of an existing system.
Raised from the start, not before launch
Architecture, security and data decisions that are cheap to make early and expensive to retrofit.
How Kerah approaches security- Whether Arabic content will be written natively or translated, and who reviews it
- Which accessibility standard the organization is obliged to meet, and who evidences it
- What the realistic peak is, and which functions must survive it
- How the system should behave on a poor connection, which is the normal case away from a desk
- Whether generated documents and reports must also be accessible
Where this stops
- Kerah tests against WCAG 2.2 Level AA and reports findings. It does not issue an audited conformance statement — that requires an independent evaluation Kerah does not perform on its own work.
- Kerah does not provide certified translation or legal-document translation services.
- Testing gives evidence about the paths that were tested. It is not a guarantee that a system is defect-free, and Kerah will not describe it as one.
- Independent accessibility audit, where required, is commissioned from a specialist third party.
Other services
Discovery and Architecture
A documented blueprint with a target architecture, a permission and data-role map, a phased roadmap and a scope you can approve, price or decline on evidence.
Enterprise Systems
One operational system where work is assigned, decisions are recorded, permissions are explicit and reporting comes from the same data people work in.
Digital Product Engineering
A designed, accessible product with a secure back end, built around the tasks people actually perform and measured after release.
Cloud, Data and Integrations
Defined interfaces, a documented data model and monitored flows, so information moves once and reporting can be trusted.
AI and Intelligent Automation
A bounded use case with defined success criteria, evaluation against representative cases, human review where it matters, and a fallback when the model is unavailable.
Managed Evolution
A defined support and release model with security maintenance, an owned backlog and a roadmap reviewed on a set cadence.
Security and Privacy Engineering
A system whose access model, data inventory, encryption, logging and deletion behaviour were designed together — and the documentation an assessor asks for, produced as delivery output rather than reconstructed afterwards.
Discuss testing and accessibility.
Tell us what is not working today, who it affects and what a better outcome would change.