Giacomo Petri

@dd8, I believe we've covered all the points discussed. We've received 4 approvals, but I'd appreciate your final review, especially considering your previous concerns with the earlier version. Thanks

Call for review ends on May 8th

I'll address this with a PR, first making sure that browsers expose consistently the same title.

Outcomes of my test: | Scenario | Chrome | Safari | Firefox | | --- | --- | --- | --- | | 2 titles, both in `` | The...

Should we contemplate including it in the rule template as well? Otherwise, there's a chance we might overlook this aspect when creating new rules. Alternatively, we could explore the option...

How about incorporating a feature akin to the aria-valuetext attribute available in the progressbar role? If supported by both browsers and assistive technologies, this enhancement could expose the element as...

@MarioBatusic, as per specifications, the aria-checked attribute is mandatory. In the context highlighted by Scott, the attribute is consistently checked, given that the switch button doesn't toggle a function on...

After some thoughts, do we really need the switch role at all? Imagine, for a moment, that an element designated with the switch role not only responds to the spacebar...

Disregard the previous feedback as it is inaccurate. Screen reader users may inadvertently interact with the "already selected" radio button, leading to an unintended activation of the "unselected" option.

While working on an initial draft to implement the discussed idea, I noticed that the aria-valuetext attribute, as it currently stands, is overly tailored for range widgets. Thus, there are...