Robust: Will It Work With Their Tech?
Valid, well-named markup that assistive tech can parse.
Robust: Will It Work With Their Tech? is a free Web Accessibility Academy lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Web Accessibility Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
What Robust Means
Robust is the fourth WCAG principle: your content must work reliably across browsers, devices, and assistive technologies.
Built to Last
Tools change over time. Robust markup keeps working with today's screen readers and the ones people will use tomorrow.
Write Valid HTML
Browsers and assistive tech parse your markup. Valid HTML with closed tags and unique IDs gives them a clean tree to read. ✅
<ul>
<li>First item</li>
<li>Second item</li>
</ul>Name, Role, Value
Every control needs a name, role, and value that tech can read. A real checkbox exposes all three to a screen reader automatically.
Native Elements Win
A real button already has the right role and value. Reaching for a native element is the easiest path to robust markup.
ARIA Fills the Gaps
When HTML cannot express a role, ARIA can add it. Use it sparingly to give custom widgets a name, role, and state.
Bad ARIA Hurts
A wrong role can make a control announce nonsense. The first rule of ARIA: no ARIA is better than bad ARIA.
Unique IDs Matter
Labels and ARIA link elements by id. A duplicate id breaks those links, so screen readers point at the wrong thing.
<label for="email">Email</label>
<input id="email">Test With Real Tech
The only way to know it is robust is to try it. Test with a real screen reader and keyboard, not just your own eyes.
Do Not Lean on Quirks
If your page only works because one browser is forgiving, it is fragile. Standard, valid code survives the next update.
The Robust Question
Ask of every component: will assistive tech read its name, role, and value correctly? If you are unsure, your markup is not yet robust.
Quick Check
Let us test the Robust principle.
Recap: Robust
You learned that Robust means your code works across tech: valid HTML, native elements, careful ARIA, unique IDs, and real testing. POUR complete! 🚀
Frequently asked questions
Is the “Robust: Will It Work With Their Tech?” lesson free?
Yes — the full text of “Robust: Will It Work With Their Tech?” is free to read here on the web, and the Web Accessibility Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Web Accessibility Academy course, upgrade to CoddyKit PRO.
What will I learn in “Robust: Will It Work With Their Tech?”?
Valid, well-named markup that assistive tech can parse. You practise Web Accessibility Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Web Accessibility Academy?
No prior experience is required. Web Accessibility Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Robust: Will It Work With Their Tech?” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Web Accessibility Academy lesson?
Yes. Every Web Accessibility Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Perceivable: Can Everyone Sense the Content?
- Operable: Can Everyone Use the Controls?
- Understandable: Is It Readable and Predictable?
- Robust: Will It Work With Their Tech?