- Erste Schritte
- Projektmanagement
- Dokumente
- Arbeiten mit der Analyse der Änderungsauswirkungen
- Importieren von Orchestrator-Testsätzen
- Creating test sets
- Hinzufügen von Testfällen zu einem Testsatz
- Zuweisen von Standardbenutzern in der Testsatzausführung
- Aktivieren der Aktivitätsabdeckung
- Konfigurieren von Testsätzen für bestimmte Ausführungsordner und Roboter
- Überschreiben von Parametern
- Klonen von Testsätzen
- Exportieren von Testsätzen
- Linking Orchestrator test sets
- Anwenden von Filtern und Ansichten
- Ausführen von manuellen Tests
- Ausführen automatisierter Tests
- Ausführen von Testfällen ohne Testsatz
- Ausführen gemischter Tests
- Erstellen von ausstehenden Ausführungen
- Erzwingen einer Ausführungsreihenfolge
- Erneutes Ausführen von Testausführungen
- Planen von Ausführungen
- Fehlerbehebung bei automatisierten Ausführungen
- FAQ – Funktion – Test Manager vs Orchestrator
- Accessibility testing for Test Cloud
- Projektvorgänge und Dienstprogramme
- Test Manager-Einstellungen
- ALM Tool-Integration
- API-Integration
- Fehlersuche und ‑behebung

Test Manager-Benutzerhandbuch
Accessibility testing enables teams to continuously test and validate accessibility conformance of webpages throughout development and release cycles — ensuring digital inclusion, reducing risk, and enabling faster remediation of issues.
Studio Desktop 2025.10.4or higher.UI Automation Activities 25.10.26or higher (which includes the Accessibility Check activity).- Test Manager delivered through Test Cloud.
- Permissions enabled for users who generate the Accessibility Testing report:
TestExecution.Edit,TestExecution.Create. - Permissions enabled for users who view the Accessibility Testing report:
TestExecution.Read.
- Ensure the
UI Automation Activitiespackage (25.10.26 or higher) is installed and enabled in your Studio instance (2025.10.4 or higher). - Create a Studio automation project which aims at testing whether a webpage meets accessibility requirements. As part of the Studio project, configure a workflow which includes the Accessibility Check activity.
- Integrate your Studio project with your Test Manager instance.
- Run the project/automation in Test Manager.
- Check the accessibility report in Test Manager.
Accessibility testing automates the process of checking web applications (direct URLs) for compliance with WCAG 2.1 standard (or higher), with emphasis on levels A and AA.
Users can add text-based prompts to define business, UX, or accessibility rules (“Ensure all CTA buttons user alt text aligned with brand tone.”).
Accessibility testing covers, but is not limited to the following checks:
- Analyze
DOMand visual accessibility. - Check for contrast ratio.
- Check for missing
ALTtags. - Check the tab order.
- Check for improper
ARIAroles. - Highlight problem UI areas on screen using overlays or bounding boxes.
- Is automatically uploaded to the related test case and is linked to test executions. Users receive a notification after the upload operation completes.
- Can be consulted in the Reports tab of a test case execution.
The Accessibility Testing report does not show a Pass/Fail indicator. However, when including a Verify activity in the workflow, after the Accessibility Check activity, you can specify the criteria for Pass/Fail, and consult the result in the output of the Verify activity.
- A summary of statistics (total issues grouped by severity and rule).
- A snapshot of the analysis by rule ID, tag or page.
- The page title and metadata.
- A detailed middle section including: list of issues (based on the broken rule), color coding of issues based on severity, a remedy suggestion of each issue.
- Go to the Execution tab and select an execution.
- Select a test case, and from the Reports tab, consult the Accessibility Testing report.
- Total issue: pie chart distributed by severity (Critical, Serious, Moderate, Minor)
- Issue impact by: horizontal bar chart filtered by Rule ID, Page or Tag
- All Issues: multi-select table with expandable details for each issue, which can be filtered by Impact, Rule ID, Tag, or Page.
Figure 1. Accessibility Testing report - issue details