Autoplay audio labels on page flip
- Dominant language
- TypeScript
- Stars
- 38
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Blocked by https://github.com/getodk/web-forms/issues/254
### Description
Implement support for the `autoplay` column so that audio or video media attached to a question automatically plays when the question becomes visible (after pagination/page transition).
[Specs](https://docs.getodk.org/form-styling/#autoplaying-media)
---
### Checklist
- **Does it need UI/UX design?**
- [ ] Yes. Describe the UI/UX requirements or attach a Figma link in the "Design" section.
- [x] No
- **Does it need API design?**
- [x] Yes. Specify the endpoints, methods, or data structures needed.
- [ ] No
- **Does it need design around state flow?**
- [ ] Yes. Outline the state flow requirements.
- [x] No
- **Does it need a test plan?**
- [x] Yes. Add the test plan as a comment in this task or attach the document.
- [ ] No
---
### User Stories
As a form designer / enumerator,
I want audio and video media to play automatically when a question appears (like in ODK Collect),
So that respondents don't have to manually press play, improving usability and reducing errors in guided interviews.
---
### Design
- **Figma**: [Insert URL]
- **Design Docs**: [Insert URL]
---
### Dependencies
- Pagination / question navigation must be implemented
- https://github.com/getodk/web-forms/issues/608
- https://github.com/getodk/web-forms/issues/607
-
---
### Additional Notes
-
---
### Related Issues
-
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the blocker #254 and dependencies #608 and #607, then read the linked ODK autoplay specification. Confirm the pagination and question-navigation behavior before implementing automatic playback for media when a question becomes visible, with tests covering page transitions and the documented autoplay cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- audio-video-rtc, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100