“Accessibility”

Digital Publishing WAI-ARIA Module 1.0

Digital Publishing WAI-ARIA Module 1.0 Enabling users of assistive technologies to find their way through Web content requires embedding semantic metadata about Web document structural divisions. This is particularly important for structural divisions of long-form documents and goes along with embedding semantic metadata about Web-application widgets and behaviors for assistive technologies. This specification defines a set of WAI-ARIA roles specific to helping users of assistive technologies navigate through such long-form documents.

Continue reading →

Techniques for WCAG 2.0

This Techniques for WCAG 2.0 document provides guidance for web content authors and evaluators on meeting Web Content Accessibility Guidelines (WCAG) 2.0 [WCAG20] success criteria.

Continue reading →

headingsMap - Chrome Web Store

headingsMap To show (and audit) the headings structure

Continue reading →

Website Accessibility Conformance Evaluation Methodology

WCAG-EM applies to all websites, including web applications and mobile websites. It covers different situations, including self-assessment and third-party evaluation. It is independent of particular evaluation tools, web browsers, or assistive technologies.

Continue reading →

Website Accessibility Evaluation Report Generator

This tool helps you generate a report according to the Website Accessibility Conformance Evaluation Methodology (WCAG-EM)

Continue reading →

Inclusive design

Continue reading →

Web Accessibility Specialist

Links to help me prepare for the IAAP Web Accessibility Specialist certification exam

Continue reading →

Accessibility Testing Methods and Tools

Continue reading →

The Roles Model | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Continue reading →

WAI ARIA Landmark Roles Cheatsheet

You will have better “hooks” to target your elements, avoiding excessive use of id or class attributes. WAI-ARIA Role values can not be repeated, but HTML5 elements can (you can have several header or footer elements in a single page), so it is easier to make sure you are targeting your actual document header, instead of affecting every possible header element that may in the future be put on your document

Continue reading →

1 Next Page