Localization QA Retainer
For teams shipping continuously without an Arabic speaker on staff.
Arabic quality is not a launch-week problem. It decays: a component is refactored, a stylesheet is regenerated, a new page ships from a template nobody checked. The retainer is the standing arrangement where that decay is somebody's job: scans on a schedule, a human reading the new findings, and a prioritised list rather than an alert nobody triages.
What you get
- Scheduled scans of your Arabic surface, with every release diffed against the last
- A person reviewing new findings, so you are told what matters rather than what fired
- A prioritised fix list each month, ranked by severity against pages affected
- Direct access for the questions that are faster asked than researched
What we need from you
- The URL, and a heads-up when a big release is coming
- One channel where the monthly list should land
Illustrative: what a month's diff looks like
Most months are quiet: a handful of new findings, most of them the same rule firing on new pages built from an unfixed template. The month that is not quiet is the one this exists for, and the diff names it in the first line rather than the fortieth.
Drawn from our own fixtures and public-site scans. Not a client engagement.
Start with a scan
We would rather look before we talk. Give us the URL and we will run the same scan the homepage runs, then you can tell us what you need.