Our super web designers at Six Ticks have noticed an increase in big tech fails in the news lately, as big companies and organisations are falling short when it comes to accessibility for website and app users. So, this week we take a look at some key examples of how not to create user-friendly online systems:
Domino's Fail to Deliver
The folks at US Domino’s Pizza were in trouble recently because their website and mobile app were not fully accessible for blind people, with a customer taking them to court over online accessibility.
The customer noticed that Domino’s software was not compatible with his Apple smartphone’s built-in screen reading software which helps visually impaired people to use the internet. The software relies on a company website or app to be tagged with text for it to work. In Domino’s case, the app and websites were not appropriately
After several appeals, the case has been sent back to US District Court, and the fight to improve accessibility for visually impaired users continues...
A Very Hard Brexit for Apple Users
Another story that caught our eye was the recently launched app from the Home Office, which was designed for EU citizens to use apply to remain in the UK after Brexit.
Completing official government paperwork on a mobile app? That sounds great
Well if you have an Android smartphone then it really is. But if like almost half of UK smartphone users you have an Apple device, there is sort of a hitch - The Home Office’s ‘scanning your passport’ feature – a key part of the application process, doesn’t work on Apple devices, meaning that users have to either borrow an Android phone, or complete their paperwork manually and post it to the Home Office.
Smartphones and websites are such a key part of our lives nowadays that it seems crazy that huge
What Can I do to Make my Website and Apps Accessible for All?
Six Ticks’ super team of app and website developers create custom made apps and websites for businesses and
- Make sure your website is responsive: This means that your website works on all screen sizes, not just mobile, tablet, and desktop
coloursthat contrast and, preferably, are at opposite ends of the colourspectrum
- Do not solely rely on
colouror images for navigation through the site
- Use a reasonable font size for all text, with an absolute minimum of size 12 (12pt/16px/1em/100%), but preferably larger
- Use ALT tags: by ‘tagging’ your images, visually impaired users who rely on screen reader software will be able to know what image is appearing on their screen
- If you launch an app make sure that it is available at least on Android and Apple devices.
These are just the basics, but there is a range of guidelines that should be followed for more advanced accessibility, such as:
- The Web Accessibility Initiative (WAI)
- WebAIM’s Web Content Accessibility Guidelines (WCAG)
- W3C’s Authoring Tool Accessibility Guidelines (ATAG)
- W3C’s User Agent Accessibility Guidelines (UAAG)
- W3C’s Accessible Rich Internet Applications (WAI-ARIA)
- W3C’s Evaluation and Report Language (EARL)
- 508 Testing