Whenever you test web accessibility you need to consider all the website variants based on all media queries. This can be vital for your time usage estimates!
Tag: CSS
Latest posts:
What would I have in an automatic accessibility testing tool if I could have anything that is possible with today’s technology?
Well, I would start at the beginning – clear scope and known priorities is a start and sometimes we can’t really cover all that when we have to choose where we need to focus. Next, I would like to teach the tool, so that it will be more and more independent. And because I like to stand for my decisions – I would like to use the blockchain to prove my efforts and fixes. Words can be empty, deeds talk.
We are most probably failing a WCAG success criteria 1.4.10 Reflow because of CSS’s inability to fix word breaks for us. What can we do to allow grammatically correct word breaking when our browsers can’t help us yet?
Minimum viable product that is not accessible is not really minimum. And then also the WCAG on level AA is the minimum, a baseline. When we reflect over those two facts – we must agree that MVP must at minimum conform to WCAG 2.1 on level AA. If this MVP will run in EU’s public sector even WCAG 2.1 on level AA alone is not the minimum.
Some accessibility issues originate in code. And when design is being recreated with code it may seem to work but when thinking about accessibility we may notice that it only works for some users and not for others. I’ve decided to describe some common accessibility fails that are on developers.
Automatic testing of software is brilliant. Saves a lot of time and effort, prevents problems soon and makes our products better. But when trying to automatically test accessibility we need to know about the challenges and problems before. Some tools may even produce wrong results and some tools may report everything is perfect when they can only test up to a third of criteria.
Web is full of sticky or fixed elements and they may add to usability for some users. But if we think about variety of different users we may quickly note the possible problems for them. Covering too much screen, covering important other elements, or even blocking users totally can be prevented with proper planning and testing. This article tries to map the problems as a first step to proper awareness.
The more I know about alternative text for images the more I understand the complexity of it. There are differences between users and content creators about decorative and informative image objectives and developers should never decide if image will be decorative or not. HTML standard includes a lot on this as well and should be read by more people for better accessibility and better web in general.
Every (front-end) developer should add screen-reader to their tools. Screen-reader experience can really help us make products more accessible and also be better at our coding. Combinations of screen-readers and browsers can get over complicated, so it is important to think if code we write is supported for majority.
Semantics is how things reflect structure and meaning and Cascading Style Sheets (CSS) can change all that. So CSS can have huge impact on accessibility as well. Be mindful about it and forget about pixel perfect first – think user first, pixel second.
Accessibility for web and mobile seems to be very code-oriented, but it really starts much earlier – in the design phase.We should really shift accessibility left, on the whole picture – from A to Z. That also goes for design and initial product setup, not just developing!
Animation can enrich the content, sometimes content is animation, and sometimes animation is preventing users to understand your content or even giving users a really hard time or in some cases even make them sick. So please be responsible with animation, and most importantly – let user control it.
New CSS media query that can enable more control for high contrast mode and what high contrast mode actually is and how it is not only a dark mode
No, PDF is not accessible out of box, sorry to say. How to make it accessible then – an introduction
I believe all users should have the focus outline visible, but not everybody agrees with me. And there is a new CSS pseudo selector on the horizon – :focus-visible that is somehow connected.