Accessibility
Accessibility: what we have measured on this site.
We do not claim any level of conformance with the RGAA, the French accessibility standard: no full audit has been carried out. This page sets out what we check, with which tools, what we found and how to tell us what is blocking you.
A statement based on measurements, not on a promise
The RGAA (référentiel général d'amélioration de l'accessibilité, the general accessibility improvement framework) is the French method for checking that a website meets the international accessibility rules (WCAG). It has 106 criteria, many of which are checked by hand, page by page. We have not carried out this full audit on this site, so we cannot write “compliant”, “partially compliant” or give a percentage.
Sanfytech is not subject to the legal obligation to publish a statement: the turnover threshold is far above ours, and this site sells nothing online. We publish this page because we build websites for town halls and associations, to whom the obligation does apply, and it would be odd to ask of them what we do not do ourselves.
Checked by a script, in both themes
A suite of automated tests runs on sixteen reference pages (home, services, case studies, pricing, the blog and two articles, about, frequently asked questions, contact, a project page, three legal pages, hosting, managed services), at 1440 and 390 px wide, in light theme and dark theme.
The tests check:
- a single top-level heading per page, and no skipped heading levels;
- a skip link as the first element, visible from the keyboard, leading to the main content, and an identified main content area;
- text contrast, links in text, permitted ARIA attributes and page regions, with axe-core, in both themes;
- on all these pages, clickable targets of at least 24 px;
- the collapsed menu opens and closes from the keyboard, without JavaScript;
- no horizontal scrolling at the phone widths tested, 360 and 390 px;
- when the device asks for less motion, nothing is animated in a loop, and without JavaScript all content remains visible;
- a clickable phone number that can be reached without scrolling on a phone.
Measured pixel by pixel on the new version
The blue background of the first screen and of the banners is an image: automated tools cannot calculate contrast on a photo. So we measured it pixel by pixel, under each line of text, keeping the worst pixel.
| Criterion | Result | Method | Date |
|---|---|---|---|
| Contrast of text on the blue background | 5.68:1 at minimum, against a threshold of 4.5:1 | Worst pixel under each line of text in the banner, on five templates (home, services, case studies, project page, contact), from 360 to 1440 px, in both themes | |
| axe-core violations | 0 out of 64 runs | Sixteen reference pages, at 1440 and 390 px, in both themes | |
| Clickable targets under 24 px | None | Box of every visible link, button and field, at 390 and 1440 px, sixteen pages, two themes; a link inside a sentence is excluded, as the rule allows | |
| Text under 12 px | None | Computed size of every visible text node, at 390 and 1440 px, sixteen pages, two themes | |
| Horizontal scrolling at 360 px | None | Scroll width of the document, on the sixteen reference pages, in both themes | |
| Reduced motion | Nothing appears on scroll; transitions are switched off when the system asks for it | Reading the CSS, then checking in the browser with reduced motion requested | |
| Two themes | Same content, same structure, contrast checked in each | axe-core and the measurements above, run in each theme |
No figure is published here without its date and method. When a value gets worse, we say so and we fix it.
The checks we have not done
- No full RGAA audit of the 106 criteria.
- No testing with people who browse with a screen reader or the keyboard alone.
- No article-by-article check of the 56 blog articles: only two reference articles are in the tests.
- The home page animations (the background, the rotating word, the frame around the quote button) have no pause button: they stop when the device asks for less motion.
- The legal documents are generated from an external corpus; their long tables are readable, but they have not been reviewed criterion by criterion.
The content that may cause problems, and what we have planned
- The screenshots of our case studies contain text in the image. Each screenshot has a caption that says what it shows and an alternative text.
- The diagram of the operations chain, on the home page and the hosting page, is written as a text list, read as is by a screen reader.
- The contact form is protected against bots by a calculation run by your browser: no image to decipher, nothing to tick.
- Code samples on the blog scroll horizontally inside their frame, never the whole page.
- The site comes in a light theme and a dark theme; the toggle button is in the header, or in the menu on a phone.
Tell us what is blocking you, and we will fix it
If you cannot access some content or use a feature, write to contact@sanfytech.com or call +33 7 59 96 14 99, Monday to Friday from 9 am to 6 pm. Tell us the page, what you were trying to do and, if you know, your browser and your assistive technology. One of us will reply, and tell you when the fix is live.
This page is dated and updated with each measurement campaign. Latest measurement: .
What next
An accessible website for your municipality or association?
Tell us what you need: we will tell you what is feasible, with a timeline and a rough price, and how the accessibility statement will be written.
Reply within 24 working hours, from one of the two founders. Or by phone: +33 7 59 96 14 99.