Generating Accessibility Test Results for a Whole Website With Pa11y CI · Matthias Ott – User Experience Designer
Matthias Ott is an independent user experience designer and developer from Stuttgart, Germany. Besides design practice he teaches Interface Prototyping at the Muthesius Academy of Fine Arts and Design, Kiel.
article vs. section: How To Choose The Right One — Smashing Magazine
In this article, Olushuyi explores a mental model that helps you decide between the `` and `` elements when writing documents. You will explore how grouping content affects accessibility and how you can make it all count for users.
Once again, the advice is in the title of the post. But I will ramble anyway since you scrolled this far. First run with the advice, and then review some background on ARIA and how navigation and menu items are defined. This way you can tap out quickly when it…
Generating Accessibility Test Results for a Whole Website With Evaluatory · Matthias Ott – User Experience Designer
Matthias Ott is an independent user experience designer and developer from Stuttgart, Germany. Besides design practice he teaches Interface Prototyping at the Muthesius Academy of Fine Arts and Design, Kiel.
Level Up Your Headings Game · Matthias Ott – User Experience Designer
Matthias Ott is an independent user experience designer and developer from Stuttgart, Germany. Besides design practice he teaches Interface Prototyping at the Muthesius Academy of Fine Arts and Design, Kiel.
It’s Mid-2022 and Browsers (Mostly Safari) Still Break Accessibility via Display Properties
It was late 2020 when I last tested how browsers use CSS display properties to break the semantics of elements. I had been waiting for Safari to fix how it handles display: contents for four years now, and was excited when the announcement came in June. Then I started testing…
If a state is important enough to indicate visually, it's probably important enough to expose to assistive technologies. Here's how we can use that to create more robust styles.
Richtlinien für barrierefreie Webinhalte (WCAG) 2.1
Die Richtlinien für barrierefreie Webinhalte (WCAG) 2.1 decken einen großen Bereich
von Empfehlungen ab, um Webinhalte barrierefreier zu machen. Wenn Sie diesen Richtlinien
folgen, dann werden Inhalte für eine größere Gruppe von Menschen mit Behinderungen
barrierefreier sein. Dies beinhaltet Vorkehrungen für Blindheit und Sehbehinderung,
Gehörlosigkeit und nachlassendes Hörvermögen, eingeschränkte Bewegungsfähigkeit, Sprachbehinderungen,
Photosensibilität und Kombinationen aus diesen Behinderungen sowie einige Vorkehrungen
für Lernbehinderungen und kognitive Einschränkungen; es werden jedoch nicht alle Benutzeranforderungen
für Menschen mit diesen Behinderungen abgedeckt. Diese Richtlinien beziehen sich auf
die Barrierefreiheit von Webinhalten auf Desktops, Laptops, Tablets und mobilen Geräten.
Darüber hinaus wird das Befolgen dieser Richtlinien Webinhalte in vielen Fällen für
Nutzer im Allgemeinen benutzbarer machen.
The Surprising Truth About Pixels and Accessibility: should I use pixels or rems?
“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.
Building accessible web applications: What, Why, Who and How - by Konstantin Tieber
Konstantin thinks accessibility is a topic that anyone who builds user interfaces for humans on the web should be aware of. In this talk he's answering the "...
Building The Most Inaccessible Site Possible With A Perfect Lighthouse Score - Manuel Matuzović
Google’s built-in testing tool Lighthouse judges the accessibility of our websites with a score between 0 and 100. It’s laudable to try to get a high grading...
Making Disabled Buttons More Inclusive | CSS-Tricks
Let’s talk about disabled buttons. Specifically, let’s get into why we use them and how we can do better than the traditional disabled attribute in HTML