Illustrative scenario: not a client case study
Consider a hypothetical Dubai retail brand running an accessibility scan and finding its checkout flow has multiple form fields with no visible focus indicator, making keyboard only navigation nearly impossible to complete. Fixing focus states across the checkout flow, adding proper labels to form fields, and re testing with a screen reader would address those observed interface barriers. Whether the changes affect task completion or conversion would need to be measured; the example does not establish an outcome.
This isn't a niche concern, it's a market you're currently excluding
Review real tasks against WCAG 2.2 criteria. Automated checks may help identify issues, but they do not establish that an experience works for every person. Do not claim that accessibility changes increase conversion unless you have measured evidence.
Start with the fixes that carry the most impact for the least effort
Some barriers can be addressed incrementally. Review contrast, image alternatives, keyboard operation, and form labels and errors against WCAG criteria; do not assume that these checks are low cost in every project or that a short list catches every accessibility issue.
Arabic and RTL layouts need their own accessibility check
W3C Arabic and Persian layout guidance documents directionality and mixed direction layout considerations. Test Arabic pages and mixed direction content in the actual interface as well as English pages; the reference does not establish that a particular site is accessible.
Treat it as an ongoing practice, not a one time audit
automated checks can help find some issues, but do not establish that an experience works for every person
What to take away
- Use WCAG 2.2 to review real tasks; do not treat a checklist as proof of accessibility.
- Automated checks may identify some issues but cannot establish that an experience works for every person.
- Test Arabic pages and mixed direction content in the actual interface as well as English pages.
- Check legal or sector specific obligations with a qualified adviser; measure any claimed conversion effect.
Frequently asked questions
Is accessible web design legally required in the UAE?
WCAG 2.2 is a W3C Recommendation with testable criteria. Check any legal or sector specific obligation with an appropriately qualified adviser; this checklist is not a statement of UAE legal compliance.
Can we make our site accessible without a full redesign?
Some issues may be addressable incrementally without a full redesign, depending on the site. Review affected tasks against WCAG criteria and test after changes; do not treat a short list as proof that an experience works for every person.
How do we test our site for accessibility without hiring a specialist?
Automated tools can help find some issues, but they do not establish that an experience works for every person. Test real tasks with keyboard operation and assistive technology where possible.