Paris School of Business Commitment
Paris School of Business is committed to making its websites, mobile applications, intranet, extranet, and software accessible in accordance with Article 47 of Law No. 2005-102 of February 11, 2005.
We value inclusion and diversity and ensure that our website, psbedu.paris, is accessible to everyone, especially people with disabilities.
As part of this digital accessibility initiative, we collaborate with Accessiway.
We are firmly committed to a web for all. With a long-term and responsible vision, we aim to fully comply with regulatory requirements, including RGAA 4.1.2 and the European standard EN 301 549.
Compliance Status
The website psbedu.paris has an accessibility rate of 52.94% and is therefore partially compliant with the General Accessibility Improvement Framework (RGAA 4.1.2).
Test Results
The compliance audit carried out on 10/03/2025 by AccessiWay shows that 52.94% of the RGAA version 4.1.2 criteria are met.
Details of the results
Number of compliant criteria: 36
Number of non-compliant criteria: 32
Number of non-applicable criteria: 38
Non-accessible Content
The following content is not accessible for the reasons listed below.
Non-compliance
1.2: Is each decorative image correctly ignored by assistive technologies?
1.3: For each information-carrying image with a text alternative, is this alternative relevant (except in special cases)?
1.6: Does each information-carrying image have a detailed description when necessary?
1.8: For each text image conveying information, in the absence of a replacement mechanism, is it replaced by styled text where possible (except in special cases)?
3.2: On each web page, is the contrast between text color and background color sufficiently high (except in special cases)?
3.3: On each web page, are colors used in interface components or graphical elements conveying information sufficiently contrasted (except in special cases)?
4.1: Does each pre-recorded time-based media have, when necessary, a transcript or audio description (except in special cases)?
5.4: For each data table with a title, is the title correctly associated with the data table?
6.1: Is each link explicit (except in special cases)?
6.2: On each web page, does each link have a label?
7.1: Is each script compatible with assistive technologies when necessary?
7.3: Is each script controllable by both keyboard and pointing device (except in special cases)?
8.8: On each web page, is the language code of each language change valid and relevant?
8.9: On each web page, are tags not used solely for presentation purposes?
9.1: On each web page, is information structured using appropriate headings?
9.3: On each web page, is each list properly structured?
9.4: On each web page, is each quotation correctly indicated?
10.1: On the website, are style sheets used to control the presentation of information?
10.4: On each web page, does text remain legible when the font size is increased up to 200% (except in special cases)?
10.7: On each web page, for each element receiving focus, is the focus visible?
10.8: On each web page, are hidden contents intended to be ignored by assistive technologies?
10.11: On each web page, can content be presented without requiring both vertical scrolling in a 256px-high window and horizontal scrolling in a 320px-wide window (except in special cases)?
10.13: On each web page, are additional contents appearing on focus or hover controllable by the user (except in special cases)?
10.14: On each web page, can additional contents appearing through CSS styles only be made visible using the keyboard or any pointing device?
11.1: Does each form field have a label?
11.10: In each form, is input control used appropriately (except in special cases)?
11.11: In each form, is input control accompanied, when necessary, by suggestions to help correct input errors?
11.13: Can the purpose of an input field be inferred to facilitate autofill with user data?
12.9: On each web page, does navigation avoid keyboard traps?
12.11: On each web page, are additional contents appearing on hover, focus, or activation of an interface component accessible via keyboard when necessary?
13.8: On each web page, is every moving or flashing content controllable by the user?
Exemptions for Disproportionate Burden
No content to mention.
Content Not Subject to Accessibility Requirements
No content to mention.
Establishment of This Accessibility Statement
This statement was established on 10/03/2025.
Technologies Used for the Website
HTML5
CSS
Javascript
Test Environment
Operating Systems
Apple Mac OS X 13.4
Microsoft Windows 11
Apple iOS 16
Google Android 15
Browsers and Software
Latest versions available on the different operating systems:
Google Chrome
Windows Edge
Safari
Brave
Adobe Acrobat Reader / Preview on Mac (for PDFs only)
Accessibility Evaluation Tools
Mouse, magnifier, and on-screen keyboard emulations across systems
VoiceOver (Apple systems only)
TalkBack (Android only)
NVDA 2024 and Freedom Scientific JAWS 2022 (PC systems only)
Tanaguru webext RGAA4
RGAA Assistant
System graphic evaluation tools (colors, contrasts, subtitles, etc.)
Pages Tested for Compliance
Homepage
Contact
Legal Notice
Accessibility
Help - FAQ
About Us
News: School Life
Seminars
Grande École Program - PGE
Short Programs: Summer/Winter School
Admissions: Parcoursup
Access Map
Feedback and Contact
If you cannot access any content or service, you can contact the Paris School of Business accessibility manager at handicap@psbedu.paris ou m.todorova@psbedu.paris to be directed to an accessible alternative or obtain the content in another form.
Remedies
If you notice an accessibility issue preventing you from accessing any content or functionality and you do not receive a response after reporting it, you are entitled to contact the Defender of Rights.
You may do so through the following means:
- Send a message to the Defender of Rights
- Contact the Regional delegate of the Defender of Rights
- Send a letter (free of charge, no stamp required):
Défenseur des droits
Libre réponse 71120
75342 Paris CEDEX 07
France