Keeping navigational elements, structure and colour clear and simple with easy to read content not only helps those with cognitive impairments but everyone using content on mobile technologies.
Provide good contrast levels and alternatives to colour so that users can differentiate items – similar shapes with different colours do not necessarily help those with colour deficiencies
- Check how content looks when printed in grey scale as some people do not see difference between certain colours
- Poor visual acuity can make the use of pale shades hard to read when used against similar colours
- Use larger text if contrast levels are poor
Clarity, additional images simple and consistent navigation
- Easy to read text supplemented by images, graphs, and other illustrations.
- Consistent labelling of forms, buttons, and other content parts.
- Clearly structured content that facilitates overview and orientation.
- Predictable link targets, functionality, and overall interaction.
- Hierarchical menu and search.
It seems that some of the key web design trends for 2018 mentioned by MyMarketology Lab fit some of the requirements mentioned in these lessons
Watch out for these barriers
- Wide columns of text or large blocks of text without images, graphs, or other illustrations to highlight the context.
- Complex sentences that are difficult to read and unusual words that that may not translate well.
- Justified text or text that has uneven gaps between words.
- Text styles featuring serifs – e.g. Times New Roman.
- Italic text or very small text.
- Moving or flickering images/effects.
- Mobile Web Accessibility – W3C WAI existing and developing resources related to mobile web accessibility
- Trends in mobile device use by people with disabilities
- European Telecommunications Standards Institute, produces globally-applicable standardsfor Information and Communications Technologies (ICT), including fixed, mobile, radio, converged, broadcast and Internet technologies
- Deque: Mobile Accessibility Web Techniques – May 2017 video (one hour long – in depth support for developers)