---
title: "From a long list to a clear signal: baseline-driven acces..."
url: https://daily.dev/posts/from-a-long-list-to-a-clear-signal-baseline-driven-acces--elkvdr4g1
source_url: https://tech.trivago.com/post/2026-03-13-from-a-long-list-to-a-clear-signal-baseline-driven-accessibility-reporting/
type: article
source: "Tech at trivago"
published: 2026-03-16T09:57:24.681Z
updated: 2026-03-16T09:57:50.434Z
tags: ["testing", "cicd", "accessibility", "github-actions"]
reading_time: 8
upvotes: 0
comments: 0
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# From a long list to a clear signal: baseline-driven acces...

**[Tech at trivago](https://daily.dev/sources/trivago)** · 8 min read · 0 upvotes · 0 comments

## Summary

Automated accessibility tests typically produce a flat list of violations that mixes new regressions with long-standing technical debt, making it hard to act on. Trivago's engineering team extended their internal test automation framework with a baseline-driven reporting system. On every merge to main, a baseline.json snapshot is generated and stored in GCP. When a pull request is opened, the same tests run against the feature branch and results are compared to the baseline, categorizing issues as new, fixed, or persisting. New issues automatically fail the CI check and are surfaced directly in the pull request with screenshots, severity badges, and fix guidance. The fingerprinting mechanism hashes the rule ID, HTML snippet, CSS selector, and impact level to stably track violations across runs. The system is built as a plugin to the core framework for easy iteration, and falls back to a standalone snapshot report when no baseline is available. The authors note that automated tools catch only 30–50% of accessibility issues and that manual testing remains essential.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://tech.trivago.com/post/2026-03-13-from-a-long-list-to-a-clear-signal-baseline-driven-accessibility-reporting/>

## Similar posts on daily.dev

- [Building a general-purpose accessibility agent—and what we learned in the process](https://daily.dev/posts/building-a-general-purpose-accessibility-agent-and-what-we-learned-in-the-process-twpj2jghn) · GitHub Blog · 0 upvotes · 0 comments
- [What's new in Cypress Accessibility?](https://daily.dev/posts/what-s-new-in-cypress-accessibility--ujqkjjt4f) · cypress · 1 upvotes · 0 comments
- [Github Integrates AI to Improve Accessibility Issue Management and Automate Feedback Triage](https://daily.dev/posts/github-integrates-ai-to-improve-accessibility-issue-management-and-automate-feedback-triage-3vu0hjwbk) · InfoQ · 0 upvotes · 0 comments
- [Is This the Future of E2E Testing? How AI Automates Browser Tests from Plain English Requirements](https://daily.dev/posts/is-this-the-future-of-e2e-testing-how-ai-automates-browser-tests-from-plain-english-requirements-yx39zejmr) · This is Angular · 1 upvotes · 0 comments

---

Tags: [#testing](https://daily.dev/tags/testing), [#cicd](https://daily.dev/tags/cicd), [#accessibility](https://daily.dev/tags/accessibility), [#github-actions](https://daily.dev/tags/github-actions)

[View this post on daily.dev](https://daily.dev/posts/from-a-long-list-to-a-clear-signal-baseline-driven-acces--elkvdr4g1)