The right to use this

Accessibility statement

Civic participation is every citizen’s right — and whoever cannot use the platform is effectively denied their role, however well the rights are written. This page says exactly where we are: what is done, and what is not finished yet.

Target conformance level

WCAG 2.1 level AA. Conformance today is partial: the items below are implemented and audited; the items under “not finished yet” are still in progress.

Implemented and audited

Colour contrast: every identity token is measured by computation, not by eye — body text at 4.5:1 or better, control borders at 3:1 or better, in both light and dark themes. Values that failed were adjusted to the nearest passing colour.
Keyboard: the whole page is operable by keyboard alone, with a visible focus ring on every element.
A skip-navigation link appears on the first Tab press on every page.
Landmarks: header, navigation, content and footer are semantically marked, and headings are hierarchical.
Form fields: every field has an associated label, and error messages are textual, not colour-only.
Colour is never the only cue: every state carries text with it (live/offline, overdue, open/archived).
Live results are announced to screen readers politely when the participant count changes — not on every tick.
Reduced motion: whoever enables “reduce motion” in their system gets no animation at all.
Touch targets are 44×44 px on touch screens.
Search works fully without JavaScript — a plain GET form.
Language and direction are declared on every page (this one: English, left-to-right).
And these items are checked automatically before every deploy: a sweep opens every public page and verifies language and direction, the skip link, page landmarks, heading order, a label on every field, alt text on every image, an accessible name on every link and button, touch targets, reduced motion, the visible focus ring, the polite live announcement, and that search works without JavaScript — one failing item stops the deploy. The sweep lives in the repository as scripts/a11y-sweep.py, so anyone doubting this page can run it against the site itself.
The Android app is checked before every release too, against Android's own guidelines: 48px tap targets, a readable name on everything tappable (an icon button with no label is announced simply as "button"), text contrast in both themes, and surviving double text scaling without breaking — with screens tested loaded with real content, not empty. The tests live in apps/mobile/test.

Not finished yet

English: the platform frame is translated today — home, issues, proposals, committees and their decisions, the archive, results pages, Watch, Impact, From the people, Verify, governance, funding, the charter pages, join, login and voting itself — along with every server message. What people themselves write — proposal texts, stories, deliberation — and the signed-in pages stay Arabic on purpose: we translate no one's voice. Search, account and notifications still have no mirror. And every English link that crosses into an Arabic page now says so, with an “عربي” tag before you click — it used to drop you there with no warning, or bounce you to the English home having lost what you asked for.
External audit: no independent audit with automated tools and real screen-reader users has been run yet. The automated sweep above is us checking ourselves: it catches what can be measured, not what is experienced — no script knows that a page is confusing to someone hearing it.
The admin panel was designed for the team and has not had the same level of auditing as the public pages.
Alt text for attachments: the uploader now writes the image's description at upload time — they know what's in it, and their words reach screen-reader users and pass moderation like the proposal text itself. The field is optional, not yet required, and images uploaded before the feature keep a generic auto description — that is what remains of this debt.

Hit a barrier?

Tell us at support@lakdoor.ps — describe the page, the barrier and the tool you use. We treat accessibility reports as defects, not suggestions, and reply within a declared deadline like every other report.

← Back to home

يحمّل المحتوى… / Loading…

Implemented and audited

Colour contrast: every identity token is measured by computation, not by eye — body text at 4.5:1 or better, control borders at 3:1 or better, in both light and dark themes. Values that failed were adjusted to the nearest passing colour.

Keyboard: the whole page is operable by keyboard alone, with a visible focus ring on every element.

A skip-navigation link appears on the first Tab press on every page.

Landmarks: header, navigation, content and footer are semantically marked, and headings are hierarchical.

Form fields: every field has an associated label, and error messages are textual, not colour-only.

Colour is never the only cue: every state carries text with it (live/offline, overdue, open/archived).

Live results are announced to screen readers politely when the participant count changes — not on every tick.

Reduced motion: whoever enables “reduce motion” in their system gets no animation at all.

Touch targets are 44×44 px on touch screens.

Search works fully without JavaScript — a plain GET form.

Language and direction are declared on every page (this one: English, left-to-right).

And these items are checked automatically before every deploy: a sweep opens every public page and verifies language and direction, the skip link, page landmarks, heading order, a label on every field, alt text on every image, an accessible name on every link and button, touch targets, reduced motion, the visible focus ring, the polite live announcement, and that search works without JavaScript — one failing item stops the deploy. The sweep lives in the repository as scripts/a11y-sweep.py, so anyone doubting this page can run it against the site itself.

The Android app is checked before every release too, against Android's own guidelines: 48px tap targets, a readable name on everything tappable (an icon button with no label is announced simply as "button"), text contrast in both themes, and surviving double text scaling without breaking — with screens tested loaded with real content, not empty. The tests live in apps/mobile/test.

Not finished yet

English: the platform frame is translated today — home, issues, proposals, committees and their decisions, the archive, results pages, Watch, Impact, From the people, Verify, governance, funding, the charter pages, join, login and voting itself — along with every server message. What people themselves write — proposal texts, stories, deliberation — and the signed-in pages stay Arabic on purpose: we translate no one's voice. Search, account and notifications still have no mirror. And every English link that crosses into an Arabic page now says so, with an “عربي” tag before you click — it used to drop you there with no warning, or bounce you to the English home having lost what you asked for.

External audit: no independent audit with automated tools and real screen-reader users has been run yet. The automated sweep above is us checking ourselves: it catches what can be measured, not what is experienced — no script knows that a page is confusing to someone hearing it.

The admin panel was designed for the team and has not had the same level of auditing as the public pages.

Alt text for attachments: the uploader now writes the image's description at upload time — they know what's in it, and their words reach screen-reader users and pass moderation like the proposal text itself. The field is optional, not yet required, and images uploaded before the feature keep a generic auto description — that is what remains of this debt.