The following content is an automated AI translation from the German version.
In this article, you will find the current status of the accessibility of the current version of the incert e-commerce system based on relevant criteria. Please note that your version depends on the implementation date (or last relaunch) and that accessibility also depends on other factors.
You will also find details about our Accessibility Audit, which you can order for your system. To request accessibility improvements and a subsequent audit, please follow this procedure.
Audit & Approval
Overview
As part of a standard audit, we confirm the fulfillment of the technical aspects (template) and style adjustments. If any adjustments are requested that lead to non-compliance, we will note this. We have also prepared general information about accessibility and the procedure here.
The standard accessibility audit includes:
| Scope | Criteria & Test | Confirmation & Approval |
|
|
Not included is the review or assessment of other tests (e.g., if you conduct your own tests). Additional time can be booked for this purpose, but we note that standard tools often produce false positives. Also, a report on individual criteria of your system is not included. The confirmation is provided in the scope and form defined by incert. If you are interested in a point excluded from the standard audit, please contact us at sales@incert.at
Tools and Services
We use a range of established external services to check the accessibility of the system in its standard version. At go-live or relaunch, your system (including any custom or style adjustments) is additionally tested using axe-core test. If you want to test all or specific pages of your incert system yourself, we recommend Google Lighthouse.
| Use | Details | |
|
axe-core (Deque Systems Inc.) |
For checking the incert template. For checking your incert implementation (including style and custom adjustments) |
Used for static markup audits. The incert template meets all relevant criteria (see list) 100% with this tool. |
|
Lighthouse (Google) |
For checking the incert template. Recommended if you want to test your incert system’s accessibility yourself. |
Used as an additional validation of the audits. The incert template meets all relevant criteria (see list) 100% with this tool. |
| Various other tools |
For checking the incert template. For additional checks of navigation, screen reader output, structural integrity, and more. |
As analysis tools are either prone to false positives or have gaps in testing, we use a set of additional tools. If desired, we can provide an up-to-date list. |
Untested Elements
The following elements are currently not tested for accessibility:
- Vouchers or tickets as well as the purchase receipt (or invoice) in PDF format
- Emails sent by the system (optimization is in progress)
- (all non-incert provided elements such as the integration page, integration, payment windows of the payment service provider, externally integrated consent managers, embedding of Google Maps for partner location maps, etc.)
Accessibility Criteria
This list only contains elements that are relevant for objects and processes in the incert system and required for AA status. Our tests are therefore explicitly limited to these elements. The scope of the test itself is described above. The term "yes" refers to the result of our tests within the specified scope.
The list of fulfilled criteria explicitly refers to the incert system in standard configuration and current version. Whether your system can also be rated "yes" according to these criteria additionally depends on system-specific style and custom adjustments and on content maintained by you.