Accessibility Statement

1. Our commitment

A platform that mediates access to employment must be usable by the people it claims to serve. An inaccessible interface does not merely inconvenience a user; on a platform like this one, it excludes them from opportunity. We therefore treat accessibility as a condition of the service working, not as an enhancement to it.

2. Standard we are working to

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, which is the level required by the Digital Government Authority's Guideline for Web Accessibility of Government Websites. We track WCAG 2.2 as our forward target as DGA guidance moves toward it.

3. What we implement

• Keyboard access to interactive controls, with visible focus states.
• Semantic structure and labelling so that screen readers can convey meaning, not just text.
• Text and interface contrast meeting the AA contrast ratios.
• Touch and pointer targets sized for reliable activation.
• Responsive layouts that reflow without horizontal scrolling.
• Plain language, particularly around scores, gaps, and appeals, where misunderstanding carries real cost.
• User-adjustable display preferences within the platform.

4. Language

Fursah serves an Arabic-first audience. We are progressively delivering full Arabic across the platform, including right-to-left layout, and we regard an English-only screen as an accessibility defect rather than a missing translation.

5. Known limitations

We publish what is not yet done, because an accessibility statement that lists only successes is marketing:

• The platform has not yet undergone a full independent WCAG 2.1 AA audit. Our conformance claim is based on internal review and is stated as a target we are working to, not a certified result.
• Arabic coverage is partial and still being extended across all portals.
• Documents uploaded by users (transcripts, certificates, portfolios) may not themselves be accessible, as we do not control how they were produced. We can accept an accessible alternative on request.
• Some data-dense dashboard views are still being improved for screen-reader navigation.

6. Reporting a barrier

If any part of Fursah is difficult or impossible for you to use, tell us at info@fursah.org. Include the page, what you were trying to do, and the device or assistive technology you use. We aim to acknowledge within five working days.

If a barrier prevents you from completing something time-sensitive (submitting an application, responding to an employer, filing an appeal), say so, and we will provide an alternative route so that the deadline does not pass because of our defect.

7. How we handle accessibility issues

Accessibility issues are logged as product defects, not as feature requests, and are prioritised by their effect on task completion. A barrier that blocks a student from applying for a job is treated as a critical defect.