A resident opens a government service on her phone. She uses a screen reader. Halfway through the form, a date field stops responding. She tries again, then gives up.
What happens next depends on one page most websites forget about. If she can find a clear accessibility statement, she knows this barrier is not her fault, she knows another way to finish the task, and she knows who to tell. If she cannot, the service has lost her, and the entity will probably never hear about the problem.
That page is the accessibility statement. It is short, it is public, and for UAE federal entities it is not optional.
Statement or policy? They are not the same thing
The two terms are often used as if they mean the same thing. They do not, and the difference matters.
| Accessibility statement | Accessibility policy | |
|---|---|---|
| Audience | The public: residents, citizens and visitors using your website or app. | Your own organisation: leadership, staff, suppliers and contractors. |
| Purpose | Explains your commitment, the standard you follow, what does not work yet, and how to get help. | Sets out how you will deliver accessibility: roles, training, budgets, procurement rules and timelines. |
| Where it lives | On the website or app, linked from the footer of every page. | In your internal governance documents. |
| Tone | Plain, honest and practical. | Formal and operational. |
In short, the policy is your internal plan, and the statement is your public promise. A good statement is made possible by a good policy, but people using your service only ever see the statement. The W3C Web Accessibility Initiative (WAI) treats them as separate pieces of work, with its own guidance on developing an accessibility statement and on developing an organisational policy.
Why every entity must publish one
W3C's guidance puts it simply: a statement shows people that you care about accessibility, and about them. It tells them how accessible your content is, and it demonstrates your commitment and social responsibility. For a UAE federal entity, there are four more reasons.
It is required
The National Policy for Digital Accessibility applies to every federal ministry, authority and institution, and to the suppliers that build and run their digital services. Article 12 of the policy requires each entity to publish a digital accessibility statement on its websites and mobile apps. TDRA reviews compliance every year.
It gives people a way in
No website is perfect, and a statement does not pretend otherwise. What it does is turn a dead end into a conversation. When a barrier blocks someone, the statement tells them how to report it and how to get the content or service in another way. For people of determination and senior citizens, that can be the difference between completing a task and giving up.
It builds trust through honesty
Listing what is not yet accessible can feel uncomfortable. It is also what makes a statement credible. A clear list of known limitations tells people where they might struggle before they waste their effort, and it shows that the entity has actually tested its service rather than simply claiming it is accessible.
It keeps the entity accountable
A statement names a standard, reports a level of conformance and carries the date it was last reviewed. Once those facts are public, they have to stay true. Teams re-test, fix issues and update the page. The statement quietly becomes one of the most effective tools for keeping accessibility on the agenda.
What makes a statement strong
Start with the essentials
W3C recommends that every statement contains at least three things:
- A commitment to accessibility for people with disabilities.
- The standard you apply, such as WCAG 2.2.
- Contact details for people who run into a problem.
It then suggests adding known limitations, the measures you take, technical requirements such as supported browsers, the environments you have tested in, and the laws and policies that apply. The UAE requirements build on this baseline, so treat W3C's three items as the floor, not the finish line.
Write it for people, not for lawyers
A strong accessibility statement is:
- Easy to find. Link to it from the footer of every page, and from the help menu, sitemap and about page. Use the same link name everywhere, across your website and your app.
- In plain language. Describe problems the way people experience them. "Videos do not have captions" helps a reader; a WCAG success criterion number does not. Link to your detailed evaluation report for those who want it.
- Honest. List known limitations, explain why each exists, say what you are doing about it, and tell people what they can do in the meantime.
- Useful. Give a real contact channel for reporting barriers and requesting other formats, and say how quickly you will respond.
- Current. Show the date of the last review, with the month written in full, and review it at least once a year. An old date suggests nobody is looking after it.
- Equal in both languages. The Arabic and English versions say the same thing and are equally accessible.
To get a first draft quickly, try the free W3C Accessibility Statement Generator, then adapt it to the UAE requirements and publish it in both languages. W3C's minimal example and complete example show the two ends of the range. You can also see how this website publishes its own accessibility statement, which covers each of the UAE requirements.
A promise, not a disclaimer
An accessibility statement is not legal small print. Written well, it is one of the few places where a government entity speaks directly to the people most likely to be excluded by its services, and tells them: we know you are here, this is what we have done, and this is how we will help.
It takes an afternoon to write. It takes a commitment to keep true. Both are worth it.
Start with the requirements in the accessibility guidelines, and if you want to understand the techniques behind an accessible service, read the vital role of ARIA in enhancing web accessibility.
References
- UAE Government: National Policy for Digital Accessibility
- W3C WAI: Developing an Accessibility Statement
- W3C WAI: Accessibility Statement Generator
- W3C WAI: Developing an Organizational Policy
- W3C WAI: WCAG 2 Overview
- W3C WAI: WCAG-EM Report Tool, for producing the evaluation report your statement can link to
- W3C WAI: Web Accessibility Laws & Policies