Accessibility Compliance Statement - Whoz
Biznet is committed to making its websites accessible. This accessibility statement applies to the Whoz applications.
The Whoz application is non-compliant with the General Reference Framework for Improving Accessibility (RGAA), version 4.1, and with the European standard EN 301 549 v.3.2.1, the reference standard in force in France and Europe. This statement is based on a self-assessment and lists the non-conformities identified to date. It does not result from a comprehensive audit.
This statement was established on 04/20/2026.
Feedback and Contact
It is important to recall that under Article 11 of the February 2005 law:
"Disabled persons have the right to compensation for the consequences of their disability, regardless of the origin and nature of their impairment, their age, or their lifestyle."
Biznet undertakes to take the necessary steps to provide access, within a reasonable time, to the information and features sought by disabled persons, whether or not the content is subject to an exemption.
Biznet invites anyone experiencing difficulties to contact them at accessibility@whoz.com so that assistance can be provided (accessible alternative, information and content provided in another format).
Means of Recourse
If you notice an accessibility issue preventing you from accessing content or a feature on the site, and after reporting it to us you do not receive a response, you are entitled to submit your complaint or a request for referral to the Défenseur des droits (French Rights Defender).
Several options are available to you:
- Contact form
- Phone: (+33) 9 69 39 00 00
- Postal address (free postage, no stamp required):
Le Défenseur des droits — Libre réponse 71120 — 75342 Paris CEDEX 07
Non-Conformities Identified
The following non-conformities were identified during the internal evaluation of the application:
| Criterion | Description |
|---|---|
| [1.1] | At least one informative image lacks a text alternative. |
| [1.2] | At least one decorative image is not ignored by assistive technologies. |
| [1.6] | At least one complex image lacks a detailed description. |
| [3.1] | At least one piece of information is conveyed by color alone. |
| [3.2] | At least one text element has insufficient contrast. |
| [3.3] | At least one informative interface component or graphic element has insufficient contrast. |
| [4.8] | At least one non-time-based media element lacks an alternative. |
| [5.4] | The title of at least one data table is not properly associated with the table. |
| [5.5] | The title of at least one data table is not relevant. |
| [5.6] | The headers of at least one data table are not properly declared. |
| [7.1] | At least one JavaScript feature is not compatible with assistive technologies or makes inappropriate use of ARIA properties. |
| [7.2] | An alternative to at least one JavaScript feature is not relevant. |
| [7.3] | At least one JavaScript feature is not controllable via keyboard or another pointing device. |
| [7.5] | At least one status message is not conveyed to assistive technologies. |
| [8.6] | At least one page title is not relevant. |
| [8.7] | At least one language change is not identified. |
| [8.9] | At least one tag is used for presentation purposes. |
| [9.1] | The heading hierarchy of at least one page is not relevant. |
| [9.2] | The document structure of at least one page is not consistent. |
| [9.3] | At least one list is not properly structured. |
| [10.4] | At least one piece of content shows loss of information and readability when text is enlarged to 200%. |
| [10.6] | At least one link within body text is not sufficiently visible. |
| [10.7] | At least one visual focus indicator is not visible or sufficiently contrasted. |
| [10.8] | At least one informative content item is ignored by assistive technologies. |
| [10.9] | At least one piece of information is conveyed solely by shape, size, or position. |
| [10.10] | The alternative for information conveyed solely by shape, size, or position is not relevant. |
| [10.11] | At least one piece of content cannot be displayed without horizontal scrolling and/or shows information loss when text is enlarged to 400%. |
| [10.12] | At least one piece of content shows loss of information and readability when spacing properties are applied. |
| [10.13] | At least one additional content item that appears on hover or focus cannot be hovered over and/or dismissed with the Escape key and/or disappears after a period of time. |
| [10.14] | At least one additional content item appearing via CSS styles only cannot be made visible via keyboard or another pointing device. |
| [11.1] | At least one form field lacks a label. |
| [11.5] | At least one set of fields of the same type is not grouped. |
| [11.9] | The label of at least one form button is not relevant. |
| [11.10] | The input control of at least one field is not relevant (lack of identification of required fields and/or lack of indication of expected data formats). |
| [11.11] | At least one error message does not provide suggestions to help correct input errors, or provides irrelevant suggestions. |
| [11.12] | At least one form does not allow the user to confirm, review, edit, or cancel the submission of data. |
| [11.13] | At least one form field does not support autofill. |
| [12.6] | At least one grouping area cannot be reached. |
| [12.7] | At least one page lacks a skip link to content, or at least one skip link is not functional. |
| [12.8] | The tab order for at least one page or component is not consistent. |
| [12.9] | At least one keyboard trap prevents the user from fully navigating a page. |
| [12.11] | At least one additional content item appearing on hover, focus, or activation of a component is not reachable via keyboard. |
| [13.3] | At least one office document (doc, odt, or PDF) is not accessible and has no alternative. |
| [13.10] | At least one feature usable via a complex gesture lacks an alternative using a simple gesture. |
Keyboard Shortcuts and Accessibility Instructions
This section documents the keyboard accessibility features available in the Whoz application, in accordance with RAWeb 1.1 criteria [14.1], [14.3], and [16.1].
Global Keyboard Shortcuts
| Keys | Description | Category |
|---|---|---|
| Ctrl + Shift + H | Go to home | Navigation |
| Ctrl + Shift + K | Open global search | Navigation |
| Ctrl + Shift + A | Create a new object | Actions |
These shortcuts can be customized from User Preferences > Keyboard Shortcuts.
Accessibility Shortcuts (WAI-ARIA Patterns)
| Keys | Description | Category |
|---|---|---|
| Enter / Space | Activate an element (button, link) | Accessibility |
| ↑ ↓ ← → Home End | Navigate within tables | Accessibility |
| Enter / Space / Escape | Interact with the content of a table cell | Accessibility |
| ↑ ↓ Home End | Navigate within menus | Accessibility |
These shortcuts comply with WAI-ARIA specifications and cannot be modified.
Navigation in Interactive Grids
| Context | Instruction |
|---|---|
| General instructions | Interactive grid. Use the arrow keys to navigate between cells. Press Enter or Space to interact with a cell's content. Press Escape to return to cell navigation. Press Tab to exit the grid. |
| Entering interaction mode | Interaction mode. Press Escape to return to navigation. |
| Exiting interaction mode | Navigation mode. Use the arrow keys to navigate between cells. |
Reorderable Lists (Keyboard Drag & Drop)
| Context | Instruction |
|---|---|
| General instructions | Use ↑ or ↓ to navigate between items. Use Alt + ↑ or Alt + ↓ to move an item up or down in the list. Press Tab to navigate between controls. |
| Drag handle | Drag to reorder item {position} of {total}. Use the arrow keys to navigate, Alt + arrow keys to move. |
Known Accessibility Limitations and Assistive Technology Compatibility
The following components have known accessibility limitations that may affect users relying on assistive technologies (screen readers, keyboard-only navigation):
| Component | Limitation | Alternative available |
|---|---|---|
| Main navigation menu | Partial keyboard support — level 3 sub-menus not reachable via keyboard | Use direct page links in the search bar (Ctrl+Shift+K) |
| Availability timeline (Staffing Pipeline) | Not rendered by screen readers; tooltip not reachable via keyboard | Access talent availability via the talent profile staffing tab |
| Kanban view (Staffing Pipeline) | Drag-and-drop not operable via keyboard | Switch to List view for full keyboard navigation |
| Skills graph (Casting Engine) | SVG chart has no text alternative | Skill details available in text form in the skill detail panel |
| Astra chat window | Not implemented as a modal dialog | Fully functional via keyboard; use Escape to close |
| CV export (PDF and Word formats) | Documents are not tagged for accessibility | No accessible alternative currently available — remediation planned for 2027 |
Support Service and Accessibility Information
Our support service (accessible via the Support chat within the Whoz platform) can provide information about:
- Available accessibility features described in this documentation
- Known limitations and available alternatives for specific components
- Guidance on using keyboard shortcuts and navigation patterns
To reach our support team, use the in-app support chat or contact us at accessibility@whoz.com.
Note: The accessibility of the support service documentation is evaluated as part of our ongoing remediation roadmap.
Comments
0 comments
Article is closed for comments.