Official foundations
Standards bodies, official documentation and public authorities are used as primary reference points.
Quality tools reveal speed, accessibility and stability issues, but no score replaces a real person completing a task. Compare lab and field data when the latter is available.
Measure one page on a phone, then complete a task by keyboard and with larger text. Link findings to a specific component or piece of content before fixing them.
Browse the resourcesEach entry has a clear role and an official destination. The catalogue avoids link farms, copied descriptions and artificial rankings.
Standards bodies, official documentation and public authorities are used as primary reference points.
Established services are grouped by actual use: building, hosting, measuring, securing, publishing or promoting a website.
Inclusion is editorial and unpaid. A listing does not imply a partnership or guarantee.
| Criterion | Question to resolve |
|---|---|
| Test type | Does the result come from a laboratory test, field data or human assessment? |
| Journey | Do contact, search and navigation remain usable with a keyboard and on mobile? |
| Priority | Which problem blocks a user and which fix can be verified? |
Keep a short decision record: requirement, source, observed result and unresolved point. Test the same task with each candidate instead of comparing marketing lists of features.
Compare their role and documentation before selecting a tool. Inclusion is not a ranking.
36 resources displayed
No resource matches these filters. Try a broader search.
Google guidance on Web performance, accessibility and best practices.
Use it for : Connect performance or accessibility guidance to a measurement on your pages.
Documentation for the Chrome browser, DevTools and Web platform.
Use it for : Reproduce an issue in the browser and record the test steps.
Performance analysis based on Lighthouse and available field data.
Use it for : Separate lab diagnostics from field data when field data is available.
Automated auditing for performance, accessibility, SEO and best practices.
Use it for : Compare repeated measurements on the same page before prioritising a fix.
Detailed page-load testing from multiple devices and locations.
Use it for : Inspect loading and network waterfall for a defined scenario and location.
Speed reports, Web metrics and loading timelines.
Use it for : Read loading details rather than treating the score as a verdict.
HTML markup validation against Web rules.
Use it for : Fix HTML errors at the source, then check several templates.
Validation of CSS stylesheets.
Use it for : Inspect relevant errors without confusing a warning with a visible defect.
Browser compatibility tables for Web technologies.
Use it for : Check feature support for the browsers used by the intended audience.
Website and application testing on real browsers and devices.
Use it for : Replay an important journey on priority devices and browsers.
Automated digital accessibility testing tools.
Use it for : Pair automated findings with human review of the journey.
Visual evaluation of accessibility issues on a Web page.
Use it for : Review issues in their visual and editorial context.
Resources, training and tools dedicated to Web accessibility.
Use it for : Read an accessibility method, then apply it to a real page.
Image compression and comparison directly in the browser.
Use it for : Compare image size and appearance before selecting a format.
Online compression for common Web image formats.
Use it for : Inspect output detail and file size before replacing an image.
French evaluation of a Web page’s environmental footprint.
Use it for : Use the indicator to compare pages, then inspect technical causes.
French-language resources on digital sustainability and eco-design.
Use it for : Relate a sustainability recommendation to site measurement data.
Official patterns and examples for designing accessible interactive components with ARIA.
Use it for : Compare the keyboard behaviour of an interactive component with a documented pattern.
W3C list of accessibility evaluation tools to complement with human testing.
Use it for : Select audit aids, then manually review findings and user journeys.
Documentation for the critical path, metrics, resources and performance measurement APIs.
Use it for : Connect a slow metric to resources, rendering and interactions on the affected page.
Reference for LCP, INP, CLS and their interpretation in real user experience.
Use it for : Distinguish lab measurements from real-user data where available.
Guide to measuring and improving interaction responsiveness with INP.
Use it for : Inspect slow interactions on pages where visitors actually need to act.
Documentation for public field data used to observe real-world Chrome experience.
Use it for : Consult available field data before interpreting a single test score.
Reference for Lighthouse audits and their limits when diagnosing a page in the lab.
Use it for : Use diagnostics to locate a cause, then verify the effect on a real task.
Structured methodology for defining scope, selecting a representative sample and documenting a WCAG evaluation.
Use it for : Prepare the sample and method before concluding on accessibility across a set of pages.
Harmonized test rules for automatically or semi-automatically evaluating accessibility requirements.
Use it for : Understand what an automated rule checks and what remains outside its scope.
Documentation for recording and analyzing rendering, long tasks, interactions and bottlenecks.
Use it for : Record a slow interaction to find blocking tasks and rendering work.
Reference for DevTools features covering the accessibility tree, contrast and computed properties.
Use it for : Inspect an element’s exposed properties, then test its keyboard use.
W3C tutorial on labels, instructions, validation and messages that make forms more accessible.
Use it for : Compare a real form with examples of labels, errors and confirmations.
Official examples for clearly communicating success or errors after a form submission.
Use it for : Compare a real form’s errors and confirmations with the W3C accessibility examples.
Public digital ecodesign framework with criteria, verification methods and a declaration for documenting service design choices.
Use it for : Assess applicable criteria and retain evidence; the progress score does not measure a carbon footprint.
Reference for timed text tracks used for captions and descriptions.
Use it for : Compare the track with video, languages and necessary audio information.
Reference for font display strategies according to download and availability.
Use it for : Observe states before and after loading with a fallback font.
W3C tutorial on data tables and associations between cells and headers.
Use it for : Test a real table with headings, caption and suitable navigation.
WAI guidance for preparing accessible audio and video media.
Use it for : Plan necessary text and audio information during production.
WAI overview of accessibility evaluation methods and steps.
Use it for : Define scope and human checks before interpreting an automated score.
These examples illustrate uses, not rankings or endorsements. Verify each provider’s current documentation and terms before a decision.
Quality tools reveal speed, accessibility and stability issues, but no score replaces a real person completing a task. Compare lab and field data when the latter is available.
Questions to checkA practical use : Measure one page on a phone, then complete a task by keyboard and with larger text. Link findings to a specific component or piece of content before fixing them.
What this cannot prove : A lab score varies with its environment and cannot describe all visitors. Automated checks do not cover every accessibility barrier.
Examples : web.dev · PageSpeed Insights
Related guide : Test website accessibility through real tasks
This non-exhaustive directory was last reviewed on 30 August 2026; its links were checked on 25 September 2026. Some websites restrict automated checks. It contains external links to independent websites. Their availability, content, prices, cookies and terms may change. Française du Numérique does not control them and receives no commission for their inclusion.