Kevin Bodi
@kevinbodi.no
Managing buttons, crafting brews, and coding websites that just work.
Sites built on these templates aren't just unusable for screen reader users, they also hurt #SEO.
Markup shouldn't be buried under an “accessibility" section. It’s essential.
Authoring tools must guide authors toward the right defaults.
Markup shouldn't be buried under an “accessibility" section. It’s essential.
Authoring tools must guide authors toward the right defaults.
May 7, 2025 at 11:59 PM
Sites built on these templates aren't just unusable for screen reader users, they also hurt #SEO.
Markup shouldn't be buried under an “accessibility" section. It’s essential.
Authoring tools must guide authors toward the right defaults.
Markup shouldn't be buried under an “accessibility" section. It’s essential.
Authoring tools must guide authors toward the right defaults.
A very simple audit of their templates shows that most of them lack any markup for landmarks or heading levels.
This is despite the fact that Figma provides functionality for template authors to define elements like landmarks, heading levels, and image alternatives.
This is despite the fact that Figma provides functionality for template authors to define elements like landmarks, heading levels, and image alternatives.
May 7, 2025 at 11:59 PM
A very simple audit of their templates shows that most of them lack any markup for landmarks or heading levels.
This is despite the fact that Figma provides functionality for template authors to define elements like landmarks, heading levels, and image alternatives.
This is despite the fact that Figma provides functionality for template authors to define elements like landmarks, heading levels, and image alternatives.