` which IkiWiki doesn't use anyway. With that being the case, I'm not sure whether we gain anything from not generating HTML5 (or "HTML" as it's now labelled) all the time. In particular, non-HTML5 mode uses `` which doesn't allow newer markup like the `role` attribute, so we can't close [[todo/add_aria_landmarks_to_make_ikiwiki_websites_more_accessible]] while remaining XHTML 1.0 Strict. The recommended pseudo-doctype for HTML5, and for HTML with ARIA markup, is ``. (I do think we should continue to use `` and output well-formed XML so people who want to do XSLT tricks with IkiWiki's output can do so, though.) In practice, real browsers have never actually implemented a strict XHTML mode: they've always parsed `text/html` as "tag soup", because they need a tag-soup parser anyway, and nobody wants to maintain two parsers. Options include: * set html5 to 1 by default but retain the dual-mode templates * remove the option and always behave as if it had been 1, simplifying the templates Thoughts? --[[smcv]] > Another possibility would be to change the doctype to `` > unconditionally, stop trying to limit ourselves to XHTML 1.0 Strict > (use HTML5 features that degrade gracefully, like > [[ARIA roles|todo/add aria landmarks to make ikiwiki websites more accessible]]), > but avoid using the new elements like `

` that require specific > browser support unless `html5` is set to 1. That would get rid of the > backwards-compatibility concerns while keeping the ability to use > post-2000 markup. --[[smcv]]