Accessibility is often treated as a checkbox before launch. That approach breaks fastest on bilingual products where direction, contrast, focus order, and screen reader labels must work in two reading modes. Inclusive design is not a separate track — it is the quality bar for every screen we ship.
Inclusive design is not a separate track — it is the quality bar for every screen we ship.
What we audit early
- Semantic HTML and logical heading hierarchy in both languages
- Visible focus states that survive RTL mirroring
- Color contrast on primary buttons and error states
- Form labels, hints, and error messages tied to inputs with ARIA attributes
- Keyboard navigation through modals, menus, and language switchers
RTL is not a CSS afterthought
Mirroring layouts without re-testing screen reader order creates silent failures. We validate dir attributes, icon direction, and number formatting in Arabic contexts — especially in financial and healthcare flows where precision matters.
The payoff goes beyond compliance: clearer focus paths, better form completion, and products that enterprise buyers can procure without legal friction.
Practical bilingual a11y traps
- Language switchers that steal focus or skip announcement
- Icons that flip meaning when mirrored (carets, progress steppers)
- Mixed LTR numbers inside RTL sentences without bidi isolation
- Modals that trap focus in EN but leak in AR after DOM reorder
- Skip links that land on English landmarks when the page is Arabic
We bake these into design QA, not a last-week audit. Automated tools catch contrast; they rarely catch bilingual focus order. Pair axe/Lighthouse with a keyboard pass in both locales.
Content and media accessibility
- Alt text written per locale — not machine-mirrored English
- Captions and transcripts for video in the language of the audio track
- Error copy that names the field and the fix in plain language
- Avoid conveying meaning by color alone on status badges
Delivery checklist for studio sprints
- Definition of done includes keyboard + screen reader smoke on critical path
- Design tokens include focus ring and contrast-approved pairs
- Component library documents RTL variants, not “flip in CSS later”
- Legal and procurement get a short a11y statement they can attach to RFPs
iFynx builds bilingual accessibility as product quality: WCAG without theatre, and without treating Arabic as an afterthought pass. If your audit only runs on the English build, you do not have an accessible MENA product.
Testing with assistive technology in two locales
Run VoiceOver and TalkBack passes on the critical path in Arabic and English. Check that language announcements match the visible locale. Validate that date, currency, and phone fields are announced usefully — not as digit soup.
- Include at least one keyboard-only reviewer per release train
- Retest after RTL CSS changes even if “visual QA passed”
- Log issues with locale, AT, and OS version
- Prefer fixing semantics over ARIA sprawl
Design system commitments
If the component library cannot express accessible bilingual patterns, designers will invent one-offs that fail audits. Invest in documented RTL variants, focus states, and form field recipes. Make the accessible path the easiest path in Storybook.
- Tokenize focus rings and error colors with contrast notes
- Provide form field templates with hint and error slots
- Document do/don’t for icon mirroring
- Add a11y acceptance to pull request templates
Procurement and compliance conversations
Enterprise buyers in the Gulf increasingly ask for WCAG statements. A short, honest statement beats a marketing claim. List known gaps with remediation dates. iFynx helps clients invent neither theatre nor panic — just a backlog with owners.
Accessibility work compounds: every reusable fix lowers the cost of the next bilingual screen. Treat it as platform investment, not a pre-launch tax.
Common WCAG misses on bilingual MENA sites
We repeatedly find: low-contrast placeholders on Arabic forms, language switchers without accessible names, carousels that autoplay without pause controls, PDF policies linked only in English, and focus lost after closing a modal when dir flips. Each is cheap to fix early and expensive after a procurement questionnaire.
- Add pause/stop to any motion above subtle transitions
- Ensure select menus and date pickers work with keyboard in RTL
- Provide text alternatives for icon-only navigation
- Test zoom to 200% on article and checkout templates
Ship accessibility notes in release changelogs so clients see progress. Silence makes stakeholders assume nothing happened.
Related reading
- iFynx articles hub
- Building accessible products
- Multilingual product design
- Mobile-first for MENA markets
WCAG 2.2: what changed and why it matters for bilingual products
WCAG 2.2 became a W3C Recommendation on 5 October 2023 and added nine success criteria. Several of them affect bilingual and mobile-first products directly:
- 2.4.11 Focus Not Obscured (Minimum), Level AA: when a component receives keyboard focus, it must not be entirely hidden by author-created content such as sticky headers, cookie banners or chat widgets. Mirrored layouts move these elements, so check both directions.
- 2.5.7 Dragging Movements, Level AA: any action that uses dragging, such as sliders or reordering lists, needs a simple pointer alternative.
- 2.5.8 Target Size (Minimum), Level AA: pointer targets should be at least 24 by 24 CSS pixels, with defined exceptions such as sufficient spacing or inline links.
- 3.2.6 Consistent Help, Level A: help mechanisms, such as contact details or a chat link, should appear in the same relative place across pages.
- 3.3.7 Redundant Entry, Level A: information users already entered in a process should be filled in or selectable rather than requested again.
- 3.3.8 Accessible Authentication (Minimum), Level AA: login should not depend on a cognitive function test, like solving puzzles or transcribing characters, unless an alternative or assistance is provided.
WCAG 2.2 also removed the old 4.1.1 Parsing criterion as obsolete.
“Same relative place” in a mirrored layout
Consistent Help raises an interesting bilingual question. If help sits at the top right in English, it will usually sit at the top left in Arabic. That is consistent within each language, which is what users experience. The important thing is that, within a language, help does not jump around between pages.
Accessible authentication in the Gulf
Many regional apps use one-time passwords, national digital identity and sometimes image CAPTCHAs. OTP fields should allow paste and autofill, and avoid short time limits without a way to request more time. Image or text CAPTCHAs that require transcription are a common barrier; prefer alternatives that do not rely on cognitive tests. Biometric login and passkeys can improve accessibility when offered alongside other options.
Screen readers and language switching
Pages must declare their language correctly with the lang attribute, and mixed-language content should mark the parts in the other language, so screen readers switch pronunciation. Set dir="rtl" on Arabic content rather than relying on CSS alone. Test with the screen readers your users actually use on iOS, Android and desktop, in both languages.
Building accessibility into delivery
- Add WCAG 2.2 AA criteria to the definition of done for every feature.
- Include accessibility checks in design reviews, not only in QA.
- Run automated checks in CI, knowing they catch only part of the issues.
- Schedule manual testing with keyboard and screen readers each release.
- Track accessibility bugs with the same priority rules as other defects.
Common mistakes
- Testing only in English and assuming Arabic behaves the same.
- Sticky headers or chat widgets that hide focused elements.
- Icon-only buttons with no accessible name in either language.
- OTP fields that block paste.
- Small tap targets in dense mobile menus.
Quick checklist
- WCAG 2.2 AA in the definition of done.
- Both directions tested for focus visibility.
- Targets of at least 24 by 24 CSS pixels or adequate spacing.
- Correct lang and dir attributes.
- Screen reader tests in Arabic and English each release.
If any item is missing, it is usually the best place to start improving, because each one removes a common source of failure for users and for the team.
Accessibility done this way becomes part of normal quality work rather than a separate audit at the end.
How iFynx can help
iFynx is a product and engineering team based in Gaza, Palestine that works with clients across the Gulf. We help companies in Saudi Arabia and the UAE research, design, build and test digital products, with Arabic and English treated as equals from day one and a focus on outcomes that can be measured. If you are planning a similar product, we are happy to discuss scope, risks and a realistic first release.
Frequently asked questions
What is new in WCAG 2.2?
Nine success criteria covering focus visibility, dragging alternatives, target size, consistent help, redundant entry and accessible authentication.
What is the minimum target size in WCAG 2.2?
Success criterion 2.5.8 sets 24 by 24 CSS pixels at Level AA, with exceptions such as adequate spacing.
How do screen readers handle Arabic and English on one page?
Correct lang attributes on the page and on mixed-language passages let screen readers switch pronunciation.
Are OTP logins accessible?
They can be, if fields support paste and autofill and users can get more time.
Related: Building accessible products · Multilingual product design. Planning a product in the Gulf? See app development in Saudi Arabia and app development in the UAE.
New to the topic? Start with what is a design system.
