Our Blog

The Web Accessibility Initiative Accessible Rich Internet Applications specification 1.2, or WAI-ARIA or ARIA for short, is a technical specification written by the World Wide Web Consortium (W3C).

In this post we explore what WAI-ARIA is, and how it can enhance the user experience for people using screen readers.

Meet Joe Lamyman, an accessibility specialist at TetraLogical and lover of all things interactive media.

In this series, Inclusive Extended Reality (XR), we will be delving into ways to design accessible experiences when interacting with 3D objects, augmented reality, and virtual reality.

In our first post about creating accessible experiences within Extended Reality (XR), we highlight some key considerations for designing 3D model viewers by introducing our 3D TetraLogical principles cube.

You can also explore Inclusive XR: accessible augmented reality experiences.

Visible focus styles help us to understand which part of a web page we're 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.

A target size is the area that can be activated in order to interact with an element. For people who have dexterity issues, the smaller a target size is, the more difficult it may be to use the website.

This post explores how to create usable, consistent, and well-spaced target sizes.

Meet Henny Swan, one third of our trio that makes the TetraLogical directors, and accessible user experience and design lead.

Ela Gorla is one of TetraLogical’s principal accessibility specialists and our resident user research and training expert. Read on to discover her top accessibility tips, how she came to work in accessibility and things she wishes she’d known when starting out.

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.

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.

Given that Internet Explorer 11 is now officially retired, organisations occasionally ask us if, from an accessibility perspective, they should continue to support the browser. In short, we're edging (no pun intended) towards dropping support, or at least phasing out support, in favour of Microsoft Edge. There are a few reasons for this, both technical and non-technical.