Platform
With Avaya's globe spanning customer base, we can never be certain which operating system or web browser the customer will be using. There are multiple options in both categories, and our designs need to be built to work with all combinations. Some of our products are available for use on mobile devices and smartphones. Each platform has its own limitations and idiosyncrasies that may affect the user experience.
Web
The development of web pages and web-based applications involves supporting the major platforms, including Chrome , Firefox , Edge , and Safari . Refer to each browser's development site for associated best practices.
User Interface
The visual appearance for web applications should use Neo design elements, such as components, icons and typography.
Native Elements
Applications built for the web should use Neo components and styles everywhere to ensure consistency across Avaya products.
Interactions
Interactions such as display, responsiveness, accessibility and touch targets should conform to web standards, as well as the Neo guidelines found throughout this portal.
Display and Responsive Size
Layouts need to be flexible and responsive, with scaling to match different screen sizes. Accurate proportions improve the composition and hierarchy. This ensures consistency and a common user experience across all platforms..
Accessibility
Web applications must be accessible to all users. Learn more with our accessibility guidelines.
Touch Targets
Interactive controls, such as buttons, should have a minimum 24px x 24px tappable area making them easy to see and use, and to meet WCAG specifications .
iOS
iOS is a mobile operating system created by Apple and used across their portable devices. An overview of iOS best practices can be found in Apple's Human Interface Guidelines .
User Interface
Interactions such as display, responsiveness, accessibility and touch targets should follow iOS standards as well as the Neo guidelines outlined throughout the portal.
Native Elements
Applications built for iOS should use native components wherever possible to ensure consistency across platforms, while leveraging built-in accessibility. Neo fonts, colors, and icons should be applied at the design token level where possible.
Icons
All non-system icons used by iOS applications are available on the icons page.
Interactions
Interactions such as display, responsiveness, accessibility and touch targets should follow iOS standards as well as the Neo guidelines found throughout the portal.
Display and Responsive Size
Layouts need to be flexible and responsive with scaling to match different screen sizes. Follow Apple's recommended layouts to ensure consistency across all platforms.
Gestures
Allow users to quickly and easily interact with the device using touch. Visual cues are provided in our products to indicate where a simple movement of the hand can control and trigger certain actions.
Accessibility
iOS applications must be accessible to all users. Learn more with Apple's documentation and our accessibility guidelines.
Touch Targets
Interactive controls, such as buttons, should have a minimum 48px x 48px tappable area making them easy to see and use, and to meet Apple's specifications .
Keyboard Shortcuts
Shortcuts created for an iOS or iPadOS application must not conflict with existing system shortcuts. Refer to the iPadOS page for a complete list.
Android
Android is a mobile operating system created by Google. It is used in many devices, such as phones and tablets. An overview of their best practices can be found at the Android Developers site .
User Interface
The visual appearance for Android applications should utilize a combination of native elements and Neo styling.
Native Elements
Applications built for Android should use native components wherever possible to ensure consistency across platforms, while leveraging built-in accessibility. Neo fonts, colors, and icons should be applied at the design token level where possible.
Icons
All non-system icons used by Android applications are available on the icons page.
Interactions
Interactions such as display, responsiveness, accessibility and touch targets should follow web standards, as well as the Neo guidelines found throughout the portal.
Gestures
Allow users to quickly and easily interact with the device using touch. Visual cues are provided in our products to indicate where a simple movement of the hand can control and trigger certain actions.
Display and Responsive Size
Layouts need to be flexible and responsive, with scaling to match different screen sizes. Accurate proportions improve the composition and hierarchy. This ensures consistency and a common user experience across all platforms.
Accessibility
Android applications must be accessible to all users. Learn more with Android's documentation and our accessibility guidelines.
Touch Targets
Interactive controls, such as buttons, should have a minimum 48px x 48px tappable area making them easy to see and use, and to meet Android's specifications .
Windows
Windows is a desktop operating system created by Microsoft that is used by many computer systems. You can find an overview of their best practices on the Microsoft Build site .
User Interface
The visual appearance for Windows applications should utilize a combination of native elements and Neo styling.
Native Elements
Applications built for Windows should use native components wherever possible to ensure consistency across platforms, while leveraging built-in accessibility. Neo fonts, colors, and icons should be applied at the design token level where possible.
Icons
All non-system icons used by Windows applications are available on the icons page.
Interactions
Interactions such as display, responsiveness, accessibility and touch targets should follow web standards, as well as the Neo guidelines found throughout the portal.
Keyboard Shortcuts
Shortcuts created for Windows applications must not conflict with existing browser and desktop shortcuts. Refer to the Microsoft documentation as well as Narrator , JAWS and NVDA sites for the complete list.
Display and Responsive Size
Layouts need to be flexible and responsive, with scaling to match different screen sizes. Accurate proportions improve the composition and hierarchy. This ensures consistency and a common user experience across all platforms.
Accessibility
Windows applications must be accessible to all users. Learn more with Microsoft's documentation and our accessibility guidelines.
Touch Targets
Interactive controls, such as buttons, should have a minimum 40px x 40px tappable area making them easy to see and use, and to meet Window's specifications .
Mac
MacOS is a desktop operating system created by Apple that is used on their computer systems. An overview of Apple's best practices can be found in their Human Interface Guidelines .
User Interface
The visual appearance for MacOS applications should utilize a combination of native elements and Neo styling.
Native Elements
Applications built for MacOS should use native components wherever possible to ensure consistency across platforms, while leveraging built-in accessibility. Neo should be applied at the design token level by leveraging our colors, font and icons where possible.
Icons
All non-system icons used by MacOS applications are available on the icons page.
Interactions
Interactions such as display, responsiveness, accessibility and touch targets should follow web standards, as well as the Neo guidelines found throughout the portal.
Keyboard Shortcuts
Shortcuts created for MacOS applications must not conflict with existing OS or screen reader shortcuts. Refer to the Apple keyboard shortcuts and Voiceover documentation for the complete list.
Display and Responsive Size
Layouts need to be flexible and responsive, with scaling to match different screen sizes. Accurate proportions improve the composition and hierarchy. This ensures consistency and a common user experience across all platforms.
Accessibility
MacOS applications must be accessible to all users. Learn more with Apple's documentation and our accessibility guidelines.
Touch Targets
Interactive controls, such as buttons, should have a minimum 44pt x 44pt tappable area making them easy to see and use, and to meet Apple's specifications .