HTML semantics is a nice idea that helped us to get through years of HTML spec crisis and markup nihilism. We got our ”new HTML5 hope” and a bunch of new semantic tags, accompanied by a few repurposed old ones. But does it really make a difference? There’s a huge gap between HTML spec’s good intentions and what browsers are willing to implement. And there’s even a bigger one between all of that and what screen readers actually support. Writing semantic markup only because the good spec is a spec and it is good and it’s a spec is not the worst approach you can take, but it might lead you to HTMHell.
Talk title
The road to HTMHell is paved with semantics
Abstract
HTML semantics is a nice idea that helped us to get through years of HTML spec crisis and markup nihilism. We got our ”new HTML5 hope” and a bunch of new semantic tags, accompanied by a few repurposed old ones. But does it really make a difference? There’s a huge gap between HTML spec’s good intentions and what browsers are willing to implement. And there’s even a bigger one between all of that and what screen readers actually support. Writing semantic markup only because the good spec is a spec and it is good and it’s a spec is not the worst approach you can take, but it might lead you to HTMHell.
Your name (and pronouns)
Vadim Makeev, he/him
Contact Details
Code of Conduct