Tsallake zuwa babban abun ciki
Parousia Group

Shari’a

Sanarwar samun dama

Accessibility statement

What this site meets, how that was established, what is not yet compliant, and who to write to.

Harsunan da ke da ƙarfin dokaWannan takarda tana da ƙarfin doka a Turanci da Faransanci. An gabatar da ita a nan cikin Turanci ne domin har yanzu babu sigar da aka duba a wannan harshe — fassarar na’ura ta rubutun da ke haifar da sakamako na doka za ta fi wannan sanarwar muni.

Commitment

Parousia Group builds and operates infrastructure that institutions and the public depend on. A service that a person cannot use is a service that has failed for that person, and the group treats accessibility as an engineering requirement rather than as a compliance exercise.

This statement covers www.parousiagroup.com and the regional sites operated on the same codebase: westafrica, eastafrica, europe, americas, middleeast and apac.parousiagroup.com.

Conformance level

These sites are designed to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, which is the level referenced by EN 301 549 V3.2.1 and by Directive (EU) 2016/2102. The group states partial conformance: the criteria below are met on every page audited, and the known limitations in section 6 are not.

  • Contrast (SC 1.4.3, 1.4.11) — measured on the worst-case pixel, never on an average. Text over photography is measured after the overlay is composited, pixel by pixel; the measurements are frozen as automated tests so that lightening an overlay without re-measuring fails the build.
  • Keyboard (SC 2.1.1, 2.4.7) — every interactive control is reachable and operable by keyboard, and focus is visible on all of them with a two-pixel outline offset from the control.
  • Motion (SC 2.2.2, 2.3.3) — every moving background carries a pause control, and all non-essential motion is suppressed under prefers-reduced-motion.
  • Structure (SC 1.3.1, 2.4.6) — one h1 per page, a continuous heading outline, landmarks, and a skip link to the main content.
  • Language and direction (SC 3.1.1, 3.1.2) — eleven languages, each served with its own lang and dir attributes; Arabic and Hebrew render right to left, with logical properties throughout rather than mirrored stylesheets.
  • Forms (SC 3.3.1, 3.3.3) — errors are announced, associated with their field, and focus moves to the first field in error.
  • Target size (SC 2.5.8) — interactive targets meet the 24 by 24 CSS pixel minimum introduced in WCAG 2.2.

How this was established

Every release is audited automatically before it is deployed. The audit runs axe-core against the built site in a real browser, over the WCAG 2.0 A/AA, 2.1 A/AA and 2.2 AA rule sets, on a representative page of each template. A release with a violation does not ship.

Automated testing is necessary and it is not sufficient: it detects a minority of the barriers a person actually meets. Contrast on photographic backgrounds, heading logic, the usefulness of alternative text and the order of a form are reviewed by hand, and the measurements behind them are recorded in the repository rather than asserted here.

No third-party certification is claimedThese sites have not been audited by an independent accessibility body. Where this statement says a criterion is met, it means the group has measured it and can show the measurement — not that an external auditor has signed it off. An independent audit is planned; this statement will be updated when it has been carried out, not before.

Compatibility

The sites are built to work with current versions of assistive technology on current browsers, and are developed to standard HTML semantics rather than to any one screen reader. They do not require JavaScript to read: the content of every page, including the list of open roles, is delivered by the server.

Text can be resized to 200 per cent, and reflows to a single column at a 320 CSS pixel viewport width, without loss of content or function.

Known limitations

The following are known and are stated rather than omitted.

  • Background video and film footage carry no audio track and no dialogue, and therefore no captions. Where footage carries meaning, that meaning is also written in the adjacent text; where it is decorative, it is exposed as decorative. Any future footage with speech will be captioned before publication.
  • Legal documents are authoritative in English and French. Other languages receive the interface in their own language and the document text in English, with a notice. A machine translation of a text that carries legal effect would be worse than an honest notice.
  • Some job advertisements are published in English only, for the same reason, and this is stated on the advertisement.
  • The interactive office map is a supplementary view. Every office it plots is also listed as text, with its address, on the same page — the map is never the only route to the information.

Feedback and escalation

If any part of these sites prevents you from doing what you came to do, write to the group and say what you were trying to do and what happened. You do not need to identify the criterion, and you do not need to use any particular wording.

Response timesThe group acknowledges accessibility reports within five working days and states, in that acknowledgement, what it intends to do and when. If a barrier blocks access to a service, an alternative route to that service is offered in the same reply. Where the group cannot resolve a report to your satisfaction, you may refer the matter to the accessibility enforcement body of your jurisdiction; in the European Union this is the body designated under Article 9 of Directive (EU) 2016/2102.

Tushen ƙa’ida

  • WCAG 2.2 level AA (W3C Recommendation)
  • EN 301 549 V3.2.1
  • Directive (EU) 2016/2102
  • Directive (EU) 2019/882 — European Accessibility Act
  • Section 508 of the US Rehabilitation Act (29 U.S.C. 794d)