
I watched the zoom call with David Fairbrother and like Paul said it was quite informative.
We do take the fundamentals like colour contrast and the hierarchy of information for granted. Over 94% of of content not meeting accessibility standards just proves that businesses and brands producing content don’t take these factors into account. That’s a shockingly high percentage but it also begs the question…if it’s that high and they’re still getting the traffic is accessibility really that important?!?
Well as modern designers and the fact so much more content is being produced everyday it really is. Sure the vast majority is using bells and whistles to promote their service or product and with the lack of accessibility not withstanding ‘doing exactly what it says on the tin’. If we take that extra care on the structure and colour contrast for not just those with disabilities but with those who have to work in noisy or hectic environments that percentage could take on so many other users and therefore bring down that percentage.
David made it clear that these considerations really do need to be taken into account at the beginning of the process. All these sites, apps, games etc are so far into their brand identity that to make these changes; they really would have to start from scratch or even worse let AI take the content and rework it to meet these standards.
This is of course another case of us being dependant on technology to enhance and improve accessibility is a catch 22; if they use AI…Sure its going to do a great job producing the content that caters to a much wider audience but at the same time this will help evolve AI to an even higher level which effectively will push the original creative thinkers one step closer to becoming redundant.
We were shown a few examples of content that do & don’t meet accessibility standards.
90% of these examples were easily recognisable but the other 10 I think are up for debate. I’m not saying David was wrong; he’s obviously in a position to identify the guidelines and knows how content should be displayed. The one example I didn't really agree with though was the page that prompts you with accessibility options. he said the other page met the standards better. He was right of course he is right with the simple structure, easily legible fonts and appropriately contrasting colours. I just think to myself if the right options are selected, the page could be structured accordingly with the aesthetics that enhance the the user experience. Accessibility is important but you also want the user to have the best experience possible.
The Figma plugin was brought up and David again shot this down. I think he was just trying to reiterate the importance to the younger developers; not so much how bad the plugin in is but more how fundamental these standards are & that we shouldn't have to be dependant on plugins.
Personally I’m glad of it. I’m a designer that thinks of the aesthetics and how much adding subtle shadows or textures with animations can really improve the users engagement with the product or the service.
I have always reverse engineered my ideas. Having a final concept in mind then build it up from there but now I understand the importance of accessibility a little more I will most definitely work in the other considerations with my process. I think at first I will probably use these plugins and online resources until I get a better understanding - take my concept then see if they adhere to the guidelines then begin sketching and prototyping.
I think the fact these plugins and resources are available is a positive acknowledgement of the need to make content more accessible…
Comprehensive Accessibility Testing Services | TestDevLab
Web Accessibility for Designers | Udemy
I did take this as a great resource to get that understanding and to test my content.