Accessibility for screen readers etc. - Githubissues

fac-14 / Brickworks-Tollington_Project

MIT License

2 stars 5 forks source link

Accessibility for screen readers etc. #49

Open MissArray opened 6 years ago

MissArray commented 6 years ago

Update: accessibility features

Use <ul> or <ol> for lists, not <p>
Please don't change high-contrast colours to low-contrast colours
Please reserve heading tags for headings. Don't use them for emphasis
Use <hr> only for thematic changes, not as breaks between list items

https://www.w3schools.com/tags/tag_hr.asp https://accessibility.umn.edu/core-skills/bulleted-numbered-lists

Design all features with accessibility in mind:

tab navigation should be enabled
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.

More 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/