Notification of Loading/Busy: Question about the initial wait to load a new page

[kimamula]

Hi,

I have a question regarding this document: https://www.w3.org/WAI/GL/wiki/Notification_of_Loading/Busy

It says that: "This is not about the initial wait to load a new page. Those are announced to screen readers."

Does this mean that screen readers are responsible for announcing the loading state during the initial page load, and web pages shouldn't need to implement programmatic notifications for that?

We have a web page that takes time to load (especially for mobile devices). When a user visits this page, they first see a loading spinner that is included in the HTML returned from the server for like several seconds, and then see the actual page after the page completes loading the required JS and CSS resources. The accessibility team at my organization pointed out that it is an accessibility violation that screen readers do not announce the loading state when the loading spinner is displayed, referring to https://www.w3.org/WAI/GL/wiki/Notification_of_Loading/Busy.

I investigated this issue with VoiceOver and found that:

• aria-live doesn't work until the window's load event (i.e., VoiceOver doesn't announce anything when the content of a live region is updated before the load event). Since the majority of the time the loading spinner is displayed is before the load event, aria-live doesn't help here.
• Focusing programmatically on a visually hidden text "Loading" immediately after the HTML load lets VoiceOver announce it. However, I'm not confident that this is a proper solution because I can't find anyone mentioning such a solution on the internet. (Also, I'm unsure if this works for all screen readers.)

Could you please guide me on how web pages are supposed to be implemented in this case?

Thank you!

[TestPartners]

Your interpretation is correct and your accessibility team are wrong. Under the SC Text heading, the document says, “After initial page load, programmatic notification is provided for each visual indicator that content is loading or the page is busy”. The document only applies to changes that occur without a page reload, such as AJAX or single page applications. Steve Green Managing Director Test Partners Ltd From: Kenji Imamula ***@***.***> Sent: 08 December 2025 02:16 To: w3c/wcag ***@***.***> Cc: Subscribed ***@***.***> Subject: [w3c/wcag] Notification of Loading/Busy: Question about the initial wait to load a new page (Issue #4789) [https://avatars.githubusercontent.com/u/3130879?s=20&v=4]kimamula created an issue (w3c/wcag#4789)<#4789> Hi, I have a question regarding this document: https://www.w3.org/WAI/GL/wiki/Notification_of_Loading/Busy It says that: "This is not about the initial wait to load a new page. Those are announced to screen readers." Does this mean that screen readers are responsible for announcing the loading state during the initial page load, and web pages shouldn't need to implement programmatic notifications for that? We have a web page that takes time to load (especially for mobile devices). When a user visits this page, they first see a loading spinner that is included in the HTML returned from the server for like several seconds, and then see the actual page after the page completes loading the required JS and CSS resources. The accessibility team in my organization pointed out that it is an accessibility violation that screen readers do not announce the loading state when the loading spinner is displayed, referring to https://www.w3.org/WAI/GL/wiki/Notification_of_Loading/Busy. I investigated this issue with VoiceOver and found that: * aria-live doesn't work until the window's load event (i.e., VoiceOver doesn't announce anything when the content of a live region is updated before the load event). Since the majority of the time the loading spinner is displayed is before the load event, aria-live doesn't help here. * Focusing programmatically on a visually hidden text "Loading" immediately after the HTML load lets VoiceOver announce it. However, I'm not confident that this is a proper solution because I can't find anyone mentioning such a solution on the internet. (Also, I'm unsure if this works for all screen readers.) Could you please let me know how web pages are supposed to be implemented in this case? Thank you! — Reply to this email directly, view it on GitHub<#4789>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACSY765NJUW4A2BSX4CMYZ34ATNPRAVCNFSM6AAAAACOKN5PQGVHI2DSMVQWIX3LMV43ASLTON2WKOZTG4YDIMZVGY4DEOI>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>