We are committed to the accessibility of our web-products and seek compliance with the Web Content Accessibility Guidelines. We currently support the most recent version 2.1 on conformance target Level A.
This accessibility statement applies to:
Our configuration portal
Configuration portal for Bastion 365 with limited access to designated administrators and support users.
Our user’s personal portal
Portal for users to send messages and monitor message status.
Our MFA portal
Portal for external users to pick up messages after multi-factor authentication
The portals accessibility is guaranteed with Edge, Chrome, Firefox and Safari.
Information and user interface components must be presentable to users in ways they can perceive
- All non-text content presented to the user has a text alternative
- Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
- A correct reading sequence can be programmatically determined.
- Instructions provided for understanding and operating content do not rely on components such as shape, color, size, visual location, orientation, or sound
- Color is not used as the only visual means of conveying information.
- All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
- Site can be navigated back and forth with keyboard operations.
- Web pages do not contain anything that flashes.
- Web pages have titles that describe topic or purpose.
- The navigation sequence does not affect meaning or operation.
- The purpose of each link can be determined from the link text alone.
- For user interface components with labels that include text or images of text, the name contains the text that is presented visually.
- When motion is used as an UI element, the motion is essential for the function.
Information and the operation of user interface must be understandable.
- Website recognizes browser language settings and user can switch language.
- Focus on an UI component does not initiate change of context.
- Input errors are automatically detected and described to the user in text.
- Instructions are directly provided in almost all pages in the portal.
Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.
- In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and IDs are unique.
- The name and role can be programmatically determined for all user interface components.
Areas for improvement
- It is not possible to bypass blocks. While this doesn’t significantly impair the user, it is recommended to fix this on pages where it is relevant.
- Tenants can largely design their own MFA portal, we do not check the WCAG 2.1 compatibility for the end-result.
If you experience any accessibility issues, please contact our customer service or via firstname.lastname@example.org