Once again a discussion I had on problems with headings after an accessibility audit. Can we get it right and can we have a sustainable solution? I believe so!
Writing a blog post on the 25th of December allows me to write about wishes. And one of them is to have better tools for accessibility auditing.
This post tries to describe what I would like to get from the tool. Realistically, noting too advanced.
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.
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.
I decided to try to make my own Google Voice Assistant action that will return quotes on accessibility, universal design and also quotes from famous and less famous people with disabilities on their digital experiences.
aXeSiA – my open source contribution to accessibility testing and axe-hackathon. We all like to use browser extensions to test the pages but aXeSiA makes our work easier if we want to automate it.
Scaling down web browser is not enough. We should really test with physical devices and with at least Android and iOS based devices. UI and UX tests are important but so is testing accessibility with mobile screen-readers.
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
Why are we not encouraged to use ARIA everywhere? Because it is a last option – if we are not able to find a native semantic element, or if we want to create something special, then we can use ARIA. But it should be used wisely!
Some reflections on my newly acquired Web Accessibility Specialist certification and a mention of Neuralink that will be demoed today and can have positive implications on accessibility as well. If used correctly.
A bit personal post, but I really do think that empathy builds our awareness about accessibility and by at least trying to think about others we can be better at it.
I wanted to expose sweet points from the Making Facebook.com accessible to as many people as possible article that was published on 30th of July 2020 as it is an excellent example of continuous and from-start accessibility in my opinion and we should all implement at least some parts of it in our work-flows.
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.
Do not think that alternative text is a set and forget thing. Picture can mean different things in different contexts, so the alternative text must respect that.