Read the RGAA 4 accessibility statement for ALLFORPACK EMBALLAGE PARIS

Accessibility statement

ALLFORPACK EMBALLAGE PARIS is committed to making its website accessible in accordance with Article 47 of French Law No. 2005-102 of 11 February 2005.

To this end, the company is implementing the following strategy and actions:


Compliance status

The website ALLFORPACK EMBALLAGE PARIS is partially compliant with the General Accessibility Improvement Framework (RGAA), version 4.1.2, due to the non-conformities listed below.

Test results

The compliance audit conducted by Agence Aksé shows that:

  • 53.13% of the RGAA 4.1.2 criteria are met (overall compliance rate)
  • The average compliance rate of the website is 62.43%


Non-accessible content

Non-conformities

  • Criterion: 1.2 - Theme: Images - Criterion title: Is each decorative image correctly ignored by assistive technologies? - Affected pages: Transverse
  • Criterion: 1.3 - Theme: Images - Criterion title: For each informative image with a text alternative, is this alternative relevant? - Affected pages: Home page 
  • Criterion: 3.1 - Theme: Colors - Criterion title: On each web page, information must not be conveyed by color alone. Is this rule respected? - Affected pages: Transverse
  • Criterion: 3.2 - Theme: Colors - Criterion title: On each web page, is the contrast between the text color and its background sufficiently high? - Affected pages: Home page, FAQ, Exhibitors, Event Calendar, News, Search Results Example
  • Criterion: 3.3 - Theme: Colors - Criterion title: On each web page, are the colors used in interface components or graphic elements conveying information sufficiently contrasted? - Affected pages: Transverse
  • Criterion: 4.1 - Theme: Multimedia - Criterion title: Does each pre-recorded time-based media have, when necessary, a text transcript or audio description? - Affected pages: Transverse
  • Criterion: 6.1 - Theme: Links - Criterion title: Is each link explicit? - Affected pages: Transverse
  • Criterion: 6.2 - Theme: Links - Criterion title: On each web page, does each link have a label? - Affected pages: Transverse
  • Criterion: 7.1 - Theme: Scripts - Criterion title: Is each script compatible with assistive technologies when necessary? - Affected pages: Transverse
  • Criterion: 7.3 - Theme: Scripts - Criterion title: Is each script controllable using a keyboard and any pointing device? - Affected pages: Home page, Event Calendar
  • Criterion: 8.7 - Theme: Mandatory elements - Criterion title: On each web page, is every change of language indicated in the source code? - Affected pages: Home page
  • Criterion: 8.9 - Theme: Mandatory elements - Criterion title: On each web page, HTML tags must not be used solely for presentation purposes. Is this rule respected? - Affected pages: Home page, Accessibility Statement
  • Criterion: 9.1 - Theme: Information structuring - Criterion title: On each web page, is information structured using appropriate headings? - Affected pages: Home page, Contacts
  • Criterion: 9.2 - Theme: Information structuring - Criterion title: On each web page, is the document structure consistent? - Affected pages: Transverse
  • Criterion: 9.3 - Theme: Information structuring - Criterion title: On each web page, is each list correctly structured? - Affected pages: Transverse
  • Criterion: 9.4 - Theme: Information structuring - Criterion title: On each web page, is each quotation correctly identified? - Affected pages: Search Results Example
  • Criterion: 10.4 - Theme: Information presentation - Criterion title: On each web page, does the text remain readable when the font size is increased to at least 200%? - Affected pages: Transverse
  • Criterion: 10.7 - Theme: Information presentation - Criterion title: On each web page, is keyboard focus visible for every element receiving focus? - Affected pages: Transverse
  • Criterion: 10.11 - Theme: Information presentation - Criterion title: On each web page, can content be displayed without vertical scrolling in a window with a height of 256 px or horizontal scrolling in a window with a width of 320 px? - Affected pages: Transverse
  • Criterion: 10.13 - Theme: Information presentation - Criterion title: On each web page, can additional content appearing when an interface component receives focus or is hovered over be controlled by the user? - Affected pages: Transverse
  • Criterion: 11.1 - Theme: Forms - Criterion title: Does each form field have a label? - Affected pages: Transverse
  • Criterion: 11.5 - Theme: Forms - Criterion title: In each form, are fields of the same type grouped together when necessary? - Affected pages: Exhibitors, Event Calendar
  • Criterion: 11.9 - Theme: Forms - Criterion title: In each form, is the label of each button relevant? - Affected pages: Search Results Example
  • Criterion: 11.10 - Theme: Forms - Criterion title: In each form, is input validation used appropriately? - Affected pages: Transverse
  • Criterion: 11.11 - Theme: Forms - Criterion title: In each form, is input validation accompanied, when necessary, by suggestions to help users correct input errors? - Affected pages: Transverse
  • Criterion: 11.13 - Theme: Forms - Criterion title: Can the purpose of an input field be identified to facilitate automatic completion using the user's data? - Affected pages: Transverse
  • Criterion: 12.6 - Theme: Navigation - Criterion title: Can content grouping areas appearing on multiple web pages (header, main navigation, main content, footer, and search engine) be reached or skipped? - Affected pages: Transverse
  • Criterion: 12.7 - Theme: Navigation - Criterion title: On each web page, is there a skip link or quick access link to the main content? - Affected pages: Transverse
  • Criterion: 12.9 - Theme: Navigation - Criterion title: On each web page, navigation must not contain keyboard traps. Is this rule respected? - Affected pages: Innovation Awards
  • Criterion: 12.11 - Theme: Navigation - Criterion title: On each web page, is additional content appearing on hover, focus, or activation of an interface component accessible via keyboard when necessary? - Affected pages: Transverse


Content under derogation

No content under derogation.

Establishment of this accessibility statement

This statement was established on October 1, 2026.

Test environment

Content rendering checks were carried out based on the combination provided by the RGAA 4.1.2 reference base, with the following versions:

  • Browser: Firefox and Chrome
  • Assistive technology: NVDA (latest version) and VoiceOver


Tools used to assess accessibility

  • Code inspector
  • Colour Contrast Analyser
  • Web Developer Toolbar
  • Contrast Finder
  • Adobe Acrobat Pro


Pages of the site that were subject to the compliance check


Feedback and contact

If you are unable to access a content or service, you may contact Comexposium to be directed to an accessible alternative or to obtain the content in another form.


Remedies

This procedure is to be used in the following case.

You have reported an accessibility defect that prevents you from accessing content or one of the portal's services to the website manager, and you have not received a satisfactory response.