Search
Enter at least two characters without personal information.

    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.

    AI-generated illustration

    Editorial method

    A directory made to be useful, not merely long.

    Selection prioritises recognition within the field, professional use and reference status. Highly specialised documentation entries are consolidated under their main resource.

    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.

    9 resources displayed

    The date applies to the linked document, not to a review of every service feature.

    Web standards and governance

    W3C

    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.

    InternationalInstitution / standard
    w3.orgVisit official website
    Web standards and governance

    W3C WAI

    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.

    Documented characteristics
    Specification
    WCAG 2.2
    Number of principles
    4
    Number of guidelines
    13
    Conformance levels
    A · AA · AAA

    Official documentation ·

    InternationalInstitution / standard
    w3.orgVisit official website
    Web standards and governance

    WHATWG

    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.

    Documented characteristics
    Specification
    HTML Living Standard
    Syntax
    HTML / XML
    Source
    github.com/whatwg/html

    Verification path

    1. Find the normative rule
    2. Associate the label and field
    3. Check the rendered example

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Learning example: a field uses 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.
    Useful check
    The 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.
    Interpretation and next step
    Keep the cited section and consultation date. A valid snippet does not establish accessibility of the whole page. Check the accessible name, focus and error feedback in the rendered example.

    Official documentation ·

    Official documentation · HTML · label

    Official documentation · HTML · email

    InternationalInstitution / standard
    whatwg.orgVisit official website
    Web standards and governance

    IETF

    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.

    Documented characteristics
    Format
    RFC
    Status
    Proposed Standard · Internet Standard · Best Current Practice · Informational · Experimental · Historic · Draft Standard (legacy level) · Unknown
    Check
    Updates · Obsoletes · verified errata
    Source
    RFC Editor

    Verification path

    1. Identify status and subseries
    2. Read relationships and errata
    3. Interpret the requirements

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Learning example: prepare an HTTP note using RFC 9110. Its record states Internet Standard and STD 97. An RFC number does not establish the status of other publications in the series.
    Useful check
    Before citing a passage, examine 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.
    Interpretation and next step
    When a document adopts 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 ·

    Official documentation · RFC 9110 · HTTP Semantics

    Official documentation · BCP 14 · RFC 2119

    Official documentation · BCP 14 · RFC 8174

    InternationalInstitution / standard
    ietf.orgVisit official website
    Web standards and governance

    ICANN

    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.

    Documented characteristics
    Format
    RDAP
    Access
    lookup.icann.org
    Scope
    Generic domain registration data

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Fictional example: during a handover, a generic domain’s RDAP response does not display all holder contact details. That absence is not enough to establish that the name is available.
    Useful check
    Consult ICANN Lookup, then identify the registrar and published statuses. Compare these with the records and access details supplied by the holder.
    Interpretation and next step
    Record the lookup date. Public data provides neither account access nor transfer authority; confirm access rights and renewal responsibility separately.

    Official documentation ·

    Official documentation · ICANN Lookup

    InternationalInstitution / standard
    icann.orgVisit official website
    Web standards and governance

    Afnic

    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.

    Documented characteristics
    Scope
    .fr · .re · .yt · .pm · .wf · .tf
    Access
    Whois
    Checks
    Registrar, dates and nameservers

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Fictional example: Whois for a .fr domain lists nameservers while its website no longer responds. Domain registration and service availability require separate checks.
    Useful check
    Record the displayed registrar, dates and nameservers. Compare them with the management account and expected DNS delegation, without changing records during this initial observation.
    Interpretation and next step
    A Whois record tests neither the web server nor email. Continue with DNS diagnosis and then the affected service; confirm renewal in the registrar account.

    Official documentation ·

    Official documentation · Afnic — Whois (EN)

    FranceInstitution / standard
    afnic.frVisit official website
    Web standards and governance

    Schema.org

    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.

    Documented characteristics
    Specification
    Schema.org
    Syntax
    JSON-LD · Microdata · RDFa
    Checker
    validator.schema.org

    Official documentation ·

    Official documentation · Schema Markup Validator

    InternationalInstitution / standard
    schema.orgVisit official website
    Web standards and governance

    MDN Web Docs

    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.

    Documented characteristics
    Resources
    @mdn/browser-compat-data
    Format
    JSON
    Dataset licence
    CC0-1.0
    Validation
    partial_implementation · notes
    Status
    experimental · deprecated

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Before choosing a browser feature for a form, find its precise MDN compatibility entry under __compat.support. Check the target browser and relevant version. Information about a general API does not automatically describe every method or option within it.
    Useful check
    For a fictional entry marked 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.
    Interpretation and next step
    Record the @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 ·

    Official documentation · MDN Browser Compatibility Data — Data guidelines

    InternationalCommunity / learning
    developer.mozilla.orgVisit official website
    Web standards and governance

    RGAA

    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.

    Documented characteristics
    Specification
    RGAA 4.1.2
    Items
    106 criteria
    Scope
    13 topics

    Official documentation ·

    Official documentation · RGAA · critères et tests

    FranceInstitution / standard
    accessibilite.numerique.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.
    • Distinguish normative requirements from explanatory material and check the criterion’s exceptions.

    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.
    Another case to examineThe external component changed after your review
    Situation
    An embedded service replaces its form while your own page remains unchanged. Its error messages and navigation order may have changed too.
    Before drawing a conclusion
    The previous review describes a particular version and task. Keeping that evidence does not remove the need to check the new interface.
    Practical check
    Complete a valid submission and then trigger an error using the keyboard. Record the component version or date, the feedback received and any new obstacles before renewing your decision.

    Reference : W3C WAI · Forms

    Further documentation

    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.

    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.

    Directory questions

    Selection, independence and updates.

    Entries describe resources from their publishers’ pages and provide a source, category, purpose and checking date. The selection covers different Web tasks rather than ranking every available provider. Open the cited source to check current scope, availability and conditions before relying on a service.

    No. Inclusion identifies a resource to examine; it does not certify every feature, price, policy or result. Compare the resource with your actual task, country, language and technical requirements. Confirm current conditions with its publisher before committing time, data or money.

    Yes. Search the displayed catalogue, combine the available filters and clear them to return to the full list. Every entered word must match the indexed text. The visible result count describes this selection, not the entire Web. Individual category pages and direct links remain available without JavaScript.

    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.

    Compare using observable evidence

    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.

    Use precise terms

    Two distinctions before comparing resources

    Distinguishing link destinations and content roles helps when examining a standards example.

    Documented reference points for this topic

    Documented reference points for this topic
    ReferenceValue or syntaxScope
    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 · @contextJSON-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 processWithin 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 · authenticationAn 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" → 412If-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.