This post offers an overview of various disability types across four groups: seeing, hearing, moving, and thinking, and provides a brief exploration of what disability is, highlighting how permanent, temporary, or situational disabilities can affect us all.| TetraLogical Blog
Accessibility consultancy with a focus on inclusion. We can help you with knowledge, experience, strategy, assessments, and development.| TetraLogical
18/5000 한국어 번역| Tink - Léonie Watson - On technology, food & life in the digital age
When `tabindex="0"` is applied to an HTML element, the content marked up using that element will become keyboard focusable, and is therefore a good starting point for supporting keyboard accessibility. However, applying this attribute haphazardly or unnecessarily can reduce the experience for people who use a keyboard or an equivalent input device to navigate web content.| TetraLogical
Traduction française| Tink - Léonie Watson - On technology, food & life in the digital age
Supporting keyboard-only interaction is one of the most important principles of web accessibility. However, the scope of the Web Content Accessibility Guidelines (WCAG) in relation to keyboard accessibility is often misunderstood.| TetraLogical
This document is a practical guide for developers on how to add accessibility information to HTML elements using the Accessible Rich Internet Applications specification [WAI-ARIA-1.1], which defines a way to make Web content and Web applications more accessible to people with disabilities. This document demonstrates how to use WAI-ARIA in [HTML51], which especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies.| www.w3.org
Deciding whether to use native or custom components for a website or web application can have implications in terms of development effort, user experience, and accessibility. This post considers the pros and cons of each approach with a focus on accessibility, and provides guidance on how to choose one.| TetraLogical
HTML semantics provide accessibility information about page structure and an element's role, name, and state, helping to convey the nature and purpose of content on web pages. In this post we explore what HTML semantics are, and how they're experienced by people using assistive technologies like screen readers and speech recognition software.| TetraLogical
In our third post from our browsing with assistive technology series, we discuss browsing with a keyboard. You can also explore browsing with a desktop screen reader, browsing with a mobile screen reader, browsing with screen magnification and browsing with speech recognition.| TetraLogical
In our first post from our browsing with assistive technologies series, we discuss desktop screen readers. You can also explore browsing with a mobile screen reader, browsing with a keyboard, browsing with screen magnification and browsing with speech recognition.| TetraLogical
Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address ...| www.w3.org