120 cards
This deck is a focused review of web accessibility fundamentals, with an emphasis on ARIA patterns used to make interactive interfaces usable for everyone. It covers the basics of the a11y acronym, how accessibility differs from general usability, and the disability categories and conformance levels defined by WCAG 2.1. You'll also find targeted questions on contrast ratios, the POUR principles, the purpose of the ARIA specification, and the practical rules developers are encouraged to follow when adding ARIA to their markup. A few cards dive into accessible name calculations, helping you understand how assistive technologies resolve labels from native HTML, aria-label, and aria-labelledby.
It's well suited for front-end developers, UI engineers, designers, and QA or accessibility specialists preparing for interviews, certifications, or day-to-day implementation work. Beginners with some HTML familiarity will find it approachable, while experienced practitioners can use it to refresh the precise numbers and rules that are easy to forget between projects. If you're studying for a specific accessibility exam or onboarding into a team that cares about inclusive design, this deck gives you a tight, question-driven way to lock in the essentials.
Because the material mixes conceptual knowledge (like POUR principles and ARIA rules) with concrete specifications (such as exact contrast ratio thresholds), active recall will serve you well. Try answering each card out loud before flipping it over, and pay extra attention to the contrast ratio values, since they are the kind of detail that slips away without spaced repetition. Studying a handful of cards per day across a week or two is more effective than cramming everything at once, especially for the numeric guidelines.
One practical tip as you work through the deck: whenever you see a question about ARIA rules or accessible name precedence, pause and think of a real component in your own projects where that pattern applies. Connecting the cards to code you have actually written will make the answers stick and help you apply these patterns confidently in future interface work.