seirdy.one/layouts/shortcodes/image-figure.html

<figure itemscope="" itemtype="https://schema.org/ImageObject"
	{{- with .Get "id" }} id="{{ . }}" tabindex="-1"{{ end -}}
	{{- if .Get "representative" }} itemprop="image">
<meta itemprop="representativeOfPage" content="true" />
	{{- else }} itemprop="hasPart">
{{- end }}
{{ .Inner | markdownify | safeHTML }}
</figure>
Switch to XHTML5 markup The site now has polygot markup and can handle both XHTML5 and HTML5 parsing rules. My staging site will be XHTML but my main site will be HTML5, just in case of parse errors. If other tools (e.g. LightHouse) end up supporting XHTML5, I'll consider switching the content-type to XHTML. 2022-05-30 15:49:31 -07:00			`<figure itemscope="" itemtype="https://schema.org/ImageObject"`
A11y: drop draft ARIA, overhaul in-page links - Stop using draft WAI-ARIA 1.3 that isn't supported yet - Make in-page links focusable across shortcodes/partials - Replace existing in-page heading anchor links with a more accessible option. - Make backlinks aria-labelledby instead of giving them an aria-label, so they can be translated. 2022-05-19 17:18:14 -07:00			`{{- with .Get "id" }} id="{{ . }}" tabindex="-1"{{ end -}}`
Fix image structured data 2022-05-06 10:30:11 -07:00			`{{- if .Get "representative" }} itemprop="image">`
Switch to XHTML5 markup The site now has polygot markup and can handle both XHTML5 and HTML5 parsing rules. My staging site will be XHTML but my main site will be HTML5, just in case of parse errors. If other tools (e.g. LightHouse) end up supporting XHTML5, I'll consider switching the content-type to XHTML. 2022-05-30 15:49:31 -07:00			`<meta itemprop="representativeOfPage" content="true" />`
Fix image structured data 2022-05-06 10:30:11 -07:00			`{{- else }} itemprop="hasPart">`
			`{{- end }}`
			`{{ .Inner \| markdownify \| safeHTML }}`
			`</figure>`