Comment by sodapopcan

3 days ago

> It's also due to browser not doing anything useful with the additional tags,

It's clear that you are sighted and never use reader mode.

Exactly this. I really wish browsers would use semantic html to make content more accessible for me, a sighted user! Why does my browser not give me a table of contents I can use to navigate a long page?

I think the parent has a good point: browsers don't do anything with these tags for sighted users, who are unfortunately the majority of developers. If they were to notice benefits to using semantic tags, maybe they'd use them more often.

  • Developers of all people should be in a position to notice how tag semantics can keep them oriented in a document or target behavior and styling…

It’s interesting, because if you imagine sites actually using these tags to be maximally compatible with reader mode and other accessibility modes, they’re setting themselves up perfectly to be viewed without ads.

I use reader mode by default in Safari because it’s essentially the ultimate ad blocker: it throws the whole site away and just shows me the article I want to read.

But this is in opposition to what the website owners want, which is to thwart reader mode and stuff as many ads in my way as they can.

It’s possible good accessibility is antithetical to the ad-driven web. It’s no wonder sites don’t bother with it.

Reader mode seems to still work if you have a div with article text in it. I would be interested to see a comparison of what works and what doesn’t if such a reference exists though!

  • Reader mode is based on a whole slew of heuristics including tag names, class names, things like link-to-text-content ratio, and other stuff I can't recall. IIRC it considers semantic tag names a stronger signal than e.g. class names, so having <article> in your page isn't necessary but helps a lot.