Translating Accessibility
Doug Abrams explains what information on a web page should and should not be translated to keep it accessible.
Article Category
Posts
-
-
Everything’s More Complicated in Groups: Required Groups
Alicia Evans navigates through the challenges and solutions of identifying to users when groups of related fields are required.
-
CSUN Recap – Testing Mobile Apps: Tools, Techniques, and Best Practices – Part 2 (Android)
This article is based on a talk delivered at CSUN 2025, by accessibility experts Laurie Pagano, Carolina Crespo, and John Lilly. Testing mobile apps can be difficult because we can’t…
-
Celebrating with The Perfect Toast
In which Lloydi tries to come up with an approach to toasts (and not-toasts) to satisfy various annoyances and WCAG failures with this notification pattern.
-
Event handling in JAWS and NVDA
Complications can arise with JavaScript event handling in screen readers, because the virtual cursor intercepts or modifies page events.
-
CSUN Recap – Testing Mobile Apps: Tools, Techniques, and Best Practices – Part 1 (iOS)
Testing mobile apps can be difficult, so here are some techniques and tools that will make it easier. Part 1 of a 2-part series looks at iOS apps.
-
How to meet SC 2.5.3 Label in Name
For any interactive control that has a visible text label, the accessible name must contain the label’s visible text.
-
An aura of accessibility
Adam Saucier recounts his experience of epilepsy-induced auras, and how it affected his understanding and use of web pages in the immediate aftermath.
-
Tooltips are presentational
The ARIA tooltip role is functionally useless and semantically meaningless, because tooltips only benefit sighted users.
-
Putting AI to the (Accessibility) Test
Over the past few months, Tj Squires has been incorporating generative AI into his workflow as an Accessibility Engineer at TPGi, and there are three vital ways it has provided great aid.
-
When Is a Skip Link Needed?
Many developers might wonder if they need to add a “skip to main content” link on every page or if using headings, landmarks, and semantic HTML is enough to meet the accessibility requirements. The answer is often a bit more nuanced.
-
Announcing TPGi’s first Spirit of Accessibility Award Winner!
At TPGi, we’re proud of the talent, passion and commitment of our team in generating and sharing accessibility knowledge. This year, we established the Spirit of Accessibility Award a way…
-
Designing for Accessibility – Create Accessible User Experiences with AT User Flow Testing
Many organizations on their journey to make digital products more accessible start with a focus on testing against standards such as the Web Content Accessibility Guidelines (WCAG). This helps ensure…
-
PDF Accessibility on the Web: Tricks and Traps – Part 2
Ricky Onsman walks you through some more tricks and traps related to PDF accessibility on the web, with more bonus tips!
-
Mind The (Remediation) Gap
When auditors provide advice on accessibility issues, it’s primarily about the HTML used. But do frontend developers actually know HTML these days? Is the advice falling through a remediation gap?
-
PDF Accessibility on the Web: Tricks and Traps – Part 1
Ricky Onsman walks you through some tricks and traps related to PDF accessibility on the web, with bonus tips!
-
Are You Conducting User Flow Testing in These 4 Critical Areas?
Imagine trying to navigate your favorite e-commerce website as a screen reader user, but instead of hearing about images, product descriptions, and organized menus, you’re greeted by silence. Buttons don’t…
-
Making the Web Accessible: A Focus on Cognitive Disabilities
For many users with cognitive disabilities, trying to navigate a website can be confusing and overwhelming, but this is their daily experience online. Websites that aren’t designed with cognitive accessibility…