You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
colour palette and fonts must pass accessibility tests
any effects (e.g. on hover) should be cosmetic, not essential to functionality
html elements: use headings, main, form labels and native HTML buttons
avoid JavaScript for styling, where possible
check whether using a reset.css interferes with accessibility and users' preferred browser settings. If it does and also bloats the code and adds to loading time, we should scrap it, as we do set margins and padding in any case in our main css.
Update: accessibility features
<ul>
or<ol>
for lists, not<p>
<hr>
only for thematic changes, not as breaks between list itemshttps://www.w3schools.com/tags/tag_hr.asp
https://accessibility.umn.edu/core-skills/bulleted-numbered-lists
Design all features with accessibility in mind:
headings
,main
, form labels and native HTML buttonsMore on the pros and cons of resets here:
https://meiert.com/en/blog/reset-style-sheets-are-bad/
https://vanseodesign.com/css/css-resets-pros-cons/
The text was updated successfully, but these errors were encountered: