Total Results: 53
Results per page:
source UDM

Contrast is very important to colour-blind people: to prevent loss of information carried by colours or misunderstandings, developers should design mock-ups in grayscale and choose colour palettes and opacity options based on the preliminary results of online contrast checking tools. Ensure contrast ratio of text blocks is at least 4:5:1, except for very large texts, purely decorative images or backgrounds or parts of brand names or logotypes. Do not design contents in a way that is known to cause seizures or physical reactions, especially to people with cognitive impairments or specific sensitivities (synaesthesia, epilepsy, etc.)

Recommendation code: 5
source UIL

Font design is nowadays a fully independent branch of what can be called “digital art”. The temptation of using peculiar styles and playful combinations can be considered a positive attitude when designing contents that need to be highly recognizable. Indeed, essential information should always be easily read and identified. All users would suffer while reading long text blocks using fonts with low reading-speed.

  • A text spacing that is too different from the standard 1x would be detrimental for all people, especially those suffering of temporary or permanent visual impairments. Wrong text spacing pushes users to abandon reading immediately.
  • Apply a font style that is approved and validated for visual and cognitive impairments to all essential information and leave the artistic touch for logotypes, decorative elements or fillers.
  • Avoid massive updates revolutionising the application identity and structure to prevent users’ loss of confidence and familiarity

 

Recommendation code: 6
source UDM

Providing customisation, personalisation and adaptation options gives the user the feeling that the app and/or service was developed for them, with their needs at the center. Providing a personalised app will positively impact user experience and will help to market the app or service to vulnerable to exclusion groups.

Offering the possibility to partially customise the theme (colour, contrast, fonts and content behaviour), provided that at least one of them is fully-accessible, is one of the possible solutions to satisfy both the need for a nice-looking applications and to provide clearer and simpler versions to users who prefer to use the service in a more efficient and safe fashion, according to their specific needs .

Full personalisation is also an option, but people with impairments would probably find it difficult to configure their version without support. If personalisation options are offered, a guided procedure and support for first configuration must also be provided. Inclusive adaptation is a tricky topic since it requires in-depth knowledge about all possible contexts of use and all the specific needs of vulnerable-to-exclusion people. Moreover, it’s important to allow users to deactivate adaptive contents in case of need (e.g. high battery consumption).

Customisation, Personalisation and Adaptation may sound as features that only digital experts are able to configure. In INDIMO, thanks to our COPs and Co-creation communities, we are sure that it’s a matter of human-centred design, training and experience. When people get familiar with an application (from basic to advanced users), they appreciate the possibility of configuring it according to their needs.

Foresee the possibility to specify accessibility settings. A non-exhaustive list of required options from our research are:

  • personalization options to adapt the application to a specific condition
  • personalized notifications about accessibility issues (e.g. disruption, elevators out of service)
  • voice-based commands and directions (search, route planning, navigation).

Offering such options and the possibility of saving preferences when switching to new devices or reinstalling the application would make the personalisation process worth the time spent in it. Some people would also appreciate the possibility of sharing their preferences with peers or friends with similar needs. Personalisation options availability is a good strategy to foster peer-to-peer promotion of the app. Here some examples on how personalisation increases accessibility:

  • Users with cognitive disabilities may need to reduce the number of controls to create a more memorable interface.
  • Users with slower-than-average reading or input ability may prefer to map several actions to a single action or automate a process: offer users the possibility to do so with the option of saving or automating a “recurrent action” and easily find it when they need it.
  • Users with learning disabilities such as dyslexia may prefer a different font for texts. Offer the opportunity to switch between different theme-fonts or choose a font certified for full accessibility, for example those classified as Sans Serif (e.g. Arial, 14pt)
  • Users with auditory impairments who use captions on screen may need to personalise contrast background to distinguish the text provided.
  • Users with colour vision deficiencies may need symbols alongside colours to distinguish between different information.
  • Users with low vision may need a higher contrast to distinguish information in the foreground from the background.

 

Recommendation code: 7
source UIL

Welcome screens are often overlooked, despite being the first hook to catch users’ attention. The service provided should be fast recognised, clearly stated and navigation facilitated by labels and tips. Especially in first screens, information overload should be avoided thus it is important to provide direct access to the few features needed to easily access the service.

Recommendation code: 11
source UIL

Offer users the possibility to rate and review your application in terms of accessibility, as a transparent and open app-rating area and ensure to address them/solve the issues that may emerge. Consider it an opportunity for further improvement.
Be honest about your limits and offer users explanations concerning the accessibility limits of your services either through the FAQ section, in a dedicated area or whenever answering to comments.

 

Recommendation code: 22
source UIL

A full and easy access to your Privacy Policy, Terms of Use and Personal Data Treatment information should be provided to all users, especially vulnerable-to-exclusion users, mitigating readability issues through easy-to-read texts, visual explanations and simplified navigation across contents (text blocks, sections).

Recommendation code: 23
source UDM
  • Digital applications need to be modified or enhanced often and their longevity is limited. Consider splitting contents (such as tutorials) in smaller parts, adding titles and focusing on the main features, to increase accessibility and longevity of your application with a limited investment. Also, adjusting some of the content provided to users will have an effect on their choices, this can push them towards specific (sustainable) options.
  • Show relevant information early and ensure it is clearly identifiable (e.g. shown in bigger size and outstanding position)

 

Recommendation code: 27