So much of your talk are things I can empathise with or I’ve had first-hand experience of. How can you get people who make decisions to empathise with your users and so approve features to be more inclusive?
Hi Chris, as I said during the talk it depends on what the culture is at the company and what aspect of not doing or considering accessibility will have the most motivation for them. There are three main types of arguements to think about.
Moral - this shouldn’t be a discussion, it is our moral duty to make things accessible.
Financial - If 15% of users cannot access our product / services it will impact the bottom line.
Legal - It is illegal to make inaccessible software and you can be fined. I’ve also heard this referred to as LDD or lawsuit driven development
There is a fourth where you could focus on reputation and point to the publicity things like the Dominos website and app got when they wouldn’t fix theirs and spend millions in court when the fix was under $40,000.
I also mentioned I’d post a link to my talk on arguments and assumptions. The arguments part is from 16 minutes onwards. This is also one of the reasons I swapped from a 5% grey background to white text on black. High contrast for the win!
Hi Heather and thank you for a great session. I cover a lot of this in my response to Chris but if empathy is the goal i’d suggest saying that anyone of us can join this demographic at any point and probably will to some degree as we age. The other option is thinking about situational accessibility issues. The Microsoft Design Toolkit does a nice job of showing permanent, temporary and situation accessibility. Image from page 42 and link to download it below.
No preference Heather but they each have their own good and less good bits. This article has information on iOS 14 features and under the Even more section about half way down is the part on accessibility. As well as ‘allegedly’ improved Voice Over there’s a ‘back tap’ where you tap the back of the phone to do things. Am looking forward(ish) to seeing what that is like. I’m already confused enough with two and three finger gestures on the front!
Hi Fiona, and welcome to the community. While I don’t have any real views on particular colours I do know that certain things are more friendly to the majority of people. I think higher contrast on mobile is useful in more contexts than sat in an office. Your question did make me think of the article below as it has some great suggestions for ‘calm’ design. @chris_dabnor asked a question which was related so might be interested in this.
That is very much an accessibility issue as it means the site is not meeting the WCAG (web content accessibility guidelines) criteria. If something is not keyboard accessible it means for those using assistive technologies to interact such as braille keyboards, blow tubes, switches etc. will not be able to use it. If you have found this I’d strongly recommend getting a VPAT (voluntary product accessibility template) report. These give you a good overall idea of where your product or service stands in terms of accessibility. This is something you can have a go at filling in but to get really good feedback a specialist source is the best as they almost always get full time screen reader / keyboard users who know accessibility inside out. Actual experts if you will.
I think awareness of types over keeping up is probably more useful if you are starting your accessibility journey. If something isn’t keyboard accessible then it is going to block assistive technologies as they are, at the fundamental level, just a different kind of keyboard. The inputs are the same. This is worth investigating if you’re interested as it is a fascinating subject about human adaptation. The link below has a short video explaining how switch access works. Switch being an externally connected device to control the phone.