Without data we just have opinions. Having a lot of data in different formats can take time to process and sometimes also mean we can’t really compare state of accessibility if countries use different methodologies. If all countries had same data set or even better, central registry it would make data more accessible. And we could save time and money.
WCAG 2.2 seems to be around the corner, document is currently a Proposed recommendation. But what does that actually mean?
I was asked if I can issue “WCAG certificate” for a website, so I decided to investigate what would that actually mean as we all know that sites and mobile apps are constantly evolving and changing and even if they conform to WCAG they may not the following day. What would then mean to issue a WCAG certified certificate and still be ethical and the right thing to do?
W3c recently published Accessibility Maturity Model and I wanted to add some reflections of mine in this post. They refer to 4 maturity stages and I think there could even be 5 for some not so transparent organizations out there.
When in need for a custom widget / control er even basic site element – it is easier than ever before to just get it from the web or maybe even create one from scratch. This post tries to explain what has to be considered.
Web accessibility iniative on testing – valuable resource with a short reflection from me