Jean-Yves Moyen
Jean-Yves Moyen
It looks like this has been solved by #150 which added a comment to Step 2A to clarify what "hidden" means.
@scottaohara Good point. I think the underlying question of building the accessibility tree from DOM or flat tree still exists, but I agree this precise case is probably only FF...
Two points to mention: --- I'm encountering a problem similar to #1818 but the other way around, and I'm not sure this PR fully handles it 🤔 The case in...
@adampage That actually makes sense 😄 This PR seems to change the behaviour in the related simplified case: ```html Item ``` In that case, the current behaviour is to expose...
> “_Changes to ownership are resolved in DOM order. If both `aria-hidden` and `aria-owns` are specified on the same element, `aria-hidden` is processed first and `aria-owns` will not take effect._”...
Yep, poor writing on my side 🙈 and messing up things badly… ```html Child node ``` case **1 not 2** in Adam's list with `aria-hidden` replaced by `display: none`. This...
I feel there is still a small clarification needed to say that `aria-owns` breaks DOM parent/child relation in addition to create new ones (i.e. the result is indeed an accessibility...
!pr extract
Discussion during F2F meeting: WCAG is moving toward saying that transcript do not necessarily need to be visible (reason, a gif qualifies as audio-less video, and an `aria-label` (not visible)...
> Hi @Jym77, > > to be honest, it took me a while to figure out if Expectation 2 was supposed to clarify how to deal with shadow roots, but...