Post AKJS2zFPyhl2orxFhY by felix@wandering.shop
(DIR) More posts by felix@wandering.shop
(DIR) Post #AKIa5cfmyIg29K66AC by Alamantus@cybre.space
2022-06-09T02:44:26Z
0 likes, 0 repeats
Web #Accessibility #question: If I have content that is equivalent to multiple articles on a single HTML page, can I have one H1 tag per title or should I still only have one at most?(idgaf about SEO)#A11y
(DIR) Post #AKIa5diJ6QHlNQHcjA by msh@coales.co
2022-06-09T02:53:56Z
0 likes, 0 repeats
@Alamantus I would think it is perfectly valid to have multiple <article> containers in an HTML file, each with its own H1 tag and heading structure. It makes sense semantically so it should be fairly accessible by nature.
(DIR) Post #AKIa5eatpRxE6jpDou by Alamantus@cybre.space
2022-06-09T02:52:00Z
0 likes, 0 repeats
I see in this thorough article that eluded my searches until I explicitly added "A11y" to my query that no, multiple H1s will mess up some assistive technology, and that's what I really needed to know:https://www.a11yproject.com/posts/how-to-accessible-heading-structure/
(DIR) Post #AKIaoxcRwPFk8z9ciu by Alamantus@cybre.space
2022-06-09T03:02:07Z
0 likes, 0 repeats
@msh See that line of thought makes sense to me too! But I keep seeing articles saying that more than one can cause issues, but I don't really know if that applies to my use case, where the content is clearly intended to be multiple pages on one page... I know I'd ideally have multiple pages, but this is for a sort of backup situation where the whole site is on a single page for when JavaScript can't run.
(DIR) Post #AKIbDGgSi6taDpcbhY by msh@coales.co
2022-06-09T03:06:33Z
0 likes, 0 repeats
@Alamantus I am actually a bit surprised there is no talk about semantic markup beyond H# tags in such a recent article. <article> containers are supposed to denote independent content and hence independent structure. There are also specific tags for headers, footers, sections and navigation and sometimes suggestions on how user agents involving assistive technologies should handle them.Perhaps there is a lot of assistive tech that does not observe semantic markup I dunno. Also standards are full of ambiguity. I blame w3c for being too persnickity with XHTML and WHATWG for pushing back too much in response making HTML5 a bit trashy.
(DIR) Post #AKIeZG8JjqA0kOpQtU by msh@coales.co
2022-06-09T03:44:08Z
0 likes, 0 repeats
@Alamantus another take on headings (many h1 is good actually)https://webdesign.tutsplus.com/articles/the-truth-about-multiple-h1-tags-in-the-html5-era--webdesign-16824A single H1 per document is not a standards requirement. It is actually an artifact of obsolete technology interpreting a document as a single article. As such the first H1 was interpreted as the title and subsequent H1 tags were...well...open to interpretation.Semantic HTML5 document outline algorithms recognise a compendium of independent sections and articles as a valid document and user agents are expected to follow current behaviour except....inertia I guess and the tools being kinda garbage in general.Even with the "current ways" you can still have a single H1 in the top level of your body or main content then H2 as the top level of articles but there are disadvantages to that too. Ultimately the best approach would be to test against the most popular screen readers/non visual user agents to confirm it works as intended.
(DIR) Post #AKJS2zFPyhl2orxFhY by felix@wandering.shop
2022-06-09T12:58:30Z
0 likes, 0 repeats
@msh It's an article specifically about headings. It says as much right from the title.
(DIR) Post #AKJTZIdhW2MoBNHhom by msh@coales.co
2022-06-09T13:15:36Z
0 likes, 0 repeats
@felix yeah I read it, but the discussion of semantics is pretty much limited to "don't use H# tags as styling markup"...and a little bit later a bit about it being good for SEO too. However I think there was a missed opportunity to look at how H# tags fit in the larger context of a document's semantics, as there has been ongoing debate on how they fit into sections and articles.Essentially, it would be a more useful article to devs to see the reasoning behind headers as providing structure to the *HTML document* vs articles or sections, which the standards suggest represent autonomous content. Consider this scenario: a website may host articles in both a "single article" page and in a "week in review" page with all of those articles rendered in a single document. This article says "one H1 only" as well as "don't skip H# levels". That means the article contents would have to be altered for each view which is problematic.I don't think that is out of scope for an article specifically about headings.
(DIR) Post #AKJUYucMvX4vdS2a5g by msh@coales.co
2022-06-09T13:26:44Z
0 likes, 0 repeats
@felix anyways...the web is kinda trash ans WHATWG is kinda the instigator (though W3C provided the motivation for the formation of WHATWG) and it is frustrating for creators. This situation where it is valid HTML5, and even HTML5 that is presented as "good practice" by this standards group, but on the other hand "yeah but user agents don't support it so don't use it" from other experts.This is really a crappy situation, and tragic that a standards body *founded by the developers of HTML user agents* cannot be motivated to adequately support *their own standards* and work to help devs of alternative user agents support standards as well.