Likely for accessibility and compatibility with mobile devices, but I agree with you; I want something I can download and file away.

Just tack on bloated JavaScript libraries and add "onMouseover" events to everything. That will solve it.

Everything can be a <div> if you try hard enough.

I couldn't agree more. I just don't understand the thought process behind having accordions automatically close. I've seen some pretty egregious ones over the years.

This is a great approach, though it should be applied with care. AI cannot infer context unless you provide it, which can distort the image's description. It’s important to review the text to ensure it focuses on the right elements so that it's not talking about the sky when the sea is what matters.

The Government of Canada subscribes to the EN 301 549 standards, which haven’t been updated in three years and are still based on WCAG 2.1.

It's definitely contextual, but yes, I would add that detail when relevant. I like asking myself "If I were telling someone about this image, what would I say?"

I like captions at the bottom unless it provides indexing information like "Figure 1", in which case I prefer having the information before the figure itself.

I'm a little weird that way and constantly oscillate between the two on my own website with wild inconsistency.

There are no contrast requirements for disabled controls as far as the WCAG are concerned:

www.w3.org/WAI/WCAG21/U...

Alternative text is a short description embedded in an image's code that conveys the image's content and purpose to people who cannot see. They are primarily used by screen readers but also appears in place of the image should it fail to load.