Accessibility assessment

This statement applies to content published on the domain: ‘https://www.suez.com’.

It does not apply to other content or websites published on any of its subdomains. These websites and their content will have their own specific accessibility statement.

This website is managed by the SUEZ Communications Departement. It is designed to be used by as many people as possible, including persons with disabilities.

You should be able to:

• navigate most of the website using just a keyboard;
• navigate most of the website using a modern screen reader and speech recognition software (on your computer or phone);
• This website is designed to comply with the technical standard for websites and mobile apps.

This website is partially compliant with technical standard EN 301 549 v.3.2.1 and the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.
See ‘Non-accessible content’ for more details.

The website was last tested on 12 March 2025.

This statement was prepared on 14 March 2025.
The statement is based on a review of a representative sample of web pages by atalan -qualified accessibility expert, using a combination of manual and automated testing.

We welcome your feedback on the accessibility of the suez.com website. Please let us know if you encounter accessibility barriers.

Contact form: Write to us (please refrain from providing sensitive information in the form, e.g. any information that would reveal personal financial information, information related to your health, or any other sensitive topic).
We try to respond to feedback within 15 business days from the date of receipt of the enquiry by our Communications Departement team.

The suez.com website is designed to be compatible with the following most used assistive technologies:

• the latest version of Google Chrome, Microsoft Edge, Mozilla Firefox and Apple Safari browsers;
• in combination with the latest versions of NVDA, VoiceOver and TalkBack.

The accessibility of the suez.com website relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

• HTML5
• CSS3
• JavaScript
• WAI-ARIA 1.1

Despite our best efforts to ensure the accessibility of the suez.com website, we are aware of some limitations, which we are working to fix. Below is a description of known limitations and potential solutions. Please contact us if you encounter an issue not listed below.

Known limitations for the suez.com website:

1.2 Is each decorative image correctly ignored by assistive technologies?
1.3 For each image that provides information and has a text alternative, is this alternative relevant (excluding special cases)?
1.9 Where necessary, is each image caption correctly linked to the corresponding image?
3.2 On each web page, is the contrast between the colour of the text and the colour of its background sufficiently high (excluding special cases)?
3.3 In each web page, are the colours used in the interface components or graphic elements carrying information sufficiently contrasting (excluding special cases)?
4.1 If necessary, does each pre-recorded time-based medium have a text transcription or audio description (excluding special cases)?
4.3 Does each pre-recorded synchronized time-lapse medium have synchronized subtitles, if necessary (excluding special cases)?
4.4 For each pre-recorded time-synchronised medium with synchronised subtitles, are these subtitles relevant?
4.5 Does each pre-recorded time-synchronised medium have a synchronised audio description if required (excluding special cases)?
5.6 For each data table, are each column header and each row header correctly declared?
6.1 Is every link explicit (excluding special cases)?
6.2 Does every link on every web page have a title?
7.1 Is each script, where necessary, compatible with assistive technologies?
7.3 Can each script be controlled by the keyboard and by any pointing device (except in special cases)?
7.4 For each script that initiates a context switch, is the user warned or does the user have control over it?
7.5 On each web page, are status messages correctly rendered by assistive technologies?
8.6 For each web page with a page title, is the title relevant?
8.9 In each web page, tags must not be used solely for presentation purposes. Is this rule respected?
9.1 On each Web Page, is the information structured by the appropriate use of headings?
9.2 On each Web Page, is the structure of the document consistent (excluding special cases)?
9.3 Is every list on every Web page correctly structured?
10.7 On each Web page, is the focus visible for each element that receives focus?
10.9 In each web page, information should not be provided solely by its shape, size or position. Is this rule respected?
10.11 For each web page, can the content be presented without loss of information or functionality and without the need for either vertical scrolling for a window with a height of 256 px, or horizontal scrolling for a window with a width of 320 px (excluding special cases)?
11.10 Dans chaque formulaire, le contrôle de saisie est-il utilisé de manière pertinente (hors cas particuliers) ?
11.11 In each form, are input checks accompanied, where possible, by suggestions to help correct input errors?
11.13 Can the purpose of an input field be deduced to make it easier to automatically fill in fields with user data?
12.6 Can content grouping zones present in several web pages (header, main navigation, main content, footer and search engine zones) be reached or avoided?
12.7 Is there an avoidance or quick access link to the main content area on every web page (excluding special cases)?
12.8 Is the tab order consistent on every web page?
12.11 On each web page, is additional content that appears when hovering, focusing or activating an interface component accessible by keyboard, if necessary?
13.3 On every web page, is there an accessible version of every office document that can be downloaded (excluding special cases)?
13.10 On each web page, can the functions that can be used or accessed using a complex gesture also be accessed using a simple gesture (excluding special cases)?