An accessible website or app is one part of an inclusive organisation. Contracts, recruitment materials, employee policies and internal forms also shape whether people can access information and complete essential tasks.
Planning across these experiences helps teams connect digital accessibility with workplace inclusion. It starts with defining a scope that reflects the people, content and systems involved.
Include the employee journey
A product team may begin with the website or app it owns. That creates a useful starting point, while other parts of a person’s experience may sit with different teams.
Recruitment materials, employee handbooks, leave policies and internal forms need their own place in the assessment scope. Review their formats, publishing processes and ownership alongside the digital systems through which they are shared.
This broader view helps organisations support people of determination as customers, applicants and employees.
A connected assessment scope
Our ongoing engagement with Zain Kuwait, announced on Global Accessibility Awareness Day in May 2026, brings three areas into one programme:
- Digital services — the website and the native iOS and Android applications.
- Communications — social media channels and customer-facing digital content.
- Employee policies — recruitment materials, contracts, employee handbooks and leave policies.
Including employee policies connects customer-facing accessibility with the information and processes people encounter at work. The engagement is in progress; this example describes its scope, rather than completed results.
Review workplace documents
Documents need checks suited to their format and use. In a PDF, missing tags can affect structure and navigation; scanned content may require text recognition and further remediation. Forms need clear labels, a logical sequence and keyboard operation.
Accessible document forms are possible. Review their structure and behaviour with technical checks and assistive technology, using applicable PDF/UA and WCAG requirements. W3C provides guidance on keyboard-operable PDF forms (opens in a new tab).
Involve the teams that create and maintain these files. Accessible templates, authoring guidance and review responsibilities help improvements carry through to future publications.
Cover Arabic and English
Assess both language versions of the selected experience. Arabic content needs careful review of reading order, text direction, mixed-language passages and assistive technology output; these cannot be established by checking visual layout alone.
The Zain engagement includes Arabic and English assessment. Reviewing content in the language people use helps teams identify language-specific barriers alongside issues shared by both versions.
Plan for connected journeys
When planning accessibility work, identify the tasks people need to complete and the materials they encounter along the way. Use this to agree the scope with the teams responsible.
A customer may move from an app to a message and a statement. An applicant may move from a careers page to a form and a contract. Mapping these journeys helps reveal dependencies and gaps in assessment coverage.
For an initial phase, choose priority journeys, name their owners and agree how findings will be addressed. Extend coverage as the organisation’s capacity and evidence develop.
Our accessibility audits, document accessibility and policy review services support these connected experiences, with Arabic A11y expertise across both languages.
Build sustainable accessibility
Tell us about your services, your priorities and the people who use them. We will help you define the right support, agree a clear scope and plan your next steps.
Get in touch