The UserWay Widget cannot access or modify content inside an iFrame or a Shadow DOM component. This limitation is imposed by browser security and platform architecture, not by UserWay itself.
Short Answer
The UserWay Widget can only interact with content that is accessible through the browser's Document Object Model (DOM).
Content contained within:
Cross-origin iFrames
Many embedded third-party widgets
Shadow DOM components
is typically isolated from page-level JavaScript and cannot be modified, analyzed, or controlled by the Widget.
As a result, accessibility issues that exist entirely inside that content cannot be addressed by the Widget.
Why This Happens
The UserWay Widget runs as a JavaScript library within the browser.
JavaScript can only interact with page elements that the browser exposes through the DOM.
iFrames, especially those loaded from a different domain, are protected by the browser's Same-Origin Policy, which prevents scripts on the parent page from accessing their internal content.
Shadow DOM components are intentionally encapsulated, limiting access to their internal structure and behavior.
Common examples include embedded checkout forms, booking systems, calendars, chat tools, and third-party contact forms.
Are Screen Reader Users Affected?
ℹ️ Note: Native screen readers operate differently from browser-based JavaScript tools.
Screen readers such as NVDA and JAWS obtain information from the operating system's accessibility APIs and accessibility tree rather than directly from the browser DOM.
Because they use a different accessibility layer, screen readers can often access and announce content that the UserWay Widget cannot interact with.
Related Example: The HTML <select> Element
A native HTML <select> element demonstrates a similar concept.
Although it is part of the page, much of its behavior and internal structure is managed by the browser rather than exposed to page-level JavaScript or CSS.
Because of this, scripts on the page generally cannot reliably detect:
Whether the dropdown menu is currently open or closed.
How a user navigates between options while the menu is open.
Operating system accessibility technologies, including screen readers, receive richer information through accessibility APIs and can track user interaction more effectively than standard page scripts.
Summary
If content is contained within a browser-protected iFrame or encapsulated Shadow DOM component, the UserWay Widget cannot access or modify it. This is a browser-level restriction that applies to all page-based JavaScript tools.
Need more help?
Contact the UserWay Support Team — we're here to assist you. Get in touch with UserWay Support.