The CSS before/after pseudo-selectors can be used to insert content into a page. In some situations this technique is a useful thing to do, but how do browsers and screen readers handle the generated content?
When a web application has a session timeout, it’s a good idea to warn users about the impending timeout and give them the opportunity to do something about it. It’s therefore important to make sure that all users know when the warning notification appears.
Traduction française Windows screen readers have multiple modes of interaction, and depending on the task being carried out they’ll automatically switch to the most appropriate mode. This post explains why Windows screen readers behave the way they do, and how your code can influence that behaviour.
The subject of screen reader detection has been under discussion lately. It isn’t something I’m comfortable with, so I’d like to share the reasons why.
There is an unusual problem with Jaws and Internet Explorer that causes the word “region” to be announced before every field in a form. Fortunately there is a workaround until the problem itself is resolved.
Most current screen readers support ARIA to one extent or another, and many now support some features of HTML5 as well. With ARIA and HTML5 making increasing amounts of semantic data available to screen reader users, it’s really easy to inadvertently overload people with too much information. Let’s take an example that crops up from […]