Great post. Here are two more issues that I see often:
If you have to use Font Awesome or any other font icon, avoid the <i> element, which is meant to represent a range of text that is set off from the normal text for some reason, such as idiomatic text, technical terms, taxonomical designations, among others. For that reason, it fails on the WCAG validation. Instead, use <span>, which is semantically neutral and therefore the most appropriate tag for the occasion.
Avoid using <a> elements with empty hrefs as menu togglers and use <button> instead.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great post. Here are two more issues that I see often:
<i>
element, which is meant to represent a range of text that is set off from the normal text for some reason, such as idiomatic text, technical terms, taxonomical designations, among others. For that reason, it fails on the WCAG validation. Instead, use<span>
, which is semantically neutral and therefore the most appropriate tag for the occasion.<a>
elements with empty hrefs as menu togglers and use<button>
instead.