only as big of a deal as you want to make it, i suppose

I both relate to this, and yet also feel like I need to do this _more often these days_ due to shoddy spas choking on their reimplementing native browser behaviors and arbitrary session timeouts without warning.

then if they were given accessible names or desc (e.g., via aria-label/description) then browsers could have a consistent default role to expose, rather than have to either 1. do nothing and let the name / desc not be exposed, or 2. do 'something (maybe)' & have have an inconsistent experience

header and footer can be used anywhere per how they're defined in HTML.

but the landmark roles _aren't supposed to be used nearly as liberally_

so rather than have header and footer fall back to a generic role (which is how it has been for _years_)

the point of these new roles is that you shouldn't need to be using them with the html elements.

the elements aren't always supposed to be landmark roles. for a very long time they switched between being landmarks or generic.

If one were relying on common sense, then one would know that a good number of people do not rely on common sense….

Red and white deck? Nice

That’s a fair question, but for the frequency it occurs in some of the services I have in mind.

But if that’s the case, I’d rather the option not even be provided since it appears to never actually work.

THE WCAG

No really Make this a slide. Bookend my career.

I give you permission to quote me as saying “what the ever loving fucking fucking fucking fuck. Fuck…”

I’m glad to see you showing up more in my feed.

that makes one of us