Re: [w3ctag/design-reviews] Beforematch event and content-visibility: hidden-matchable (#511)

Thanks for the review!


> One important question that came up during the review is whether we have verified that this new way of making content hidden is handled correctly per the Name Computation algorithm. Since this feature makes content hidden our expectation is that the behavior will be similar to that of diaplay:none and we ask that you consider adding a WPT test to cover that scenario.
>
> Specifically, that an aria-labelledby or aria-describedby attribute which refers to an element within a content-visibility: hidden, content-visibility: auto or content-visibility: hidden-matchable block will correctly expose the text of the element as contributing to the name/description of the referring element:
> ```
> <input aria-labelledby="a-label">
> <div style="content-visibility: hidden-matchable">
>   <span id="a-label">This should be the label of the above input</span>
> </div>
> ```

Thanks for the suggestion! I tested out the current implementation in chromium and it works with Mac VoiceOver. I am writing a test [here](https://chromium-review.googlesource.com/c/chromium/src/+/2657063), but unfortunately I don't think there is currently a way to get the appropriate accessibility information in WPT - the test I made uses chromium-specific testing features. I filed a bug on WPT about it [here](https://github.com/web-platform-tests/wpt/issues/27374).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/511#issuecomment-769374038

Received on Thursday, 28 January 2021 20:40:38 UTC