Official foundations
Standards bodies, official documentation and public authorities are used as primary reference points.
Standards bodies and reference frameworks help separate a technical rule from a product preference. Start with the exact problem before reading a full specification.
To decide whether a form is accessible, first describe the observed barrier: missing label, unannounced error or broken keyboard route. Find the relevant criterion, then compare it with page behaviour.
AI-generated illustration
Selection prioritises recognition within the field, professional use and reference status. Highly specialised documentation entries are consolidated under their main resource.
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 |
|---|---|
| Text version | Is the cited recommendation published, experimental or superseded? |
| Applicability | Which requirements actually concern your page, interface or audience? |
| Verification | Can a testable example reproduce the expected behaviour? |
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.
9 resources displayed
The date applies to the linked document, not to a review of every service feature.
The link restores the search and filters, including resources selected for comparison.
No resource matches these filters. Try a broader search.
Select resources from the cards below. Compare their role and practical use, then verify current terms, costs, data export and support on official websites. Geographical origin describes the publisher; it does not establish where your data will be hosted.
No resource selected.
Open Web standards including HTML, CSS, accessibility and related technologies. Find specifications and their maturity levels. Distinguish published recommendations, explanatory notes and drafts before citing a requirement.
W3C · Source consulted
Use it for : A starting point for finding the original recommendation and the group maintaining it.
Entry point for accessibility standards, tutorials and evaluation methods. Use it to connect keyboard, form or reading difficulties to explained requirements. Choose material suited to the team’s role and distinguish the checking method from the outcome on your site.
W3C WAI · Source consulted
Use it for : Connect guidance with components and team responsibilities; add human trials to automated checks.
Living standards for the Web platform, including HTML, DOM, URL and Fetch. Consult them when browser behaviour or a document rule needs an exact reference. Specifications describe the intended model; check usage and compatibility in your target browsers separately.
WHATWG · Source consulted
Use it for : Consult the living standard to confirm expected behaviour of an HTML element.
Verification path
Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.
id="demo-email" and its label uses for="demo-email". Find the association rule in the HTML Living Standard and check that the identifier is unique within the relevant tree.email type checks an address format, not whether the mailbox exists or the person controls it. A hint inside the field does not, by itself, replace a correctly associated label.Organisation and process for Internet protocol specifications. Useful for finding an RFC, its status and documents updating or replacing it. Do not treat all RFCs or drafts as equivalent standards: context and publication status are part of the reference.
IETF · Source consulted
Use it for : Find the RFC defining a protocol before interpreting a third-party summary.
Verification path
Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.
RFC 9110. Its record states Internet Standard and STD 97. An RFC number does not establish the status of other publications in the series.Updates, Obsoletes relationships and verified errata. The original text remains archived; a revision or replacement is published under a new RFC number. Read the scope of a change in the document rather than inferring it from its date.BCP 14, uppercase MUST expresses an absolute requirement of the specification. SHOULD permits justified exceptions after considering their implications; MAY marks an option. Text can also be normative without these keywords.Official documentation · RFC 9110 · HTTP Semantics
Resources on domain-name coordination and relationships with accredited registrars. Useful for distinguishing domain actors and finding applicable documents. During website handover, also identify the holder, actual supplier and renewal mechanism in your own accounts.
ICANN · Source consulted
Use it for : Separate rules for relevant domains from the terms of your own registrar.
Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.
French information about domain names: purpose, selection, registration and management. Useful for choosing a name suited to the activity and understanding the participants. Before registration or transfer, clarify the holder, authorised access and renewal responsibility; the name alone covers none of these duties.
Afnic · Source consulted
Use it for : Check the rules and procedures applicable to a .fr domain name.
Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.
.fr domain lists nameservers while its website no longer responds. Domain registration and service availability require separate checks.Vocabulary of types and properties describing entities and their relationships. Use it to match visible page content and keep identifiers consistent. A type existing in Schema.org does not mean a search engine offers an enhanced display for it.
Schema.org · Source consulted
Use it for : Choose types and properties describing visible content; vocabulary validity and rich-result eligibility differ.
Documentation and learning material for HTML, CSS, JavaScript and Web APIs. Useful for syntax, examples, specification links and compatibility information. Apply examples to your context and test errors; a reference page does not validate a complete integration.
MDN Web Docs · Source consulted
Use it for : Compare examples, compatibility and specification before adopting a Web API.
Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.
__compat.support. Check the target browser and relevant version. Information about a general API does not automatically describe every method or option within it.partial_implementation: true, read the notes property before concluding that support is complete. A function name may exist while the expected behaviour is missing. Relate version, removal and conditional-enablement information to the feature actually being used.@mdn/browser-compat-data package version or consulted revision alongside your test result. Distinguish the experimental and deprecated markers from support data. Then check the journey in your audience’s browsers: documentation prepares the test rather than replacing its outcome.Official documentation · MDN Browser Compatibility Data — Data guidelines
French public accessibility framework providing criteria, tests and a technical evaluation method. Use it to define checking scope and assess findings. Record the applied edition and relevant criteria; passing an automated tool does not establish whole-site conformance.
RGAA · Source consulted
Use it for : Useful for connecting an accessibility finding to the French assessment framework.
These examples illustrate uses, not rankings or endorsements. Verify each provider’s current documentation and terms before a decision.
Standards bodies and reference frameworks help separate a technical rule from a product preference. Start with the exact problem before reading a full specification.
Questions to checkA practical use : To decide whether a form is accessible, first describe the observed barrier: missing label, unannounced error or broken keyboard route. Find the relevant criterion, then compare it with page behaviour.
What this cannot prove : A practical explainer and a standard serve different purposes; keep a link to the normative text and the version checked.
Related guide : Publish accessible website content every day
A reading difficulty is not always solved by adding a validator. Find the applicable document, then compare its requirement with an example from your interface. These situations help you frame a technical question that can actually be tested.
Reference : W3C WAI · Forms
Before making a resource part of website operations, plan for updates and an exit too. These checks concern your trial results without assuming features or prices of a particular plan.
Record title, version and cited section. In a report, separate normative text from the practical explanation used to apply it.
Keep the page example and examined behaviour. A component change should allow repeating the check even if the explainer moves.
Can someone else find the rule and understand why it was chosen? A screenshot without a reference cannot support that transfer.
This non-exhaustive directory had its data consistency and links checked on 2 October 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.
Before choosing a resource, run a limited trial using the same data and task. Keep the outcome and its limitations rather than a ranking based on familiarity.
Choose a page with headings, navigation and a form. Compare the standard, a documented example and keyboard behaviour. Record the framework version; success on one example does not establish compliance across the entire site.
Distinguishing link destinations and content roles helps when examining a standards example.
| Reference | Value or syntax | Scope |
|---|---|---|
| W3C · HTML language | <html lang="fr"> | The default language is declared on html; local language changes are marked. |
| W3C · JSON-LD 1.1 | application/ld+json · @context | JSON-LD describes linked data; valid syntax and factual accuracy remain separate checks. |
| W3C Internationalization · HTML direction | lang="ar" dir="rtl" | Language and reading direction are separate information. Declaring ar alone does not establish the base direction; dir="rtl" does. Logical CSS properties adapt spacing without hard-coding left and right throughout the layout. |
| WCAG 2.2 · 3.3.7 | A · same process | Within one process, previously supplied information must be auto-populated or available to select, subject to the criterion’s exceptions. Browser autocomplete alone is insufficient; the site must offer the information already received or avoid requesting it again. |
| WCAG 2.2 · 3.3.8 | AA · authentication | An authentication step requiring recall or transcription needs assistance or an alternative route, subject to the criterion’s exceptions. Test password managers and code pasting; an audio alternative requiring transcription does not by itself remove the cognitive burden. |
| HTTP · If-Match | If-Match: "r7" → 412 | If-Match compares a strong validator before a write. Under the illustrated contract, a stale version receives 412; keep the draft to compare changes. |
Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.