Those are issues with the CMS being used to host the blog. The blog has been around for a long time and isn't using BaseWeb.

What you're suggesting is that when someone releases a library with a commitment to accessibility, they are also responsible to reach out to some completely unrelated comms-focused team, take over their CMS workflow, rewrite it entirely with the new framework, and only then make a blog post about the thing you were trying to talk about.