LibraryArticles & FAQ Your projectRequest a quote
LanguageEN
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 resources Troubleshooting methods Plan for updates and an exit

Illustration

Editorial 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.

01

Official foundations

Standards bodies, official documentation and public authorities are used as primary reference points.

02

Professional tools

Established services are grouped by actual use: building, hosting, measuring, securing, publishing or promoting a website.

03

Independent reading

Inclusion is editorial and unpaid. A listing does not imply a partnership or guarantee.

Before choosing

Compare on three practical questions

Web standards and governance
CriterionQuestion to resolve
Text versionIs the cited recommendation published, experimental or superseded?
ApplicabilityWhich requirements actually concern your page, interface or audience?
VerificationCan 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.

22 resources displayed

Web standards and governance

W3C Web Sustainability Guidelines

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
InternationalInstitution / standard
w3.orgVisit official website
Web standards and governance

W3C Internationalization

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
InternationalInstitution / standard
w3.orgVisit official website
Web standards and governance

Insee Code officiel géographique 2026

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
FranceInstitution / standard
insee.frVisit official website
Web standards and governance

W3C Bidirectional HTML

Markup guidance for isolating opposite-direction fragments in text mixing Arabic, Latin names, URLs and numbers.

W3C — Inline bidirectional markup · Reviewed

Use it for : Prepare trials mixing Arabic, Latin names and numbers; check display, copying and actual link destinations.

Apply it to a project
InternationalInstitution / standard
w3.orgVisit 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.

Examples : W3C · RGAA

Related guide : Publish accessible website content every day

Explore troubleshooting situations

Troubleshooting methods

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.

Validation passes, but the form remains difficult

What you observe
The code produces no syntax error, yet a person cannot tell which field to correct. An automated result and a user task describe different dimensions.
Before drawing a conclusion
Valid syntax alone cannot establish label clarity, error announcements or the ability to complete a task using a keyboard.
Verification step
Trigger an error with demonstration data. Record the field, message, focus position and action needed to continue. Then use the relevant assessment framework to classify each barrier.

Two examples appear to disagree

What you observe
A tutorial recommends an attribute or structure missing from the documentation you consulted. The pages may come from different periods or address different contexts.
Before drawing a conclusion
A tutorial update date does not prove every example was revised. Explain a discrepancy before copying its code.
Verification step
Keep both links, the relevant passages and a minimal example. Check the reference version and expected behaviour in your context, without changing several things in one experiment.

A translation changes a requirement’s meaning

What you observe
Two language versions use terms that appear to express different obligations. The difficulty concerns the scope of the text, not just its vocabulary.
Before drawing a conclusion
A translation or summary can explain a document without having the same status as the reference version published by its organisation.
Verification step
Identify the reference version, preserve the sentence’s context and record your interpretation as a question to confirm. Have important terms reviewed before turning them into acceptance criteria.

Further documentation

Record the findings in the acceptance log

Keep useful data when changing tools

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.

Keep the reference

Record title, version and cited section. In a report, separate normative text from the practical explanation used to apply it.

Review a decision

Keep the page example and examined behaviour. A component change should allow repeating the check even if the explainer moves.

Hand over

Can someone else find the rule and understand why it was chosen? A screenshot without a reference cannot support that transfer.

Apply it to a project
Transparency

Editorial scope and third-party websites

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.

Suggest a resource or correction
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.

Start with requirements relevant to your interface and context. A list found elsewhere may concern another audience, assessment level or technology. Document why each criterion was selected; do not present a partial check as a complete assessment.

Provide a reduced example, expected result, observed behaviour and a link to the reference passage. Specify the browser and interaction methods involved. Remove personal data and credentials from shared code: the question should remain reproducible with demonstration data.