You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #10711 we discussed how to make offscreen content not part of the focus-order or accessibility tree, however, it would be really useful if it could still be discovered by find-in-page similar to hidden=until-found such that it could be found and scrolled on screen which would subsequently make it interactive in the case of scrolling content where the visible page is interactive.
The text was updated successfully, but these errors were encountered:
Yes, I've made scrollable demo's of a list of content. Just because some of the content is off screen, doesn't mean I want it hidden from search or assistive technology. It really just means I want it out of the focus order.
interactivity: disabled; ??
With a keyword like disabled, we're disabling the interaction potential of this element but not giving up the ability to be found in the tree.
or assistive technology. It really just means I want it out of the focus order.
On this I think I disagree. I think we do want it hidden from AT, otherwise it will be all too easy to accidentally create content that presents simply and nicely for the sighted user, but in the AT presents a giant document of pages to read through before getting to the content on the current page the user wants to be looking at.
On testing, this is very similar to hidden=until-found, however unlike hidden=until-found we would want this style to not be stateful. It would be expected that when the particular match is scrolled to that it would become active, but it does not become revealed by being discovered in the find-in-page search and will be effectively inactive again when offscreen again.
In #10711 we discussed how to make offscreen content not part of the focus-order or accessibility tree, however, it would be really useful if it could still be discovered by find-in-page similar to
hidden=until-found
such that it could be found and scrolled on screen which would subsequently make it interactive in the case of scrolling content where the visible page is interactive.The text was updated successfully, but these errors were encountered: