Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility for screen readers etc. #49

Open
MissArray opened this issue Oct 8, 2018 · 0 comments
Open

Accessibility for screen readers etc. #49

MissArray opened this issue Oct 8, 2018 · 0 comments
Labels
best practice recommended practices for tackling specific problems

Comments

@MissArray
Copy link
Collaborator

MissArray commented Oct 8, 2018

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/

@MissArray MissArray added the best practice recommended practices for tackling specific problems label Oct 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
best practice recommended practices for tackling specific problems
Projects
None yet
Development

No branches or pull requests

1 participant