README.md

Accessibility

40 buildable project leads for design, content, and product teams. The research signal for this category is W3C WAI. Each lead needs independent source checking and an existing-solution review before it becomes a full entry.

Ideas

1. keyboard journey test recorder: Build a test recorder for design, content, and product teams working on keyboard journey. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
2. keyboard journey review queue: Build a review queue for design, content, and product teams working on keyboard journey. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
3. keyboard journey focus visualizer: Build a focus visualizer for design, content, and product teams working on keyboard journey. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
4. keyboard journey acceptance checklist: Build a acceptance checklist for design, content, and product teams working on keyboard journey. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
5. keyboard journey issue library: Build a issue library for design, content, and product teams working on keyboard journey. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
6. keyboard journey handoff sheet: Build a handoff sheet for design, content, and product teams working on keyboard journey. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
7. keyboard journey compatibility matrix: Build a compatibility matrix for design, content, and product teams working on keyboard journey. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
8. keyboard journey regression report: Build a regression report for design, content, and product teams working on keyboard journey. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
9. screen-reader flow test recorder: Build a test recorder for design, content, and product teams working on screen-reader flow. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
10. screen-reader flow review queue: Build a review queue for design, content, and product teams working on screen-reader flow. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
11. screen-reader flow focus visualizer: Build a focus visualizer for design, content, and product teams working on screen-reader flow. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
12. screen-reader flow acceptance checklist: Build a acceptance checklist for design, content, and product teams working on screen-reader flow. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
13. screen-reader flow issue library: Build a issue library for design, content, and product teams working on screen-reader flow. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
14. screen-reader flow handoff sheet: Build a handoff sheet for design, content, and product teams working on screen-reader flow. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
15. screen-reader flow compatibility matrix: Build a compatibility matrix for design, content, and product teams working on screen-reader flow. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
16. screen-reader flow regression report: Build a regression report for design, content, and product teams working on screen-reader flow. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
17. accessible form test recorder: Build a test recorder for design, content, and product teams working on accessible form. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
18. accessible form review queue: Build a review queue for design, content, and product teams working on accessible form. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
19. accessible form focus visualizer: Build a focus visualizer for design, content, and product teams working on accessible form. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
20. accessible form acceptance checklist: Build a acceptance checklist for design, content, and product teams working on accessible form. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
21. accessible form issue library: Build a issue library for design, content, and product teams working on accessible form. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
22. accessible form handoff sheet: Build a handoff sheet for design, content, and product teams working on accessible form. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
23. accessible form compatibility matrix: Build a compatibility matrix for design, content, and product teams working on accessible form. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
24. accessible form regression report: Build a regression report for design, content, and product teams working on accessible form. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
25. caption review test recorder: Build a test recorder for design, content, and product teams working on caption review. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
26. caption review review queue: Build a review queue for design, content, and product teams working on caption review. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
27. caption review focus visualizer: Build a focus visualizer for design, content, and product teams working on caption review. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
28. caption review acceptance checklist: Build a acceptance checklist for design, content, and product teams working on caption review. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
29. caption review issue library: Build a issue library for design, content, and product teams working on caption review. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
30. caption review handoff sheet: Build a handoff sheet for design, content, and product teams working on caption review. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
31. caption review compatibility matrix: Build a compatibility matrix for design, content, and product teams working on caption review. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
32. caption review regression report: Build a regression report for design, content, and product teams working on caption review. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
33. document remediation test recorder: Build a test recorder for design, content, and product teams working on document remediation. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
34. document remediation review queue: Build a review queue for design, content, and product teams working on document remediation. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
35. document remediation focus visualizer: Build a focus visualizer for design, content, and product teams working on document remediation. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
36. document remediation acceptance checklist: Build a acceptance checklist for design, content, and product teams working on document remediation. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
37. document remediation issue library: Build a issue library for design, content, and product teams working on document remediation. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
38. document remediation handoff sheet: Build a handoff sheet for design, content, and product teams working on document remediation. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
39. document remediation compatibility matrix: Build a compatibility matrix for design, content, and product teams working on document remediation. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
40. document remediation regression report: Build a regression report for design, content, and product teams working on document remediation. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.

Turn a lead into a project

Use the repository project template. Document the problem, users, existing approaches, material gap, first version, and sources before submitting a pull request.