Design: Readspeaker button

[jeroenkel]

User story

A clear and concise description of what the problem is. Eg: As an [actor], I [want|must] [action] so that [achievement].

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

Acceptance criteria

Conditions that must be satisfied to be accepted by a user, customer or other stakeholder.

Definition of Ready

To be completed before the issue can be added to backlog.

• [ ] Acceptance criteria are described
• [ ] Any preconditions are described
• [ ] Possible dependence on external experts is mentioned
• [ ] The story must be understandable for the development team
• [ ] Any requirements for accessibility are described

Definition of Done

To be completed before the issue can be marked as Done.

• [ ] Code exists on main branch
• [ ] Meets acceptance criteria
• [ ] Complies with the standard of public code
• [ ] Story has been sufficiently tested
  • [ ] 90% code coverage
  • [ ] Build completed
  • [ ] Existing tests pass
• [ ] The frontend component complies with WCAG 2.1 accessibility guidelines

[paulAcato]

@jeroenkel ,

Design is af. Echter hebben we voor ReadSpeaker credentials nodig ;-) anders mogen we van RS niets inladen.

[jeroenkel]

@paulAcato ik heb de vraag gesteld bij functioneel beheer. Wacht op antwoord. Hou je op de hoogte. Verwacht niet dat ik die vandaag nog heb.

[bddjong]

@paulAcato is this issue still relevant?

[paulAcato]

@bddjong , Sadly yes. The Readspeaker component hasn't been made jet. They postponed it to Phase 2.