Thorough manual testing across the product, including with screen readers (H2)
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Tranquilla
- Stack tecnologico
- playwright, typescript
- Ambito
- accessibility, ci-cd, cli, frontend, testing
Direzione di ricerca
Complete the team orientation at usabl-dev.github.io/usabl/team-orientation.html, then use the human-tasks.md handoff catalogue entry H2 to identify the four surfaces and the hero bug and repair. Exercise the CLI, overlay, stop hook, PR and CI, onboarding path, and keyboard and screen reader interactions; record findings the automated layer missed. Done means every surface has been manually exercised and the hero bug and its repair are confirmed by ear and keyboard for v0.2.1.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
usabl issues machine verdicts on accessibility. The automated layer can miss what a real user catches, so a human has to confirm the tool itself and the fixture behave.
Some screen reader review has already been done. It was a spot check, not broad enough to sign anything off on. What v0.2.x needs is a thorough manual pass across the whole product, with assistive technology as one part of it rather than the whole task.
- Why: a narrow spot check is not evidence that the product holds up. An accessibility product that has only been tested the easy way is the exact failure it exists to catch.
- Scope: all four surfaces (CLI, overlay, stop hook, PR and CI), the hero bug and its repair, and the onboarding path. Screen reader and keyboard-only passes are part of this, not the entirety of it.
- Owner: a teammate with Orca, plus at least one person doing a keyboard-only pass.
- Acceptance: every surface has been exercised by hand; the hero bug and its repair are confirmed by ear and by keyboard, not only by the gate; and every finding the automated layer missed is recorded.
- Target: v0.2.1.
Prerequisite for every human task: complete team-orientation first (usabl-dev.github.io/usabl/team-orientation.html), so the owner shares the result model, the four surfaces, and the claim boundary.
Source: human-tasks.md handoff catalogue (H2).
- Lingua principale
- TypeScript
- Stelle
- 0
- Fork
- 0
- Merge medio
- 2h 48m
- PR unite (30g)
- 8
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di usabl-dev/usabl
-
area: engine bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
-
Stop hook allows a stop on an unknown verdict, and the self-check prints IDLE for a null verdictApertaarea: assistants bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
area: engine bug security
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Overlay: browser context failures are counted per plugin, not per browser, and close is not sharedApertaarea: overlay bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
-
area: engine enhancement performance
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Tutte le issue di usabl-dev/usabl
Issue simili
-
area: image-engine bug priority: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
snapotter-hq/SnapOtter#3885 ·
I maintainer di solito rispondono entro 1 giorno
-
Mend: dependency security vulnerability
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 3 giorni
-
pending triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
bug P3 UI/UX
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
openclaw/openclaw#182077 · 1 commento · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno