List known validation errors/warnings

Description

Once we’ve finished the WCAG 2.1 compliance work, we should consider increasing visibility of any known validation errors with our code due to accessibility, legacy etc fixes. This would help users to know which errors/warnings are known / expected.

An example would be the role attribute we add to <header>, <footer>, <button> for older browsers that don’t support HTML5 elements, and the src on SVG issue.

Checklist

• Review and list existing / known issues -> resulting list
• Triage list with team to decide which ones need to be investigated / fixed and which ones should be documented in the Design System / somewhere as known issues.

[NickColley]

Would be good to consider getting this published properly at some point, had reports from a user that it’s not very easy to use as a reference right now.

With Hanna’s list being inside a comment, it isn’t especially easy to read (scrolling horizontally is a pain) and it’d be good to surface the reported bugs, as I didn’t know where to look for them (apologies if there is a big link somewhere obvious 🙂 ).

[hannalaakso]

As discussed above the table is hard to use, especially with regards to horizontal scrolling. I’ve tried to add some inline styles / HTML to the table to limit the column widths to reduce the need to scroll horizontally but Github markdown strips out any inline styles / col attributes so I don’t see a way to control the column widths. We’re basically asking too much of the Github table format and should look to publish these differently.