Our foundations series provides an overview of core accessibility considerations. They are a good starting point for visual designers, content designers, interaction designers, and developers when designing and building accessible products and services.| TetraLogical
By prioritising semantic HTML and offering keyboard-friendly alternatives for complex interactions, you help create a more inclusive experience for people who use a keyboard.| TetraLogical
As well as labelling text fields with input and labels, form validation and error messages are also essential to making forms accessible to everyone.| TetraLogical
Accessibility consultancy with a focus on inclusion. We can help you with knowledge, experience, strategy, assessments, and development.| TetraLogical
The ARIA Authoring Practices Guide (APG) contains an extensive range of design patterns aimed at helping developers to create accessible web experiences using WAI-ARIA. However, while we encourage web authors to follow these design patterns, a common misconception is that their usage is a prerequisite for conformance. This is not the case.| TetraLogical
Well structured content helps everybody understand and navigate documents. When coded properly in the HTML, headings, lists, and landmarks help people who use screen readers (software that reads what’s on screen) both scan and navigate pages.| TetraLogical
Visible focus styles help us to understand which part of a web page we may be interacting with. You may have seen visible focus styles appear as an outline around a link or a button for example. For people who only use a keyboard to navigate the web, visible focus styles may be one of the few ways to understand where they are in a page and what it is that they are interacting with.| 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
A list is generally agreed to be a series of words or phrases that are grouped together for a reason. That reason might be to remember the items we want from the store, to share our top five favourite movies, or to write down the steps needed to complete a task.| TetraLogical
Session timeouts are designed to protect privacy and security, but if they’re implemented incorrectly, they can prevent people from completing tasks on a website.| 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
In our fifth and final post from our browsing with assistive technology series, we discuss browsing with speech recognition. You can also explore browsing with a desktop screen reader, browsing with a mobile screen reader, browsing with a keyboard, and browsing with screen magnification.| 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
Some people find accessing audio or visual content in video challenging or impossible; for this reason, providing alternatives is a requirement of the Web Content Accessibility Guidelines (WCAG) 2.1. It is a common belief that producing alternatives are expensive and time-consuming. This can be the case when accessibility is not considered at the planning stage of video content. This article describes an inclusive approach to video production that allows you to create accessible videos withou...| TetraLogical
Accessibility resources free online from the international standards organization: W3C Web Accessibility Initiative (WAI).| Web Accessibility Initiative (WAI)
