Official foundations
Standards bodies, official documentation and public authorities are used as primary reference points.
Web resources
Web standards and governance
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.
Browse the resourcesEditorial method
A directory made to be useful, not merely long.
Each entry has a clear role and an official destination. The catalogue avoids link farms, copied descriptions and artificial rankings.
Professional tools
Established services are grouped by actual use: building, hosting, measuring, securing, publishing or promoting a website.
Independent reading
Inclusion is editorial and unpaid. A listing does not imply a partnership or guarantee.
Compare on three practical questions
| 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.
Search and filter
Official starting points for this topic
Compare their role and documentation before selecting a tool. Inclusion is not a ranking.
21 resources displayed
No resource matches these filters. Try a broader search.
Open Web standards including HTML, CSS, accessibility and related technologies.
Use it for : A starting point for finding the original recommendation and the group maintaining it.
Apply it to a project
w3.orgVisit official website
Entry point for World Wide Web Consortium standards and work.
Use it for : Check the recommendation and its version before citing a Web rule.
Apply it to a project
w3.orgVisit official website
International resources and standards for making the Web accessible.
Use it for : Start from a specific usage barrier, then consult the relevant tutorials and techniques.
Apply it to a project
w3.orgVisit official website
Living standards for HTML, DOM, URL, Fetch and the Web platform.
Use it for : Consult the living standard to confirm expected behaviour of an HTML element.
Apply it to a project
whatwg.orgVisit official website
Organization developing many of the Internet’s technical standards.
Use it for : Find the RFC defining a protocol before interpreting a third-party summary.
Apply it to a project
ietf.orgVisit official website
Global coordination of domain names and the Domain Name System.
Use it for : Separate rules for relevant domains from the terms of your own registrar.
Apply it to a project
icann.orgVisit official website
Registry for .fr and a key organization in the French Internet infrastructure.
Use it for : Check the rules and procedures applicable to a .fr domain name.
Apply it to a project
afnic.frVisit official website
International organization supporting an open, global and trustworthy Internet.
Use it for : Understand the Internet governance context before choosing a local solution.
Apply it to a project
internetsociety.orgVisit official website
Standards organization notably responsible for ECMAScript.
Use it for : Check the standardised language version when JavaScript compatibility matters.
Apply it to a project
ecma-international.orgVisit official website
Shared structured-data vocabulary for search engines and Web services.
Use it for : Choose a type that truly describes the page and inspect its documented properties.
Apply it to a project
schema.orgVisit official website
Reference documentation for HTML, CSS, JavaScript and Web APIs.
Use it for : Compare examples, compatibility and specification before adopting a Web API.
Apply it to a project
developer.mozilla.orgVisit official website
French framework for assessing and improving digital accessibility.
Use it for : Useful for connecting an accessibility finding to the French assessment framework.
Apply it to a project
accessibilite.numerique.gouv.frVisit official website
French public resources on digital service design and quality.
Use it for : Study public-service design principles in the context of the service being delivered.
Apply it to a project
design.numerique.gouv.frVisit official website
Global technical registries for names, numbers and protocol parameters.
Use it for : Confirm a registered value, such as a media type, in the relevant registry.
Apply it to a project
iana.orgVisit official website
Official introduction to the Schema.org vocabulary, types, properties and markup formats.
Use it for : Choose a type that genuinely describes the page content, then validate its output.
Apply it to a project
schema.orgVisit official website
W3C reference recommendation for making Web content perceivable, operable, understandable and robust.
Use it for : Consult criteria relevant to an observed issue and follow up with human testing.
Apply it to a project
w3.orgVisit official website
W3C guidance for designing, developing and operating digital products that are more sustainable for the planet, people and society.
Use it for : Use the guidance for measurable reduction ideas without claiming an uncalculated impact.
Apply it to a project
w3.orgVisit official website
W3C resources for designing pages across different languages, writing systems and cultures.
Use it for : Check declared language, text direction and movement between versions on a real page.
Apply it to a project
w3.orgVisit official website
Official French reference for administrative codes and names of regions, departments and communes as of 1 January 2026.
Use it for : Check a commune code or name in the relevant release before publishing a local page.
Apply it to a project
insee.frVisit official website
Filterable reference for WCAG criteria and associated techniques.
Use it for : Find the relevant criterion and applicable version for a specific barrier.
Apply it to a project
w3.orgVisit official website
Public guidance for documenting dataset provenance, structure, context and limitations.
Use it for : Separate publication, extraction and measurement dates in metadata.
Apply it to a project
guides.data.gouv.frVisit official website
Choose a starting point
What each category helps you decide.
These examples illustrate uses, not rankings or endorsements. Verify each provider’s current documentation and terms before a decision.
Web standards and governance
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 check- Identify whether the document is a standard, a recommendation or an explanation.
- Record its version and the context in which it applies.
A 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
Transparency
Suggest a resource or correction
Editorial scope and third-party websites
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.
Directory questions
Selection, independence and updates.
The editorial selection prioritises primary and official sources, established standards bodies, widely used professional tools, specialised media and active communities that are directly relevant to creating, operating, securing or promoting websites. An entry should have a clear purpose, an identifiable publisher and an official destination. The catalogue is independent, non-exhaustive and does not attempt to rank every available provider. Inclusion may be reconsidered when a resource closes, changes purpose, becomes misleading or no longer offers enough practical value. Review dates indicate when the catalogue was last checked as a whole, not a guarantee that every external page remains unchanged afterwards. Visitors should therefore confirm current pricing, terms, security and suitability on the third-party website before relying on a service.
No. A directory entry is a practical reference, not a certification, partnership, security audit or commercial endorsement. The listed organisations remain responsible for their products, content, prices, availability, cookies, personal-data practices and contractual terms. A resource may be useful for one project and unsuitable for another because requirements, jurisdiction, budget and technical capacity differ. Française du Numérique does not receive a commission for inclusion in this editorial directory. Before creating an account, purchasing a service or transferring data, visitors should review the official documentation, current terms, support arrangements, export options and relevant independent evidence. When the decision carries legal, financial or security consequences, an appropriately qualified assessment may also be necessary.
Yes. The search field checks resource names and editorial topics, while filters narrow the catalogue by category, geographical origin and resource type. Filtering and sorting take place locally in the browser, so the text entered in the directory search is not sent to a separate search provider. Combining several filters may produce no result even when a useful resource exists in a neighbouring category; in that case, remove one filter or try a broader term. The catalogue descriptions are deliberately concise and cannot represent every feature offered by a third party. Open the official website to confirm capabilities, documentation and current conditions before making a decision.
Use the contact page and provide the resource name, official URL, publisher, relevant category and a short explanation of its value for web professionals or project owners. For a correction, identify the entry and the information that appears inaccurate or outdated, ideally with a primary source. Suggestions are reviewed before publication and may be declined when the destination lacks a clear publisher, duplicates an existing entry, is primarily promotional, creates avoidable risk or falls outside the directory scope. Submission does not guarantee inclusion or a particular position, and paid placement is not offered through this editorial process.