You’ve made it through the course! Congratulations! 🥳
- Learn HTML
- Progressive enhancement is your friend. It forces you to think about the most important layer first.
- PE is not anti-JS. You’ve seen in several chapters that JS is imperative for creating truly accessible components and widgets. Use it wisely.
- Look up AAPI mappings and make a habit of inspecting the a11y tree. It gives it important insights into the a11y of your work.
- Fire up a screen reader.
- Try to simplify your components whenever you can. Choose a few radio buttons instead of a select dropdown when you’re offering a few options.
- Under-engineering your components will get you far ahead.
- Don’t overthink it. You’ll more often need less ARIA than you think. -Don’t try too hard — it’s almost as bad as not trying at all.
- ARIA is a polyfill. Use it as such.
- We’ve seen a few patterns and how they can be built without ARIA in the live regions chapter. A simple hint, using simple controls, and less ARIA can go a long way.
- One of my goals with this course is to have a larger impact so that we can colectivelyn make the web a more inclusive place, The place it was intended to be. Hopefully next year’s WebAIM results will be better.
- BE an a11y advocate. A11y isn’t as hard when you shift it left and have it in mind from the get-go. and always always test.
Under-engineer your patterns. Use simpler, more robust controls.
- Select dropdown? use radio buttons if you can.
- date input? use three separate text inputs.
- menu? use a simple disclosure widget.
Thank you for taking this course with me.
Provide feedback? take survey? // links in text version of chapter
Further learning