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
Third-party content (including plugins, widgets, feeds, maps, carousels, etc) should be placed behind a click-to-load delay screen (using the "import on interaction" pattern), while alternatives to automated solutions such as chatbots should be offered.
I wonder if we could quantify when third-party is such that click-to-load screen saves data?
Ideas:
“if the third-party content weighs more than x% of the page” (that way a tool could calculate?)
maybe we need to also define what third-party is, an obvious example seems to be loading Google Maps in an iframe… is it maybe along the lines of 'content that uses script to load content from a third party'?
include 'chatbots' (or 'chat widgets'?) into list of examples of third-party content, and make the last bit something like 'while alternatives are offered, for instance a link to a contact form as an alternative for a chat widget' ?
I think we should stop at suggesting to use a delay pattern (lazy-loading, click-to-load, click-to-play, etc) also to avoid the risk to break the UX of the website/webapp.
include 'chatbots' (or 'chat widgets'?) into list of examples of third-party content, and make the last bit something like 'while alternatives are offered, for instance a link to a contact form as an alternative for a chat widget' ?
I would like to support above. Third-party script can easily fail to load, no matter the reason why, so providing alternative content/function/etc. is always good in terms of accessibility AND sustainability.
third-party is defined as 'loads or requests resources or functionality from a location outside of the primary location'.
'chat widgets' is now included in the list of examples of third-party content.
'a link to a contact form' is now used as an example of alternative content.
I've not included material on x% of a page because even though that would increase measurability, it would place emphasis on page weight being the main factor of compliance. This could put other sustainability factors should be considered (privacy, security, HTTP requests, accessibility, etc) at-risk of being ignored?
Note to @fullo, facades and lazy-loading is covered in part in 2.16 (amongst others), to avoid duplication click-to-load is likely the best reference as its not noted elsewhere?
Activity
fullo commentedon Mar 20, 2025
I think we should stop at suggesting to use a delay pattern (lazy-loading, click-to-load, click-to-play, etc) also to avoid the risk to break the UX of the website/webapp.
kazuhito-kidachi commentedon Mar 21, 2025
I would like to support above. Third-party script can easily fail to load, no matter the reason why, so providing alternative content/function/etc. is always good in terms of accessibility AND sustainability.
w3c#32 3.7 SC2 Updates
AlexDawsonUK commentedon Mar 23, 2025
I've made the changes as requested.
I've not included material on x% of a page because even though that would increase measurability, it would place emphasis on page weight being the main factor of compliance. This could put other sustainability factors should be considered (privacy, security, HTTP requests, accessibility, etc) at-risk of being ignored?
AlexDawsonUK commentedon Mar 23, 2025
Note to @fullo, facades and lazy-loading is covered in part in 2.16 (amongst others), to avoid duplication click-to-load is likely the best reference as its not noted elsewhere?