In the first part of this article, I've discussed keyboard accessibility issues which are often found in overlay windows, and which affect both sighted keyboard users and screen reader users. Apart from these issues, dialogs can be tricky to use for screen reader users for few other reasons.
All posts for "ARIA" tag
Technical delivery document
A Technical Delivery Document is designed to aid the client's understanding of the way we work and what the outcome is on the end user. We feel it is beneficial to try and communicate our approach at the start of a project and better manage the client's expectations at the same time.
A short guide to how and why you should validate your code.
How ARIA landmark roles help screen reader users
This video from Nomensa demonstrates how ARIA landmark roles help screen reader users understand the purpose of different areas of a web page, such as search, navigation or main content.
Accessible Tabs - Part 2: The Solution
As we saw in Accessible Tabs Part 1 - The Problem, there are several accessibility issues with tabs created for the web compared to those created for use in software applications. Tabs on the web should ideally replicate the functionality used in applications, so they are more intuitive for everyone. In this article we will look at three existing scripts for creating accessible tabs.
Screen Readers And WAI-ARIA Landmark Roles
WAI-ARIA Document Landmark Roles
The Accessible Rich Internet Applications (WAI-ARIA) specification defines a set of roles known as document landmarks. They can be used to programmatically identify key areas of content on a page, which means they can be interpreted by access technologies such as screen readers.