I’m Kitty Giraudel, a non-binary trans frontend developer based in Berlin, focused on accessibility and inclusivity.

As designers, we should challenge fragmentation rather than foster it.

Let's break down the new accessibility guidelines!

The “more options” button is emblematic of how something can be technically usable by everyone, but also how it’s use is also confusing for all involved…

A collection of bad practices in HTML, copied from real websites.

A tool that brings attention and understanding to how color contrast can affect people with different visual impairments.

While compliance with accessibility checklists is essential, it doesn’t necessarily mean a pleasant experience. That’s why live sessions can give you lots of priceless insights.

TL;DR: Be careful when using the word menu. Be certain you have chosen the term that accurately describes the control you want. If this post looks familiar to you, that is because it is essentially a redress of my 2020 post Stop Using ‘Drop-down’. It is not as divergent as…

Accessibility consultancy with a focus on inclusion. We can help you with knowledge, experience, strategy, assessments, and development.

How can we make disabled buttons more inclusive? When do they work well, and when do they fail on us? And finally, when do we actually need them, and how can we avoid them? Let’s find out.

Slack’s accessibility team recently launched a series of changes to make navigating around Slack more reliable and efficient for keyboard-only and screen reader users. While our accessibility had significantly improved over the last few years, we were still hearing from blind and low-vision users that moving around the interface felt disorienting and noisy. One user […]

How can we make disabled buttons more inclusive? When do they work well, and when do they fail on us? And finally, when do we actually need them, and how can we avoid them? Let’s find out.

An overview of the new WCAG 2.1 Success Criteria broken down by user groups that they accommodate and other helpful resources.

Making text accessible should be part of everyday practice. However, general typographic practices of optimizing legibility and readability don’t necessarily go all the way towards making text accessible.

Applying the principles of WCAG 3.0 to some current visions of the future

Accessibility, inactive buttons and WCAG

In this article, Kate Kalcevich explains when to use ARIA and how to use it properly so that you can use ARIA in a way that’s helpful to the many disabled people who use [assistive technology](https://makeitfable.com/glossary/?utm_source=Smashing+Magazine&utm_medium=sponsored+content&utm_campaign=Upskill&utm_term=Fable&utm_content=Sept2022) to navigate the Internet. Let’s dive in!

A library of React Hooks that provides accessible UI primitives for your design system.

A guide around how to mark up tabs

“Should I use pixels or rems?”. In this comprehensive blog post, we'll answer this question once and for all. You'll learn about the accessibility implications, and how to determine the best unit to use in any scenario.

Are “accessible” fonts actually as accessible as they claim? If not, what are the things we need to know when choosing a font that responds to different reader needs? This session will explore what dyslexia is, what cognitively happens when we read, and what elements of a typeface make a difference to how accessible it is, and to whom. Bruno, David, and Gareth have decades of experience between them. Bruno as a Typeface Designer, David as a Typographer, and Gareth as a UX Design/Accessibility expert. Together they spent over 3 years researching and steering the creation of BBC Reith family, the BBC’s corporate accessible typeface. This session is from the Design track. About the speaker: Gareth Ford Williams, BBC, Head of User Experience Design, Accessibility Preferred Pronoun: He/Him Gareth Ford Williams In 2005 Gareth founded the BBC’s Digital Accessibility Team. Over the course of the first 3 years the Accessibility Team worked as an integral part of iPlayer’s core Product Team ensuring BBC iPlayer V1.0 launched as an accessible product. The accessibility team became part of UX when the BBC’s UX Design Team was founded in 2008. Gareth established the Design Research Team in 2010 and subsequently became a Head of UX Design. His team manages a network of over 200 Accessibility Champions, the oldest network of its kind in the industry. His team has also pioneered Mobile Accessibility Guidelines, BBC MAG, which were the first in the industry which have been used by thousands of organisations around the world. He has an interest in accessible typography going back his time on attachment as a product manager at YouView where he led the work on selecting the UI typeface, and since then he was a key stakeholder in the delivery of BBC Reith and BBC Qalam. About the speaker: David Bailey, BBC, UX Principal Preferred Pronoun: He/Him David cut his teeth as a designer in the nineties working with world-renowned agency The Designers Republic. In 2005 he formed his own studio, Kiosk, which produced cutting-edge design and branding for the music, arts, fashion and broadcast industries. He joined the BBC as a design director in 2013, spearheading the development of its digital design framework, GEL, and the introduction of their corporate typeface ‘BBC Reith’. This work helped inspire the formation of The Readability Group, alongside Bruno Maag and Gareth Ford Williams. About the speaker: Bruno Maag, Dalton Maag, Typeface Designer Preferred Pronoun: He/Him Bruno Maag is an expert typographer with over forty years of expertise in his field. He founded and led Dalton Maag Ltd, the world’s leading studio for typeface design where he worked with some of the best known brands: Amazon, Nokia, Intel, HP, AirBnB, Netflix, Facebook, DHL, FedEx, ABB, BBC, Rakuten amongst many others. All these brands have in common that their typography needs to be as accessible as possible to the clients’ audiences. 00:00 Don’t Believe The Type! 38:18 Q&A Learn more about axe-con at: https://www.deque.com/axe-con/

F69: Failure of Success Criterion 1.4.4 when resizing visually rendered text up to 200 percent causes the text, image or controls to be clipped, truncated or obscured | Techniques for WCAG 2.0

Why, what and how designers should document accessibility requirements and user interactions to make product better and more inclusive

Easy-to-follow guidelines can make accessibility part of your everyday design process

It’s more important than ever to consider mental health while designing.

Geri Reid, UI and UX Designer, London

Reliable accessible front-end components: :focus styles, content sliders, dark mode, data charts, date pickers, form styles, navigation menu, modals, radio buttons, "skip" links, SVGs, tabs, tables, toggles and tooltips.

Checks contrast using SAPC rather than the current WCAG methods. SAPC is supposed to be much more realistic to how the human eye sees contrast.

Really interesting discussion on the failings of the current WCAG color contrast ratios. The W3C's specification for determining sRGB contrast as discussed in "Understanding WCAG 2.0 and 2.1, Minimum Contrast 1.4.3" is not perceptually uniform and as a result ...