What kinds of errors do you usually spot? A spelling mistake or off-brand product name? A slow page, an inaccessible feature, or a widget that’s awkward to use? Syntax errors or deprecated functions?
Everyone on a project notices quality issues—but not everyone feels equipped to fix them. Many teams already run checks such as code linting, copy editing, or accessibility reviews. But do these checks surface problems too late, competing with higher priorities? As preview environments and continuous integration become more common, you might realize you could use tools to catch errors sooner—but feel lost in a sea of jargon and complexity.
This session reframes QA as a shared responsibility that spans every role and stage of web development feature delivery. We’ll map the modern QA landscape and explore lightweight testing and preview tools anyone can use—from content editors to frontend and backend developers—to identify issues sooner and communicate them clearly.
Then we’ll see those ideas in action. The slides for this presentation will be hosted in a GitHub Pull Request and deployed through a Tugboat preview environment. Together, we’ll identify a late-detected error, propose a fix, commit it live, and watch the preview rebuild in real-time—demonstrating how an accessible, collaborative QA process can work.
Finally, we’ll examine how a local check could have identified the problem before the Pull Request was even opened, illustrating how you can continually learn from feedback and enhance your quality-assurance processes.
Attendees will leave with:
- A clear mental model of the QA landscape across roles
- Examples of small, approachable tools for checking quality locally or in CI/CD
- Practical ideas for building a QA process that both “shifts left” and shares responsibility
