Accessibility consultancy with a focus on inclusion. We can help you with knowledge, experience, strategy, assessments, and development.| TetraLogical
In this post about forms, we explore how to effectively label text fields using <input> and <label> elements to create form inputs that are both accessible and user-friendly.| TetraLogical
Why, what and how designers should document accessibility requirements and user interactions to make product better and more inclusive| Stéphanie Walter - Senior UX Designer, Mobile Expert, Conference Speaker, Bl...
When conducting usability testing with disabled users, we observed how well images performed from both a visual and non-visual perspective when it came to finding and understanding content.| TetraLogical
As part of our ongoing effort to meet the Web Content accessibility Guidelines (WCAG) 2.1 and 2.2 Level AAA, we've created British Sign Language (BSL) versions of our video and created BSL playlists in our TetraLogical YouTube channel. In this post we explore our process for adding BSL to videos and share some tips.| 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
A design system is a library of styles, components, and patterns used by product teams to consistently and efficiently launch new pages and features. A good system has accessibility embedded throughout and includes documentation, guidelines and implementation notes for accessibility.| TetraLogical
Text descriptions are primary content, and when images do not have a text description, anyone who cannot see the image will not know its purpose. This means people may be unable to access content or perform related tasks.| TetraLogical
Understanding how people with disabilities browse the web using assistive technologies (AT) is core to making an accessible and inclusive user experience. Our browsing with assistive technology videos series introduces commonly used software, who uses it, how it works, and ways people navigate content.| TetraLogical
In our fourth post from our browsing with assistive technology series, we discuss browsing with screen magnification. You can also explore browsing with a desktop screen reader, browsing with a mobile screen reader, browsing with a keyboard, and browsing with speech recognition.| 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 second post from our browsing with assistive technology series, we discuss mobile screen readers. You can also explore browsing with desktop screen readers, browsing with a keyboard, browsing with screen magnification and browsing with speech recognition.| TetraLogical
An element's name, or accessible name, is how it's identified. An accessible description provides additional information, about the element, that complements the accessible name. In this post we explore assigning accessible names and descriptions using HTML and WAI-ARIA.| TetraLogical
Overcorrecting for one form of disability may unintentionally negatively impact the experience for other forms of disability. For example, partially visually hidden link names may work great for people who use screen readers, but this approach can be problematic for people who rely on voice control software. Because of this, your designs need to be flexible and adaptable, as well as accommodate the many different ways people can interact with them.| Smashing Magazine