Is there a way from a web page to dynamically force a full page re-read ? #16107
Coldknife2
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I know that there is aria-live with assertive/polite and role=alert on web pages to dynamically tell the presence of new elements.
But as I've tested a few things, it seem for instance that when a new button is added to the page under a live polite element, it is read as only the title, not as a button
ex:
<div aria-live="polite">
adds a
<button>"click me"</button>
inside said<div>
reads: "click me"
VS
when loading a page
<button> "click me"</button>
reads as: "Button click me"
And when we're talking about SPA it's almost worse when you change pages : screen readers considers we haven't changed web pages (which is true) but in fact we are displaying a complete different page.
And the few attempts I've made (like having a top div element containing all page changes) help a little but it's really hard figuring the new layout of the page displayed (Could change from a form to another with a lot of fields changes and new buttons but buttons aren't read as buttons, and links as links)
[Possibly here, could provide an example with react, vue, angular... to demonstrate said problems]
So I was wondering: since there is the possibility to trigger a page re-read ("+" numpad shortcut if I recall correctly), isn't there somewhere in a RFC of the sort a way by javascript to trigger a re-read ?
Like window.accessibility.askToReadAllPage() ?
If not, how can one propose such an idea to be evaluated for future addition or editions of such web standards ?
Beta Was this translation helpful? Give feedback.
All reactions