Principles

The global marketplace is evolving and the transition toward customer centric products is the most striking change. An important change is the realization corporations must start making software products that are accessible.

Accessibility means making Avaya’s products and services available to the greatest number of customers. People with visual, hearing, physical, or cognitive impairments must be able to easily use our software. People who fear that they won’t be able to use a product will not buy it.

Avaya believes that our software and hardware solutions should be accessible to everyone. Neo is committed to following and complying with industry best practices and regulations.

• Neo and Accessibility
• Standards and Regulations
• Types of Disabilities

In addition to helping users with disabilities, accessible design helps provide better user experiences for everyone. A text description included in an image makes its content available to a user who is blind, and makes it possible for search engines to index the image.

Using Neo components improves accessibility and consistency when building UX/UI solutions. However, the way Neo is used can affect the accessibility of the application. Be sure to include testing in the design and development process to avoid any accessibility barriers and delays due to fixing the problems before release.

Neo targets Web Content Accessibility Guidelines (WCAG) 2.2 AA (used in many government regulations internationally), as well as Section 508 regulations. More information can be found here.

• WCAG 2.2
• ARIA 1.1
• Section 508

To understand the accessibility barriers to users, it is helpful to be aware of the range of disabilities that exist. Each group faces defferent challenges that need to be resolved. Including these considerations in the design and development process creates a better user experience for everyone.

Blind

Blindness refers to a large range of visual disabilities, from impairments that interfere with completing tasks, to total blindness. Blind users interact with interfaces by using screen readers, refreshable braille displays, and other assistive technologies.

Things to consider:

• Visual information should be also provided in text format (e.g. alt text).
• Functional elements should be controllable with a keyboard.
• Content should be structured and simplified where possible.
• Time limits should provide sufficient time or be extendable.
• Video should include audio narration.
• Test all designs with a screen reader where possible.

These considerations will also help others as audio interfaces, such as Siri and Alexa, are increasingly popular for assisting with tasks.

Low Vision

Low Vision refers to issues with one or both eyes. Users are still able to view content with assistive technology. They interact with an interface by using screen magnification tools, high contrast modes, monochrome displays, or screen readers.

Things to consider:

• Maximize readability and visual clarity of content.
• Consider how the proximity of information changes when a page is magnified.
• Time limits should provide sufficient time or be extendable.
• Test all designs with a screen reader where possible.
• Test with color contrast tools or color simulators to ensure sufficient contrast.

These considerations will also help other users, including those in poor lighting conditions, or other environments where they may experience similar difficulties.

Color Blindness

Color blindness refers to an inability to see all colors. There are three main forms of color blindness: red-green, blue-yellow, and total color blindness. These users interact with an interface by relying on non-color information to complete tasks, and may use adjusted display settings or color filters to compensate.

Things to consider:

• Ensure information is not conveyed with color alone.
• Test with color contrast tools or color simulators to ensure sufficient contrast.

These considerations will also help other users, including those in poor lighting conditions, or other environments where they may experience similar difficulties.

Deaf and Hard of Hearing

Deaf and hard of hearing users face a complete or partial reduction in their ability to hear sound. These users interact with a UI by using hearing aids, or use captioning and other alternative representations of audio content.

Things to consider:

• Ensure information is not conveyed with sound alone.
• Transcribe and caption videos and multimedia elements.

These considerations will also help others, including those in loud environments where they may experience similar difficulties if they cannot hear audio, or quiet environments where they cannot play audio.

Cognitive Disabilities

Cognitive disabilities refer to a range of mental impairments including memory, problem solving, attention, reading, verbal, math and visual comprehension. These users interact with interfaces by relying on information remaining visible while completing tasks.

Things to consider:

• Ensure language is simple and clear.
• Ensure content is structured.
• Avoid uncontrollable and flashing animations.
• Avoid visual clutter.
• Offload tasks when possible (e.g. by showing previously entered info to avoid recall).
• Ensure quick response times so users don't lose track of their tasks.

These considerations will also help others, including those in busy environments who may experience heavier cognitive loads.

Physical Disabilities

Physical disabilities refer to impairments of mobility, dexterity or control. These users interact with interfaces using keyboards, track balls, voice recognition, or other assistive technologies.

Things to consider:

• Functional elements should be controllable with a keyboard.
• Ensure clickable regions have sufficient target space.

These considerations can also help others since keyboard navigation and shortcuts are frequently used to perform tasks quickly.