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
Accessibility consultancy with a focus on inclusion. We can help you with knowledge, experience, strategy, assessments, and development.| 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
If you have little experience with ARIA, screen readers, or testing in general, understanding accessible descriptions can be trickier than understanding accessible names (already confusing for many). I have written explanations so many times for clients and in fora that I opted to put this together so I maybe never…| Adrian Roselli
Meet Andre, a music producer and blind screen reader user who is not afraid to take his custom elsewhere if your site is not accessible. Andre shares his experience using the web including his love of headings and consistent design to help him navigate, and his dislike of accessibility overlays and poorly implemented page updates using live regions.| 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
Meet Hasmukh, a talented blind cricketer with lots of patience and determination. Hasmukh shares his experience using the web with a screen reader and highlights the importance of accessible emails, forms, language, and prioritising content within a web page.| 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
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
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...
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
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
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
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.| TetraLogical
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.| 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 user story usually focuses on the value a software feature will deliver to an end-user, and an accessibility user story is no different. Whether you need to write an accessibility user story to fix issues found in an accessibility review, as part of a business case, or as part of your service delivery plan, there’s not much that you need to do differently.| 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
Colour is a valuable tool for communicating meaning. But if you can't see colour, then meaning is lost. Always plan to use colour to convey meaning in combination with another means of identification.| 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
These 10 quick accessibility tests can help you understand how easy or difficult it is for people with disabilities to perceive, operate and understand content on your website or mobile app. The tests are helpful for anyone wishing to get an idea of a product's support for accessibility, including project managers, content editors, procurement managers, and many others.| 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 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 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