Hi
How do you expect screenreader users to understand which price is active on this? A checkbox implies an on/off state. It’s ideal for yes/no answers or on/off toggles. It’s not really ideal for a switch like this that has has two distinct and labelled states - how would I know whether checked means monthly or annual? It’s very unclear. In these cases it is always better to use radio inputs.
The other issues I see with this are
- again screenreader content order and content change announcement. I think some aria-live attributes are needed, or even a screenreader specific message
- header always goes outside of main, not within it. It is it’s own landmark
- similar this should not have an article within it, or sections. It’s all one related piece of content
- if using a button to submit the chosen options this should all be a form.
Marked as helpful