Accessability

Question 1

tools to help audit a site

Answer 1

• introductory tools, you need humans to help solve your problems
  
  • wave - extension, best tool within a browser.
  • lighthouse
  • chrome dev tools
  • axe - robust for single developer, you want to be testing as you’re developing
  • site improve
  • contrast checker
  • sketch - plugins you can use
  • stark - plugin in design tools like xd, sketch etc. Equivalent of grammerly for design. It’s like a spell check, really basic preventable things.

Question 2

• how important is human testing?

Answer 2

• introductory tools, you need humans to help solve your problems
  
  • software will only detect 30% at it’s highest
  • user flow
  • in lawsuits settlement agreement will include a provision that will provide end user testing - happens often now

Question 3

common things to follow

Answer 3

1. unlabeled images
   * some of good linters will give a warning if you miss alt text
2. page structure helps with seo and screen readers - like article, section
3. html tags use them for their purpose
4. in js frameworks - if you use a div as a checkbox you have to reinvent the wheel for compliance; aria labels whole lot of baggage that comes with it - use the native html checkbox element

Question 4

arya tags

Answer 4

• arya tags - if you have 2 nav sections - put arya label
• wave will tell you which arya labels are missing
• arya attributes - easy to misuse them - you can do a lot of damage with them, strongly encourage to go to web accessibility and learn how to use time
• if you use the right tags you don’t have to use arya

Question 5

resources

Answer 5

ada site compliance