The Learning Thread

Having looked at Perceivable, Operable, and Understandable, the final WCAG principle is Robust. This principle takes us into the future, ensuring that all the work done to make sure content is accessible isn’t lost as technology evolves. (If you need a quick refresher on how these earlier principles reinforce each other, particularly how navigation, structure, and media choices feed into robustness, you can revisit the earlier see A Designer’s Guide to WCAG Perceivable Principles, WCAG Operable Principles, andWCAG Understandable) for more from me on the other WCAG principles.)

For this principle particularly it’s important to know which version of WCAG you’re working with. Most current standards reference WCAG 2.1, which introduced guidelines for mobile accessibility and low-vision users. WCAG 2.2, released in 2023, adds success criteria for focus indicators and touch targets, critical for responsive learning content.  

Looking ahead, WCAG 3.0 (still in draft) will shift toward a more flexible, outcome-based model. This means accessibility will be evaluated on a spectrum rather than pass/fail, allowing for more nuanced scoring. For learning designers, this is significant because it prioritises user experience and functional accessibility over technical compliance alone, shifting emphasis from meeting criteria to whether designs remain valid under changing conditions. (If you’re watching how these shifts reflect wider movement in the field; AI‑assisted authoring, adaptive interfaces, and automated tagging, the broader industry view in Top Learning Design Trends for 2026 offers helpful context for future‑ready practice.)

This principle can feel technical, and it is, but by staying informed about these updates you can better understand accessibility reports and remain compliant in the way you utilise programmes. 

What Does Robust Mean? 

Robust content is designed to be interpreted accurately by technology including browsers, assistive technologies, and emerging tools so meaning can still be accessed when systems or contexts change. This means making smart choices when exporting content and choosing authoring tools. Tools that enable: 

• Clean, semantic code and, 
• Proper tagging so that content doesn’t break when technology changes. 

WCAG breaks the principle of Robust into success criteria that focus on ensuring content can be reliably processed by different types of software that display or interact with your content, including assistive technologies. For most learning designers, including myself, the only way to know if the tools I use meet these criteria is to look at the accessibility report. 

However, once a tool has been chosen (by myself or institution), adopting best practices for my input with semantic structure, responsive design, and inclusive interaction patterns will make my content future-ready. It will help reduce remediation work later, and, importantly, constrain whether the design will hold once conditions differ from those in which it was created. (For designers working with video, audio, or interactive media, many robustness issues emerge from how media is structured. For guidance on reducing cognitive overload and improving compatibility, see Top Multimedia Principles for eLearning Design.)

ARIA (Accessible Rich Internet Applications) is worth noting for more technical designers than myself before I move on. ARIA can further enhance accessibility for complex interactive elements when used judiciously to help define the purpose and behaviour of elements for assistive technologies when native HTML semantics aren’t enough. 

Key Actions for Learning Designers 

Here’s what you can do to make learning experiences robust: 

Use Semantic Structure 

When creating content in authoring tools or LMS platforms, ensure headings, lists, and tables use proper semantic structure. For example, apply heading styles (H1, H2, H3) rather than manually formatting text. This, formatting text rather than using semantic structure, is a pet peeve of mine as I regularly use it to navigate long documents. From an editing viewpoint editing the structure means everything tagged as that structure changes which makes it really easy to create consistency. From an accessibility viewpoint, this helps screen readers interpret content correctly and improves navigation.  (Ensuring content is structured, scannable, and technically sound is also a core part of the learning designer’s remit. These expectations are outlined more broadly in The Role of a Learning Designer.)

Tag PDFs Correctly 

PDFs are widely used in learning, but they can be a major accessibility barrier if not properly tagged. Tags define the reading order and structure for assistive technologies. Tools like Adobe Acrobat Pro allow you to add tags and run accessibility checks to ensure compliance. 

Test with Assistive Technologies 

Automated checkers are helpful, but nothing beats real-world testing. Use free screen readers like NVDA or VoiceOver to verify that content is navigable and logical. This step ensures that learners using assistive technologies have a smooth experience under real usage conditions rather than controlled testing environments. If your content will ultimately be viewed on a browser, many like Edge or Chrome have screen readers that utilise your operating system for functionality with no additional costs for you or your learners.  (In team settings, testing workflows and shared authoring practices matter just as much as the tools themselves. Collaborative Tools for Enhanced Learning offers practical ways teams can standardise accessibility habits.)

Choose Accessible Authoring Tools 

Select tools that support WCAG compliance and produce clean, standards-based output that adapts well to different screen sizes and that interactive elements meet WCAG touch target guidelines. Platforms like Articulate Storyline, Rise, and Captivate offer accessibility settings for focus order, alt text, and keyboard navigation. Always enable these features before publishing. 

Tools to Help 

Accessibility Checkers 

I am not sponsored, though maybe I should be as I have mentioned Adobe and Microsoft for every principle, but they really are useful and the most common tool for authors. Acrobat will verify tags and reading orders while Microsoft will flag structural issues. I found Acrobat harder to correct issues in, still do sometimes but very worth checking. 

Screen Readers 

Built-in tools like VoiceOver (MacOS/iOS), Narrator (Windows), and TalkBack (Android) are great for quick checks. Most with temporary accessibility needs will utilise these tools rather than the more complex (and expensive) screen reader programmes. However, pair them with NVDA or JAWS for full compatibility testing as they offer more advanced features with more granular controls. These will also be fully up to date with industry and accessibility standards. 

Quick Decision Tree

Why Robust Matters 

Robustness ensures that your content works now and in the future, reducing potential workload as technology evolves. This principle is a commitment to sustainability and inclusivity. Future-proofing learning experiences so they remain accessible across platforms, devices, and assistive tools. By using semantic structure, tagging PDFs, testing with assistive technologies, and choosing accessible authoring tools, you create learning experiences that stand the test of time and remain interpretable when assumptions about technology and context no longer hold.