Expert Guide: Writing HTML for Screen Reader Users
Improve your website's accessibility with our comprehensive guide on utilising HTML for screen readers. Learn the best practices and avoid common pitfalls.
To celebrate and contribute to Global Accessibility Awareness Day, we at the UX Collective have partnered with our most prolific accessibility writer, Sheri Byrne-Haber, CPACC, to bring a more candid take on the topic.
The methods include tips for how to accommodate participants with diverse abilities to ensure that everyone feels included in a workshop setting no matter what they are capable of.
A Complete Guide To Accessible Front-End Components — Smashing Magazine
An up-to-date collection of accessible front-end components: accordions, form styles, dark mode, data charts, date pickers, form styles, navigation menu, modals, radio buttons, "skip" links, SVGs, tabs, tables, toggles and tooltips.
The Department of Justice published guidance today on web accessibility and the Americans with Disabilities Act (ADA). It explains how state and local governments (entities covered by ADA Title II) and businesses open to the public (entities covered by ADA Title III) can make sure their websites are accessible to people with disabilities in line with the ADA’s requirements.
The W3C Accessibility Guidelines (WCAG) 3.0 provide a wide range of recommendations for making web content more accessible to users with disabilities. Following these guidelines will address many of the needs of users with blindness, low vision and other vision impairments; deafness and hearing loss; limited movement and dexterity; speech disabilities; sensory disorders; cognitive and learning disabilities; and combinations of these. These guidelines address accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other web of things devices. They ad...
This document provides readers with an understanding of how to use WAI-ARIA 1.1 [WAI-ARIA] to create accessible rich internet applications. It describes considerations that might not be evident to most authors from the WAI-ARIA specification alone and recommends approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. This document is directed primarily to Web application developers, but the guidance is also useful for user agent and assistive technology developers.