Symbols are cool. They add decoration and/or information to user interfaces. For screen reader users their inclusion can sometimes be annoying or confusing as the visual and aural user interface…
Is there a recommended ARIA pattern for making sure that <mark> is properly announced in screen readers? — Šime Vidas (@simevidas) December 3, 2017 Short answer is no, but there…
In pursuit of a better user experience I, and many others like me, have long wrestled with this beast and others of its kind. Attempting to tease out the rhyme…
One of the tasks I perform regularly is to test web content using screen readers. It can be somewhat annoying to be capturing data in a desktop application while testing…
Back in 2012 I did some testing of ARIA alert support across browsers, screen readers and operating systems. The results were not encouraging. Fast forward to yesterday, while in a…
There’s a lot of help online about making Portable Document Format (PDF) accessible. Even with all the advice out there, I still encounter people who find it difficult to make…
“Necessity is the mother of invention” We have changed our Quality Assurance (QA) methods recently at TPGi and now require a screen reader friendly method to find spelling errors in…
The TPGi partners Mike, Debs and Charlie have always placed an emphasis on developing and sharing knowledge on how to make the web more accessible for users. A major aspect…
Native HTML elements don’t require the addition of ARIA attributes to expose the semantics they have, as, for the most part, browsers expose this information: YAY. This is expressed in…
ZoomText Magnifier/Reader is a popular combination magnifier/screen reader, primarily for users with low vision. A feature it provides is Web Finder, which makes use of HTML semantics to provide navigation…
The following content written by me, was until recently a part of the W3C Custom Elements specification, but was removed/substantially re-written when a new editor took over. As we think, in…
A discussion occured on A11ySlackers gitter channel last evening about whether use of the following markup pattern was a WCAG 2.0 failure: <img src=”a.gif” alt=”” title=”some text”>
You can make an element scrollable using CSS overflow property, problem is that typically the content cannot be scrolled using the keyboard.
I have reported previously on support in browsers and screen readers (SR) for aria-hidden and the HTML5 hidden attribute. The last time was 2 years ago, the orginal article published…
Tooltips have always bugged me, apart from regularly mispelling as “TOOTlips” it is a bugger trying to create one that works across browsers with Assistive Technology (AT), in particular screen…
Error messages can be problematic to convey consistently to all users across browsers and assistive technology (AT). Using simple HTML, with a little ARIA polyfil magic if you want to…
Recent articles by people of TPG:
Any change in WCAG 2.1? Nope, 2.1 parsing criterion is still a PITA The WCAG 2.0 Parsing Criterion is a Pain In The Ass (PITA) because the checking of it…