Adrian Roselli

Minutes from the deep dive: https://www.w3.org/2024/05/02-aria-dive-minutes > general consensus is that we should go forward with this

I am on board with consistency within the spec itself. Are you proposing a PR to do so? Otherwise I cannot tell from your comment what you feel the next...

Both `` and `` (media elements in HTML5) support the [`` element](https://html.spec.whatwg.org/multipage/media.html#the-track-element). As you know, the [`kind` attribute](https://html.spec.whatwg.org/multipage/media.html#attr-track-kind) allows for captions, subtitles, and audio description but not transcripts. `` points...

If you have a test case at hand, I can run at it. If you don't have a test case at hand, I can make one. And then run at...

Each of a native checkbox, an ARIA checkbox (using `aria-checked`), and an ARIA toggle button (using `aria-pressed`) are tri-state controls. All three allow a `mixed` value. The `switch` role does...

> I am able to remove the "img" role and change it to "table", do you think it would be ok even if we don't set more precise roles for...

Yes, the `radio` role does not belong there and _definitely_ cannot have any interactive content within it. If you gave the radio inputs a `presentation` role that would only have...

@SachaG > We wanted to hide them visually to avoid cluttering up the page even more. I think we chose to hide them using `opacity` and not just remove them...

> The visibility property does not allow for transitions (I'm not sure if we're using any right now, but I think that was the intent behind using `opacity`). Gotcha. >...

I am not sure there is a screen reader issue. The original bug I identified was about the nested roles, which presented in screen readers and you have since fixed....