UX Review: 2.25 Audit and test for bugs or issues requiring resolution #184
Description
THIS IS NOT A PROPOSAL!
Continue discussion with a due date of November 1, 2025.
Revised
2.25 Audit and test for bugs or issues requiring resolution
Regularly audit for issues or problems, running tests at regular intervals to ensure stability of the project.
Success Criterion: Regular audit
Check the codebase for bugs, identify performance issues, and account for accessibility or security problems at appropriate regular intervals, such as every month or quarter.
Success Criterion: Non-regression tests
Implement non-regression tests for all critical features.
Success Criterion: Regression tests
Incorporate regression testing into each release cycle to ensure new features do not introduce bugs or otherwise conflict with existing functionality.
Previous
I no longer have access to the previous document. Earlier version: https://w3c.github.io/sustainableweb-wsg/#display-any-variables-that-have-a-negative-impact-on-your-project
Discussion
Web Dev's Responsibility
- This one feels VERY web dev, at least without talking about user tests.
- Needs clarification. Maybe we do not need this
- Surely this would be the part of project/ product management
- I think this is general maintenance and good web management rather than UX
- Bugs = webdev and @A's job. (an aside - is QA under
- webdev in the WSG?). UX's role is test the site for usability issues (usability testing, heuristic eval etc).
- I agree this is very aweb dev.
- Important, but maybe move from UX to webdev or even product level. Potentially form it differently if there is a specifc testing process that is done during the UX design phase
Clarify how this is UX's job, or part of the UX process (UX QA)
- Need to identify and provide how UX can audit/ test, such as UX QA process, which I perform on my teams and write up the issue tickets. For example, text across browsers and devices to validate the design is as intended. Document what is not.
Comments
- The way the SC are written it certainly is more webdev-y. For UX we should compose some audit & test SC language. UX QA is a thing and we can help surface the how & why.