In the first post of his advanced ARIA series, Deque Software Developer Harris Schneiderman gives a refresher on the principles of ARIA – and how to use it to fix common accessibility issues. This series is a must-read for developers looking to take a deep dive into implementing web accessibility.
Calling all content creators and UX Designers! Our Deque University course on Accessible InDesign will provide you with the tools and know-how you need to make your InDesign content assets accessible. PDF or EPUB? We’ll help you figure it out. What to do about complex images and anchor text? We’ll show you the way. Read on to learn more.
Check out this useful course on PowerPoint Accessibility Techniques from Deque University. This course covers the ins and outs of easily creating accessible PowerPoint presentations, with practical tips and a11y hacks for anyone that wants to “do better” at PowerPoint.
Take Deque’s Mobile Accessibility Challenge: Next week, watch Paul J. Adam’s webinar for developers, Mobile Accessibility 101. Then take the Mobile Web Accessibility course offered at Deque University (with both self-paced and instructor-led options). This dual-pronged method is your comprehensive guide to mobile accessibility!
What are your favorite accessibility tools and checkers? That’s the question we asked the experts on our accessibility team. From aXe to WAVE to NoCoffee and more, our accessibility experts discuss the merits of their favorite accessibility tools that they use in their daily work.
Find out more of what Deque University has to offer in this week’s course highlight: HTML and CSS Accessibility. Designers, web developers, QA testers and content creators can learn how to implement accessibility into HTML and CSS – plus prevent and fix accessibility errors in their code.
Remember the early days of web accessibility, when Bobby and Cynthia Says were the accessibility tools to know? In this post, Deque’s accessibility subject matter experts discuss their favorite early accessibility tools and checkers that paved the way for later innovations in digital accessibility.
Previously Paul J. Adam explained how to build ARIA role=”alert” Modal Dialogs in his A11y support series. In his latest post in the series, Paul details how to build another ARIA widget: a simple role=”button” UI control. He also explains what screen reader and browser combinations are supported when using other ARIA attributes allowed on role=”button.”
Learn about the newest cool tool from Deque: The Android Analyzer, which will help developers create accessible Android apps with the integration of accessibility testing into their development workflow. The Analyzer’s rules have been developed in accordance with emerging WCAG mobile standards. Best of all, it’s built for both manual and automated testing and can be specified to meet developers needs.
The following post is the first in Paul Adam’s new blog post series, “WAI-ARIA Widgets, Design Patterns, and Accessibility Support […]
Ambiguous IDs: Harmless Lurker or Queen of Disaster? A Little Background It’s one of the most common WCAG 4.1.1 violations […]
Something you may not be aware of: at any given time: roughly 20% of Americans have either a temporary or […]