Responsible Design: Accountable Accessibility

Arrived 10 minutes late, so

Bill Gregory – CGI – @thebillygregory

As a web developer, I took on responsibility for coding accessibility into my projects

When good enough stopped being “Good Enough”

  • Spent more time planning code up front, which lead to less time fixing later
  • Questioned everything on the page, made sure it was documentes
  • Wireframes became my recipe, I refused to  cook without them
  • Always assumed at least SOME level of accessibility

Own your code

  • Real lessons in teh stuff you did wrong
  • Every gbug could be a chance to learn something you didn’t know before

 

Top 10 things I can do that I have complete control over

  1. Semantic mark up
  2. ARIA landmark roles
  3. Lists and the many ways we can use them
  4. Skip links
  5. Focus
  6. Headings
  7. Forms and labels
  8. Alt text
  9. Hidden text
  10. Testing

 

QUESTIONS

How do you approach a dev when they come to you to learn “after they’ve already done everything?”  When baking chocolate chip cookies, you bake the chocolate chips into it.  If you add them afterward, it’s not a chocolate chip cookie, it’s a cookie with chocolate melted on top of it.

Missed a few questions ’cause I was listening and not typing…sorry!

 

One thought on “Responsible Design: Accountable Accessibility”

Comments are closed.