The Inclusive Design Principles (IDP) were first published in 2016 by myself, Ian Pouncey, Léonie Watson, and Heydon Pickering. We felt that while the Web Content Accessibility Guidelines (WCAG) set out what to do to meet technical compliance, many design decisions fall outside the scope of WCAG but still determine whether an interface is inclusive, usable, and welcoming. The principles were developed to plug that gap with people-centred guidance that helps teams make better design decisions...| TetraLogical
The European Accessibility Act (EAA) came into effect on 28 June 2025. Many of our customers have asked what impact that may have on the digital services they offer. This post provides information on the application of the EAA in the context of websites and mobile apps.| TetraLogical
While EN 301 549 is the technical standard cited in the European Accessibility Act (EAA), EN 17161 Design for All is a framework that supports embedding accessibility into strategy, design, and development processes. Both are harmonised standards used by the EAA and yet all the focus has been on EN 301 549. This post explores how the two standards relate to each other, and what that means for providers of digital products and services.| TetraLogical
The European Accessibility Act (EAA) requires that products and services made available to citizens of the European Union (EU) are accessible. Like most EU Directives, the EAA (DIRECTIVE (EU) 20191882) is hard to understand, and this has left many people unsure about what it means - and more importantly, what they need to do to make sure their products and services comply. With this in mind, we'd like to share our understanding of the EAA as it applies to digital products and services.| TetraLogical
In this post, we explore how to use the <fieldset> and <legend> elements to group and label form elements effectively, creating a more accessible and well-structured experience.| 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
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
Extended Reality (XR) provides immersive experiences through detailed visual, audio, and multi-media content. When using these different types of content, we need to consider how we can communicate the same information to people with disabilities in order to make XR accessible to everyone.| 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
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
Live regions have a reputation for being "flaky" and inconsistent. While this can be attributed in part to shortcomings in current implementations, the problem can also be caused by developers misunderstanding how live regions are intended to work.| TetraLogical
TVs, set-top boxes and streaming devices are a huge part of all our lives and should be accessible so everyone can watch what they want, when they want, how they want. We've started exploring challenges people with disabilities may face when interacting with TV apps and considerations for people designing and developing TV app interfaces.| TetraLogical
In our second post about creating accessible experiences within Extended Reality (XR), we highlight some key considerations for designing accessible augmented reality (AR) experiences with our AR TetraLogical principles cube. You can also explore Inclusive XR: accessible 3D experiences.| TetraLogical
This article gives an overview of what an accessibility assessment is, when it is beneficial, and when another service such as an Insight Report may be better suited.| TetraLogical
When a website is assessed using the Web Content Accessibility Guidelines (WCAG), it is rarely feasible to test every single page. Instead, the assessment can be based on a sample of pages that are representative of the website as a whole, to keep things as efficient and cost-effective as possible.| TetraLogical
A new law concerning the accessibility of public sector websites and mobile apps came into effect in 2018. This article explains what the Public Sector Accessibility Regulations mean, what’s included and what isn’t, and the deadlines by which all public sector websites and mobile apps must comply.| TetraLogical
The Web Content Accessibility Guidelines (WCAG) are a set of recommendations for making websites and apps accessible to people with disabilities. This article explains WCAG and how to use them.| TetraLogical
