Declaration of Conformity Accessibility
Last update: 27-08-2024
Introduction
This documentation records the declaration of conformity of Versio.io with the Web Content Accessibility Guidelines (WCAG), published by the Web Accessibility Initiative (WAI) of the W3C. WCAG 2.1 provides guidelines to make web content more accessible for people with disabilities.
Target groups & limitation
The user interface of the Versio.io platform takes into account usability requirements for ... - People with visual impairments (e.g. through screen reader use). - People with motor or cognitive impairments. - Users with color vision deficiency or other perceptual impairments.
Conformity is established specifically for areas in the application that are mainly used in work processes by people with disabilities. This is comparable to the use of the Versio.io user interface on mobile devices.
WCAG conformance level
Versio.io strives for conformance level AA according to WCAG 2.1. This level guarantees a high degree of accessibility and takes into account the essential needs of Versio.io's target groups.
Technical measures
Versio.io implements the following measures as part of the software development process in order to comply with the WCAG guidelines:
Perceivability
1. text alternatives
- All images and icons are underlaid with meaningful alternative texts (alt attributes).
- Results of rule-based violations are provided in an additional text form.
2. Distinguishable colors
- The contrast between text and background is at least 4.5:1.
- Colors for specific representations (e.g. new, changed or deleted content) can be individually adjusted in the settings of each client-oriented Versio.io environment.
3. Scalability
- The web-based user interface can be enlarged by up to 500% using the zoom function provided by the browser (see support for mobile devices).
Usability
1. keyboard accessibility
- Basic navigation functions are accessible via keyboard (see hotkey support Navigation).
2. focus indicators
- The active element in input masks is clearly highlighted by a focus indicator.
3. navigation aids
- The navigation framework always gives the user the opportunity to recognize the current navigation path of the user and enables new navigation steps.
- The individual elements of the navigation framework can be targeted with hotkeys (see Navigation).
- By supporting deep links, subordinate points in the navigation including default settings can be accessed directly (e.g. calling up a specific content view including all filter configurations).
Comprehensibility
1. readable content
- All content is formulated in clear, simple language.
- Each content page consists of ...
- a breadcrumb
- a heading
- a short explanatory text
- Für komplexe, visualisierte Regelbäume im Policy Monitoring werden Zusammenfassungen in minimaler Textform erstellt.
2. Vorhersehbare Navigation
- Navigation and interactions are consistently designed and based on a Versio.io internal guideline for the Versio.io user interface.
- The Versio.io interface provides a continuously available framework to guide the user in terms of content. For the framework, hotkeys are supported for simplified keyboard control. These include:
| Element | Hotkey | Note |
|---|---|---|
| Home | h (home) |
By clicking on the icon in the header, the user can return to the initial start page from any position in the Versio.io application. |
| Main menu | m (menu) |
There is a menu on the left-hand side to select the different function areas. |
| Breadcrump | - | For all useful content pages, there is a breadcrumb display under the header, which gives the user an orientation to their navigation path. |
| Fulltext search | f (find) |
A full-text search of the inventoried assets and configuration items is available in the header. The search can be used from any position in the Versio.io application. |
| User menu | u (user) |
The user menu is located in the top right-hand corner. Here the user can change their personal settings, change the active environments and find helpful links in the context of their user role (e.g. release notes). |
| Questions & feedback | i (incident) |
In addition to the user menu, it is also possible to ask the Versio.io team any open questions and provide feedback on the Versio.io product. |
- The context-related meaning of actions in the form of buttons on content pages is facilitated by means of color and contrast display:
| Color design of the buttons | Meaning |
|---|---|
| Blue colored button | The user's focus should be directed to this action. The button represents an important and frequently used action in the context of the page. |
| Blue bordered button | The button represents an action that is rarely used in the context of the page. |
| Red colored button | The user's focus should be directed to this action and at the same time warned against using it. The button represents an action that is important and frequently used in the context of the page, but which is usually irreversible (e.g. delete function). |
| Red bordered button | The button represents an action which is usually not reversible (e.g. delete function). |
Robustness
1. compatibility with assistive technologies
- The user interface code conforms to the standard and is continuously tested.
- The following tools are used for testing:
- Windows 11 integrated speech output (screen readers)
- Chrome browser content translation (Google Translate)
- Lighthouse (quality check of websites)
Test procedure
The accessibility of Versio.io is regularly checked using the following methods:
- Automated tests
- Manual tests
- User feedback
Restrictions and feedback
We are aware that not all requirements can be met in every situation. If you encounter a usability problem in your practical work with Versio.io or have suggestions for improvement, please contact us at: service@versio.io.
Future improvements
Versio.io is continuously working to improve accessibility. Planned measures include:
- Internal training on accessible software for our development team.
- Optimization of screen reader compatibility for dedicated use cases.
- Involvement of customer employees with disabilities in optimizing the user interface.
- Requesting feedback from customers on accessibility and incorporating it into the product roadmap as a feature requirement.
- AI-generated summaries, e.g. for a host instance or a description of a violation.
Conclusion
Versio.io strives to provide an accessible platform that includes all users. This documentation is updated annually to reflect progress and new developments.