Numberly - 1000Mercis undertakes to make its websites and software packages accessible (and its mobile applications and digital street furniture) in accordance with Article 47 of Law No. 2005-102 of February 11, 2005.
This accessibility declaration applies to La Numberly Martech Platform.
Status of compliance
The Numberly Martech Plateform is partially compliant with the referentiel général d'amélioration de l'accessibilité (RGAA).
The audit was carried out on the Accessly, Sendingly(hors journey), Dashboardly & interfaces window.
The interfaces were chosen because they represent the most widely used platforms of the Numberly Martech Platform.
Test results
The compliance audit conducted by Numberly - 1000Mercis reveals that 52% of RGAA version 4 criteria are met.
Objectives for improving accessibility
As part of our continuous improvement approach, we would like to remind you of our strategic objectives in terms of digital accessibility:
- Improvements will be made via a multi-year workspace-by-workspace scheme to achieve 100% accessibility.
These objectives are part of our commitment to comply with the requirements of the RGAA and to promote optimal accessibility on all our digital platforms.
Non-accessible content
Non-conformities
1. Images
- 1.2 Some decorative images are not correctly ignored by assistive technologies.
- 1.3 Some text alternatives to information-carrying images are not relevant.
2. Frames
- 2.1 Some frames have no title.
3. Colors
- 3.1 In some web pages, information is given only by color.
- 3.2 The contrast between text color and its background is insufficient in some web pages.
- 3.3 The colors used in certain interface components or graphic elements carrying information are not sufficiently contrasting.
5. Tables
- 5.1 Some complex data tables lack summaries.
- 5.2 Some complex data table summaries are irrelevant.
- 5.4 Some data table titles are not correctly associated with their table.
- 5.7 The appropriate technique for associating each cell with its headers is not always used in data tables.
6. Links
- 6.2 Some links do not have a heading.
7. Scripts
- 7.1 Some scripts are not compatible with assistive technologies.
- 7.2 Some script alternatives are irrelevant.
- 7.3 Some scripts are not controllable by keyboard and any pointing device.
- 7.4 Some scripts initiating a context switch do not warn the user or offer control.
- 7.5 Some status messages are not correctly rendered by assistive technologies.
9. Information structuring
- 9.1 On some web pages, information is not structured appropriately with headings.
10. Presentation of information
- 10.1 Some web pages don't control the presentation of information via style sheets.
- 10.2 Some visible content carrying information disappears when style sheets are disabled.
- 10.3 In some web pages, information becomes incomprehensible when style sheets are disabled.
- 10.5 CSS declarations of element background and font colors are not always used correctly.
- 10.7 Some elements receiving focus do not make the focus capture visible.
- 10.9 In some web pages, information is given only by shape, size or position.
- 10.11 Some content cannot be presented without loss of information or functionality and requires vertical scrolling for a 256 px high window or horizontal scrolling for a 320 px wide window.
- 10.13 Certain additional content appearing when the focus is taken or when an interface component is hovered over is not controllable by the user.
- 10.14 Some additional content generated solely by CSS styles is not accessible from the keyboard or any pointing device.
11. Forms
- 11.1 Some form fields do not have a label.
- 11.6 Some groupings of fields of the same nature in forms do not have a legend.
- 11.10 Input control is not always used appropriately.
- 11.11 Some input controls are not accompanied by suggestions facilitating the correction of input errors.
12. Navigation
- 12.1 Some page sets do not have at least two different navigation systems.
- 12.5 In some page sets, the search engine is not identically reachable.
- 12.7 Some avoidance or quick access links to the main content area are missing.
- 12.8 Tab order is not always consistent.
- 12.9 Some web pages contain keyboard traps.
- 12.11 Some additional content appearing when hovering, focusing or activating an interface component is not accessible from the keyboard when required.
Establishing this accessibility declaration
This declaration was established on October 30, 2024. It was updated on January 22, 2025.
Technologies used to carry out the audit
- HTML
- CSS
- Javascript
- Vue.JS
Test environment
Content rendering checks were carried out on the basis of the combination provided by the RGAA reference base, with the following versions:
- On Windows computers with Chrome and VoiceOver
Tools for assessing accessibility
- Web Developer Toolbar
- RGAA Assistant
- Colour Contrast Analyser
- AxeDevTool
Pages of the site that have been checked for compliance
- Switch
-
Accessly
- Profile
- General
- User
- Groups
- Roles
-
Sendingly
- Home
- Campaign listing
- Campaigns
- Campaign creation
- Changing the target of a campaign
- Changing a campaign's header
- Editing the content of a campaign
- Campaign preview
- Scheduling a campaign
- Parameters
- Journeys
- Listing of journeys
- Home
-
Dashboardly
- Home
- Emails
- SMS
- Push notification
- Web page
- QRCodes
- Report
- Parameters
Feedback and contact
If you are unable to access any content or service, you can contact the Numberly manager for assistance.
- Send a message https://numberly.com/fr/contact/
Recourse
If you notice a lack of accessibility that prevents you from accessing a content or functionality of the site, you report it to us and you are unable to obtain a response from us, you are entitled to send your grievances or a request for seizure to the Rights Defender.
Several means are available to you:
- Write a message to the Défenseur des droits
- Contact the Rights Defender delegate in your region
- Send a letter by post (free, do not put a stamp) to:
Défenseur des droits
Libre réponse 71120
75342 Paris CEDEX 07