PipeCraftPipeCraft
Try free
Try free
Skip to main content
Accessibility

Accessibility statement

PipeCraft Updated : 19 June 2026 RGAA 4.1

Table of contents

  • 01Commitment
  • 02Compliance status
  • 03Technologies
  • 04Measures in place
  • 05Non-conformities
  • 06Action plan
  • 07Contact & feedback
  • 08Remedy
01

Publisher commitment

The publisher of PipeCraft undertakes to make its digital service accessible to all persons, regardless of ability or technology used, in accordance with:

  • Article 47 of French Law No. 2005-102 of 11 February 2005 on equal rights and opportunities, participation and citizenship for persons with disabilities;
  • Decree No. 2019-768 of 24 July 2019 on the accessibility of online public communication services;
  • the General Accessibility Improvement Framework (RGAA) version 4.1.

This statement applies to the service accessible at https://pipecraft.cloud/.

02

Compliance status

Evaluation in progress

PipeCraft is subject to an ongoing compliance assessment under RGAA 4.1. An external audit is planned; the detailed compliance rate will be published upon completion. In the absence of a full audit, formal "partial compliance" cannot yet be established.

Evaluation information
Reference frameworkRGAA version 4.1
Scope evaluatedPublic pages (home, login, registration, legal pages) and authenticated application interface (pipeline canvas, ETL)
MethodInternal self-assessment β€” June 2026
03

Rendering technologies

Technologies used to render content are:

  • Semantic HTML5
  • CSS3 (variables, media queries, prefers-reduced-motion, prefers-color-scheme)
  • JavaScript (focus management, dynamic ARIA states)
  • ARIA attributes (roles, properties and states) for interactive components
  • SVG (decorative or informative as appropriate)

The assessment was conducted with the following tools and browsers (stable versions β€” June 2026):

  • Chrome, Firefox, Safari β€” current stable versions
  • Keyboard-only navigation (Tab, arrow keys, Enter, Escape)
  • Browser zoom up to 200 %
  • Screen readers: NVDA 2024.x + Firefox (Windows), VoiceOver + Safari (macOS/iOS)
04

Accessibility measures in place

πŸ—οΈ
Semantic structure β€” hierarchical headings (H1β†’H2β†’H3), ARIA landmarks (header, main, nav, footer), skip link to main content.
⌨️
Keyboard navigation β€” interactive elements on audited public pages are keyboard accessible in logical order; focus indicators are visible. Certain application components (canvas, drag-and-drop) have non-conformities listed in section 05.
🎨
Contrast β€” main contrasts on public pages have been verified and meet applicable RGAA contrast requirements. Dynamic components, disabled states and graphics are under ongoing review.
πŸ–ΌοΈ
Images and SVG β€” decorative SVGs carry the aria-hidden="true" attribute; informative SVGs have a title or ARIA label.
πŸƒ
Reduced motion β€” CSS transitions respect the prefers-reduced-motion: reduce media query.
πŸ“±
Responsive and zoom β€” the interface is usable up to 200 % zoom without loss of information or horizontal scroll; the design is adaptive (tablet, mobile).
πŸ“‹
Accessible forms β€” each field is associated with a visible label or aria-label; error messages are explicit and associated with the corresponding field.
πŸ”€
Declared language β€” the lang attribute is set on the html element of each page.
05

Identified non-conformities

The following elements have non-conformities under correction:

  • Complex data visualisations (canvas, interactive charts in the ETL interface) β€” text alternatives or associated tables not yet systematic. Fix planned for 2027.
  • Drag-and-drop components (pipeline canvas) β€” keyboard-accessible interactions partially implemented; a sequential navigation alternative is planned. Fix planned for Q4 2026.
  • Exported PDFs β€” generated PDF files are not yet structured for screen reader accessibility. Non-conformity under correction, planned for 2027.
  • Dynamic status messages β€” some alerts are not yet announced via aria-live. Fix planned for Q3 2026.
ℹ️

If you encounter a difficulty not listed here, please report it to us (see section 7). We will prioritise your request.

06

Action plan

The publisher is committed to continuous accessibility improvement according to the following priorities:

🎯
Short term (Q3 2026) β€” fix missing aria-live messages; exhaustive keyboard audit of multi-step forms.
πŸ”§
Medium term (Q4 2026) β€” keyboard accessibility of the pipeline canvas (alternative sequential navigation); full external RGAA audit and publication of compliance rate.
πŸ“„
Long term (2027) β€” structured exported PDFs (tagged PDF); text alternatives for all complex data visualisations.
07

Contact and feedback

If you encounter an accessibility barrier preventing access to content or a feature, contact us:

Accessibility contact

accessibilite@pipecraft.cloud Β· Acknowledgement within 5 business days

Please include in your message: the URL of the page concerned, a description of the problem and, if possible, the browser and assistive technology used. We undertake to acknowledge receipt within 5 business days, and to provide a corrective or alternative solution depending on the complexity of the issue.

08

Remedy

If you have reported an accessibility issue and have not received a satisfactory response after reporting, you may lodge a complaint with the Defender of Rights:

🌐
Online β€” form available at defenseurdesdroits.fr
πŸ“ž
By phone β€” 09 69 39 00 00 (non-premium rate call, Monday to Friday 8am to 8pm)
βœ‰οΈ
By post (free, no stamp required) β€” Defender of Rights, Libre rΓ©ponse 71120, 75342 Paris CEDEX 07
πŸ›οΈ
Regional delegates β€” list available at defenseurdesdroits.fr

← Back to home

PipeCraftPipeCraft

Data quality & ETL pipelines, no code required.

Product

  • Features
  • Contact

Account

  • Sign in
  • Create account

Legal

  • Legal notice
  • Terms of use
  • Accessibility

Β© 2026 PipeCraft. All rights reserved.