I believe in web for everyone.
It all started as an idea for a way scientists could share data about physics experiments and now we know, the web has changed the world.
It’s not only governments job to form rules and regulations for the digital channels but it is equaly important for the big or small organizations to do more for human rights, democracy or public safety. That’s why we have a responsibility to make sure it is recognised as a human right and it has built for the public good.
In theory, any webpage should be accessible regardless of the device it is used on. The web was never meant to lock people into some sort of box. The idea was that you could link anything, connect the dots, and to contribute and be a part of the information system. The web’s greatest power has always been the ability of anyone to build anything.
The first step towards designing accessibility is to understand how people with disabilities use the web. I believe that the blind person can do everything as an individual with full vision, but it takes them a bit longer or it takes them an alternative way of finding it and getting to it BUT they can do it. My job is to make things easier and remove barriers that are blocking them from various rights, opportunities, resources that are available to other people. While perfect design solutions do not yet exist, the first step in the design-thinking process is to empathize.
How to measure digital accessibility?
At the moment, I measure accessibility using WCAG 2.X. But on the horizon there’s WCAG 3.0, which is going to change the way we measure the accessibility of our digital products and channels.
Current 2.X guidelines are pass/fail and don’t reflect on “real-world” accessibility. Humans aren’t binary and we don’t fit this model. WCAG 3.0 is about real people in their real environments and how our products can serve their needs. Current 3.0 draft includes the needs of people with a wider range of disabilities – particularly the needs of people with cognitive disabilities or low vision who often don’t fit the pass/fail success criteria of WCAG 2.X.
Improved color contrast with 3.0
As a designer, the most interesting part is APCA (Accessible Perceptual Contrast Algorithm). For example, the current measurement scale is not working, because you get a lot of issues in the midrange oranges and blues. The current ratios will be replaced by a level out of 100. The highter the number, higher the contrast.
Disclaimer: I’m not an accessibility expert, just an accessibility advocate attempting to make the web a friendly place for everyone.