Jason Knight
2 min readAug 1, 2022

--

And making the reply to your MDN stuff a second post because it's a bit more complex.

That is clearly NOT the H1. Why? Becuase in the footer what should be H2 -- MDN, Support, Commnities, Developers -- are not marking the start of subsections of "Resources for Developers , by Developers_"

That's a gibberish document outline.

The bottom four are not subsections of the splash/banner. They’re subsections of the whole site and would be on every page. Thus H1 makes no sense. Just as that H3 for “contributor spotlight’ does NOT seem to be part of “recent contributions”. It does nothing to tell someone on a braille reader or screen reader what SITE they are on. Since again <title> isn’t content and generally not used by such user agents.

That is NOT the H1 that would be consistent for all headings on all pages. That’s the first H2. It is a content section, not the base / root heading that everything else is part of.

Of course their recently pissing on the site with the sticky header crap, making the banner area search harder to use by removing the fieldset, and endlessly mindlessly slopping DIV and classes for nothing in there is why its’ not only been made uselessly inaccessible the past year or so, they’re also vomiting up 43k of markup on a page that likely doesn’t warrant a third that.

But MDN’s website goes in cycles like that. The content is always good, but how they build sites alternates between amazing and utter garbage. It’s like they get new people, veer horiffically off course, and then take corrective action.

Though I don’t see corrective action coming this time since they up and fired all the talent like six or seven months ago.

--

--

Jason Knight
Jason Knight

Written by Jason Knight

Accessibility and Efficiency Consultant, Web Developer, Musician, and just general pain in the arse

Responses (1)