Comprehensive test management solution for complex challenges.
Missed it? The accessibility webinar recording is now online
Missed our live webinar "Digital Accessibility with andagon"? No worries – the recording, featuring the live demo and Q&A session, is now available. Immanuel Georgius, ISTQB®-certified software tester and Accessibility Specialist at andagon, walks through a professional accessibility test step by step, live on a real website.
Part 1: Automated quick-scan with WAVE
The demo starts with WAVE, a browser tool that automatically flags common violations. Immediately visible: a missing or non-informative page title that leaves screen reader users hearing only the raw URL, along with several "empty links" – buttons with no link text, so nobody knows where a click leads. On top of that come classic contrast errors, such as white text on a blue background in the main menu with a contrast ratio of just 3.3:1, well below the required minimum.
The key takeaway straight from the demo: automated tools like WAVE only catch around 30–50% of WCAG issues. Everything else can only be found through manual visual and functional testing.
Part 2: Manual testing with concrete test cases
In the second part of the demo, Immanuel runs through real WCAG test cases in andagon's in-house ALM tool:
• 1.4.1 – Use of Color (Level A): A carousel link "More info!" [dt. “Mehr Infos!”] is marked as clickable using color alone – no underline, icon, or bold text. For anyone who can't distinguish colors, this call-to-action is effectively invisible.
• 1.4.10 – Reflow (Level AA): During the reflow test at 400% zoom, the phone number and icons in the header disappear entirely – information is lost even though the page looks like it’s still working at first glance.
• 2.4.7 – Focus Visible (Level AA): While tabbing through the lower page clearly highlights the focus with color, that indicator vanishes completely in the top navigation bar – the only clue is the URL shown in the bottom-right corner of the browser, which is practically unusable for keyboard-only users.
• 3.3.2 – Labels or Instructions (Level A): In the contact form, a field’s label (e.g. “First name”) disappears the moment you start typing – a common but serious error.
• 4.1.2 – Name, Role, Value (Level A): The screen reader’s link list reveals several more “unlabeled links” – a violation of the “Name, Role, Value” requirement, which mandates a clear mapping between an element, its function, and its state.
The demo wraps up with an automatically generated audit report covering the legal basis, tools used, testing methodology, and sorted findings – plus a tailored accessibility statement that companies can embed directly on their website.
Part 3: How andagon can help
After the demo, Vera Kopistecki outlines andagon's service offering: an Accessibility Assessment (automated scans plus manual expert testing with screen reader and keyboard, findings prioritized by severity), support during implementation (fix reviews, retesting, drafting the accessibility statement), and ongoing assurance through accessibility checks in CI/CD, training for development, design, and content teams, and recurring audits after releases.
Part 4: Questions from the audience
The Q&A covers practical topics raised by attendees:
• Automating "name, role, value" checks: Where a programmatically recognizable structure exists (e.g. labels built with native HTML elements), this check can be automated. Where labels aren't generated through native HTML, keyboard control, labeling, and mapping all need to be verified manually.
• Scaling to multiple websites and workflows: For something like 98 BITV test steps applied across several processes or websites, Immanuel recommends building test cases separately per site by default, while reusing shared modules to cover page- and feature-specific changes precisely.
• Accessibility and AI: The better a website's programmatic accessibility is implemented, the more accessible it also becomes to AI systems, which rely on the same structural information to navigate.
Watch now and see for yourself how many barriers can hide behind a seemingly "good" website.