Thank you @tabatkins, @dizhang168 for confirming (also, that is a neat idea and inclusive approach, re the examples). One further thing that came up in APA WG's discussion (HT @AutoSponge) is: we were wondering if there may be a need (practical/implementation or otherwise) for signals from the UA to the AT when a big reflow occurs (especially thinking of the Masonry case). We are also following up with our AT vendor contacts, to see how much (if any) caching of the accessibility tree they do. If they don't need to do any, it may not be an issue, but if they do, such signals may be needed to ensure the reflowed layout is reflected. If you have any thoughts on this, do let us (or APA WG may be a good avenue—you could use the "a11y-tracker" label) know. If we find out anything interesting, we'll feed it back to you. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/978#issuecomment-2489102491 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/978/2489102491@github.com>
Received on Wednesday, 20 November 2024 16:52:48 UTC