HTML validator reports warnings/errors for site redesign pages

[lcarcone]

(links updated to use beta.w3.org)

I checked with the following three pages:

https://validator.w3.org/nu/?doc=https%3A%2F%2Fbeta.w3.org%2F

https://validator.w3.org/nu/?doc=https%3A%2F%2Fbeta.w3.org%2Fstandards%2F

https://validator.w3.org/nu/?doc=https%3A%2F%2Fbeta.w3.org%2Fblog%2F

I addition to fix the few errors, a global remark is that the attribute "role" should be removed where it is redundant with the semantic of the element.

Also, it seems that the trailing slash is not necessary for void elements.

[vivienlacourba]

a global remark is that the attribute "role" should be removed where it is redundant with the semantic of the element.

Example of such warnings reported by the validator:

@NicolaSaunders do you think it is ok to remove those?

[NicolaSaunders]

In some (older) browser and screen reader combinations, when using an SVG as the source for an image if role="img" is not included the SVG is announced as "group" rather than "image". See https://www.deque.com/blog/creating-accessible-svgs/

Adding the .clean-list class to a list may remove the list semantics, so where it is deemed to be important that a list is still exposed to users as a list, irrespective of the CSS display property, role="list" is added. See https://www.scottohara.me/blog/2019/01/12/lists-and-safari.html

The HTML validator is not able to pick up on this nuanced use of the role on elements which should already have that role.