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.
This will improve PDF accessibility on a large scale if we take into account the share of Google Chrome users globally and at the same time add the fact that it will also be possible to use headless Chrome from the command line or server or cloud to generate accessible PDF documents with scripting.
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.
Technical debt is also possible in accessibility and can easily grow when re-using code or components.
Americans with Disabilities Act was signed into law on 26th of July 1990. And it has improved accessibility for other countries too.
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.
Design is art, I agree, but not every new page should be a independent piece of art, consistency is king. Easier to make accessible, easier for the user to use.
Starting soon lowers the costs on the end. And minimizes potentially unneeded dialogs that should already be a part of the design process from before.
I have done some quick practical testing and research about cookie consents accessibility, usability and also some testing with search engines – on some websites in Europe, to see what are consequences of cookie consents for users, owners and search engines.
A lot is written on Continuous Delivery and Continuous Integration and I think they should also include accessibility. Maybe we should define Continuous Accessibility as a part of them as well.
Relying on semantic text highlighting alone can be dangerous as screen readers use to ignore special emphasizing tags to prevent clutter to their users.
It is interesting to compare accessibility errors from a million of popular websites and see if and how are they improving or deteriorating compared to previous year.
At first glance not very much, but when we research the details and difficulties of some user groups then it is not difficult to understand that content must be readable to be understood.
I use zoom as well, and it is a perfect example of accessibility feature that is beneficial for everyone, especially in this demographics with population getting older and older…