Editorial policy

HTML5 Doctor is a resource for people learning and using HTML, semantic markup, accessibility and related web technologies. Our editorial standard is to give readers useful explanations, identify who is responsible for them and explain the sources, testing and scope of each article.

Effective 23 October 2026. This policy applies to new work and subsequent revisions. Technical review dates are recorded on the relevant articles.

Responsibility and authorship

The HTML5 Doctor team handles current site administration and editorial enquiries. Administrative responsibility is separate from authorship and technical review. Articles retain their credited authors. A contributor’s name, biography or photograph must not be used to imply involvement in new work without their participation.

New articles and substantial revisions should identify the writer. A separate technical reviewer should be named only when that person has actually reviewed the work. Author biographies must describe real experience and verifiable work; credentials, affiliations and testing must not be invented.

Sources and technical checks

For HTML semantics and conformance, the starting point is the WHATWG HTML Living Standard. Accessibility guidance should refer to relevant W3C WAI specifications and implementation guidance. MDN Web Docs provides practical reference material. An article must distinguish a standard’s requirements from browser behaviour and the author’s own recommendations.

When a new article or revision reports a test, it should provide a reproducible example, the relevant browser and operating-system versions, the test date and any important limitations. Accessibility test claims should identify the assistive technology where relevant. A validator result alone does not demonstrate accessibility or compatibility. Claims of first-hand testing must be supported by work that was actually performed.

Publication dates and updates

Articles are organised by topic, regardless of when they were first published. The original publication date is retained. A substantive technical update should carry a separate update date and explain what changed. Routine maintenance, ownership changes, formatting and policy notices are not a fresh technical review.

Browser support and standards can change. Unless an article documents a later review, its publication date is the starting point for understanding when its advice was written. See Using HTML5 Doctor articles for guidance on checking sources and testing examples.

Editing and AI assistance

Writers remain responsible for accuracy, source checking and the originality of their contribution. If AI or other automation materially contributes to new published content, the article should explain that role when it affects a reader’s understanding of how the work was produced. AI output is not evidence of testing or expert review. These requirements apply to new work and revisions.

Commercial relationships and relevance

New commissioned, contributed and sponsored material must be useful to the site’s web-development audience. A commercial relationship must not be presented as an independent test, an endorsement by an original contributor, or editorial authorship by someone who did not write the work. Read the advertising policy for disclosure and link standards.

Corrections and reader contributions

Readers can report errors through our corrections process. Comments are reader contributions and may contain outdated or incorrect advice; their appearance does not mean editorial endorsement. Spam, personal information and unrelated promotional material may be removed.

About · Contributors · Editorial policy · Corrections · Advertising policy · Contact