There is an all-in-one article including every part from this series (if you want prefer to read it all at once instead of "by installments")
We've heard many times developers say, "HTML is accessible out of the box," almost as if the definition of HTML in the dictionary was:
But that is not always the case. There are HTML elements that are not accessible by themselves or may present challenges to the users.
For example, elements like
<audio> have controls that are not fully keyboard-accessible and that differ considerably from browser to browser and cause frustration. Or the
<input> element has many types that open pop-ups, which may not be accessible for everyone.
There are many components and structures that are not native HTML elements (e.g., tab panels), and once we start combining HTML, accessibility issues may pop up from the interaction.
The definition of HTML in that imaginary Hitchhiker's Guide to the (Web) Galaxy should be updated to something more appropriate:
That looks much better, and it is definitely more accurate to reality.