Skip to content

Latest commit

 

History

History
50 lines (45 loc) · 10.1 KB

File metadata and controls

50 lines (45 loc) · 10.1 KB

Games and play

40 buildable project leads for game makers and player communities. 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. accessible control input mapper: Build a input mapper for game makers and player communities working on accessible control. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  2. accessible control playtest diary: Build a playtest diary for game makers and player communities working on accessible control. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  3. accessible control accessibility checklist: Build a accessibility checklist for game makers and player communities working on accessible control. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  4. accessible control matchmaking board: Build a matchmaking board for game makers and player communities working on accessible control. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  5. accessible control progress journal: Build a progress journal for game makers and player communities working on accessible control. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  6. accessible control server-status guide: Build a server-status guide for game makers and player communities working on accessible control. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  7. accessible control moderation log: Build a moderation log for game makers and player communities working on accessible control. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  8. accessible control challenge planner: Build a challenge planner for game makers and player communities working on accessible control. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  9. player feedback input mapper: Build a input mapper for game makers and player communities working on player feedback. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  10. player feedback playtest diary: Build a playtest diary for game makers and player communities working on player feedback. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  11. player feedback accessibility checklist: Build a accessibility checklist for game makers and player communities working on player feedback. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  12. player feedback matchmaking board: Build a matchmaking board for game makers and player communities working on player feedback. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  13. player feedback progress journal: Build a progress journal for game makers and player communities working on player feedback. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  14. player feedback server-status guide: Build a server-status guide for game makers and player communities working on player feedback. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  15. player feedback moderation log: Build a moderation log for game makers and player communities working on player feedback. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  16. player feedback challenge planner: Build a challenge planner for game makers and player communities working on player feedback. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  17. community event input mapper: Build a input mapper for game makers and player communities working on community event. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  18. community event playtest diary: Build a playtest diary for game makers and player communities working on community event. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  19. community event accessibility checklist: Build a accessibility checklist for game makers and player communities working on community event. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  20. community event matchmaking board: Build a matchmaking board for game makers and player communities working on community event. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  21. community event progress journal: Build a progress journal for game makers and player communities working on community event. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  22. community event server-status guide: Build a server-status guide for game makers and player communities working on community event. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  23. community event moderation log: Build a moderation log for game makers and player communities working on community event. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  24. community event challenge planner: Build a challenge planner for game makers and player communities working on community event. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  25. game tutorial input mapper: Build a input mapper for game makers and player communities working on game tutorial. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  26. game tutorial playtest diary: Build a playtest diary for game makers and player communities working on game tutorial. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  27. game tutorial accessibility checklist: Build a accessibility checklist for game makers and player communities working on game tutorial. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  28. game tutorial matchmaking board: Build a matchmaking board for game makers and player communities working on game tutorial. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  29. game tutorial progress journal: Build a progress journal for game makers and player communities working on game tutorial. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  30. game tutorial server-status guide: Build a server-status guide for game makers and player communities working on game tutorial. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  31. game tutorial moderation log: Build a moderation log for game makers and player communities working on game tutorial. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  32. game tutorial challenge planner: Build a challenge planner for game makers and player communities working on game tutorial. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  33. mod compatibility input mapper: Build a input mapper for game makers and player communities working on mod compatibility. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  34. mod compatibility playtest diary: Build a playtest diary for game makers and player communities working on mod compatibility. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  35. mod compatibility accessibility checklist: Build a accessibility checklist for game makers and player communities working on mod compatibility. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  36. mod compatibility matchmaking board: Build a matchmaking board for game makers and player communities working on mod compatibility. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  37. mod compatibility progress journal: Build a progress journal for game makers and player communities working on mod compatibility. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  38. mod compatibility server-status guide: Build a server-status guide for game makers and player communities working on mod compatibility. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  39. mod compatibility moderation log: Build a moderation log for game makers and player communities working on mod compatibility. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  40. mod compatibility challenge planner: Build a challenge planner for game makers and player communities working on mod compatibility. 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.