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.
Meet Felicity Miners-Jones, our fearless project manager, and hear what her top accessibility tips are and what she wished she'd known when she started out in accessibility.
Quick Response (QR) codes are graphics that can be scanned to direct people online to complete an action or find content. This blog post explores considerations and provides guidance for creating accessible experiences with QR codes.
One of the most important and challenging aspects of running inclusive user research is finding participants with a wide range of access needs, who can provide feedback on different features of your products. Our third post from the Inclusive user research series answers key questions around recruitment.
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.
Meet Léonie Watson. Our purple-haired maverick was TetraLogical's founder back in 2019 and has guided this accessible ship through an incredible amount in such a short time.
TalkBack only announces role information for a relatively small number of user interface (UI) elements within native apps. When comparing this behaviour against web content, this can often give the (false) impression that these elements must have been coded incorrectly and therefore need to be "fixed".
This blog post looks at when it is acceptable for a role not to be announced, the roles that TalkBack does announce, and what this means for conformance to the Web Content Accessibility Guidelines (WCAG).
We like to listen. If you have a project, product, problem, or idea that you want to discuss, get in touch!