Evidence
Scored against issues planted in OpenClass, a demo class app, plus decoys that look wrong but are correct.
PR-1
Fixes proven by a test that fails before and passes after: 23 of 23.Missed by CurbCut: P1-11, P1-15.Findings matching no planted issue: 6 of 23. Some are real issues that were not planted; they are listed in the results file, not counted as correct.
PR-1-RUN2
Missed by CurbCut: P1-11, P1-12, P1-14, P1-15.Findings matching no planted issue: 5 of 21. Some are real issues that were not planted; they are listed in the results file, not counted as correct.
PR-2
Missed by CurbCut: P2-05, P2-10.Findings matching no planted issue: 1 of 16. Some are real issues that were not planted; they are listed in the results file, not counted as correct.
Limits of this benchmark
- Two runs on PR-1 found 16 and 14 issues. Differences of this size are run-to-run variation in IBM Bob's judgment, not an improvement.
- The issues were planted by the same team that built CurbCut.
- A finding counts only if it points at the same element with an accepted success criterion.
- Rerun it:
uv run --project codes/engine python scripts/benchmark/score.py pr-1
What CurbCut does not check
- It does not certify WCAG conformance. Testing with disabled people cannot be replaced.
- It does not judge real screen reader experience, cognitive load, or caption quality.
- Flagged findings are IBM Bob's judgment and can be wrong.
- Benchmark numbers come from a demo app with planted issues. Other code bases may differ.