IFRAME Ghost Reviewing Accessibility https://liferay.dev/sv/c/message_boards/find_thread?p_l_id=119785294&threadId=103283312 2026-04-17T07:39:43Z 2026-04-17T07:39:43Z Enrique Rodríguez Vallejo https://liferay.dev/sv/c/message_boards/find_message?p_l_id=119785294&messageId=103632551 2025-12-17T15:05:27Z 2018-02-07T07:44:09Z

<strong>Really thanks for the answer Minhchau</strong>. At least I have a beginning to solve this problem. <img alt="emoticon" src="@theme_images_path@/emoticons/cool.gif" ><br /><br />Regards.

Enrique Rodríguez Vallejo 2018-02-07T07:44:09Z Minhchau Dang https://liferay.dev/sv/c/message_boards/find_message?p_l_id=119785294&messageId=103622009 2018-02-07T00:50:20Z 2018-02-07T00:50:20Z

<div class="quote-title">Enrique Rodríguez:</div><blockquote>Hi Minhchau, yes I&#39;m working with <strong> Koa11y</strong>. Do you know of any problems with this application?</blockquote><br />I was actually secretly hoping that you weren&#39;t using Koa11y, because I couldn&#39;t get it to work on my machine. However, I discovered that when you checkout the repository, the default branch hasn&#39;t been released yet (so it&#39;s expected that it won&#39;t work right), so I switched to the 3.0 branch and was able to take a look at it.<br /><br />Based on some experimentation, Koa11y detects the invisible iframe that&#39;s temporarily added for <a href="https://sennajs.com/">Senna.js</a> as problematic, which is essentially a false positive. If for some reason you have some requirement that says you must get Koa11y to report no errors, currently the only way to get rid of the WCAG2AA.Principle2.Guideline2_4.2_4_1.H64.1 error is to set <strong>javascript.single.page.application.enabled=false</strong> in your portal properties.<br /><br />Also be aware that certain Javascript interactions that create modal dialog windows won&#39;t have titles either, such as the ones created using Liferay.Util.openWindow, as described in <a href="https://issues.liferay.com/browse/LPS-68701">LPS-68701</a>.

Minhchau Dang 2018-02-07T00:50:20Z Enrique Rodríguez Vallejo https://liferay.dev/sv/c/message_boards/find_message?p_l_id=119785294&messageId=103576543 2025-12-17T15:05:27Z 2018-02-06T09:14:14Z

<div class="quote-title">Minhchau Dang:</div><blockquote>There was a <a href="https://liferay-community.slack.com/archives/C5H30KZ1A/p1517244543000643">thread in the community chat</a> where someone mentioned using <a href="https://github.com/open-indy/Koa11y">Koa11y</a>…</blockquote><br /><br />Hi Minhchau, yes I&#39;m working with <strong> Koa11y</strong>. Do you know of any problems with this application?<br /><br />Really thanks <img alt="emoticon" src="@theme_images_path@/emoticons/closed_eyes.gif" >

Enrique Rodríguez Vallejo 2018-02-06T09:14:14Z Minhchau Dang https://liferay.dev/sv/c/message_boards/find_message?p_l_id=119785294&messageId=103559812 2018-02-05T21:24:02Z 2018-02-05T21:24:02Z

<div class="quote-title">Enrique Rodríguez:</div><blockquote>Again, in a clean Liferay installation (without using any script or external service), IFRAME still appears, in the HTML markup it does not appear, but when I pass the accessibility test it does.</blockquote><br />What tool are you using for your accessibility test?<br /><br />There was a <a href="https://liferay-community.slack.com/archives/C5H30KZ1A/p1517244543000643">thread in the community chat</a> where someone mentioned using <a href="https://github.com/open-indy/Koa11y">Koa11y</a> and ran into a similar problem, but the instructions on the README for the repository don&#39;t work on my distribution of Linux (tested lts/argon, lts/boron, and lts/carbon versions of node.js), so I wasn&#39;t able to investigate it.

Minhchau Dang 2018-02-05T21:24:02Z Enrique Rodríguez Vallejo https://liferay.dev/sv/c/message_boards/find_message?p_l_id=119785294&messageId=103541825 2025-12-17T15:05:27Z 2018-02-05T11:40:46Z

<div class="quote-title">Jose Jimenez:</div><blockquote>Could you attach the .html source code generated?</blockquote><br /><br />Thanks for the answer, Jose.<br />Unfortunately I cannot share the HTML markup for privacy reasons. <strong>I know it&#39;s hard to help without seeing the code</strong>, so, <strong>thanks again</strong>.<br /><br />Clean installation of Liferay 7 CE, I try to pass the AA accessibility test, and get an error with an empty IFRAME, it&#39;s this &#34;curious&#34; <img alt="emoticon" src="@theme_images_path@/emoticons/wacko.gif" >

Enrique Rodríguez Vallejo 2018-02-05T11:40:46Z Enrique Rodríguez Vallejo https://liferay.dev/sv/c/message_boards/find_message?p_l_id=119785294&messageId=103541742 2025-12-17T15:05:27Z 2018-02-05T11:35:30Z

Again, in a clean Liferay installation (without using any script or external service), IFRAME still appears, in the HTML markup it does not appear, but when I pass the accessibility test it does.<br /><br /><img alt="emoticon" src="@theme_images_path@/emoticons/suspicious.gif" >

Enrique Rodríguez Vallejo 2018-02-05T11:35:30Z David H Nebinger https://liferay.dev/sv/c/message_boards/find_message?p_l_id=119785294&messageId=103385443 2018-01-31T20:11:23Z 2018-01-31T20:11:23Z

The problem, of course, will be any dynamic DOM manipulation made on behalf of dynamic javascript. Viewing the source may or may not reveal a match.<br /><br />I have a local vanilla copy of Liferay DXP, FP 38 running. If I view source and even view generated source, I have no iframes at all on the page. I&#39;m talking a vanilla launch, no additional plugins, themes, etc. just the OOTB launch with the blue welcome portlet on it.<br /><br />If you start pulling in js libraries for, say, ad displays, analytics frameworks, APM monitoring like NewRelic, etc., you start to lose control over what the page actually imports. For example, if you ever look at a page that includes the google analytics scripts, you&#39;ll sometimes find that there are all kinds of other scripts that get pulled in too that you didn&#39;t even realize. Try doing a view source on this forum page and check out all of the scripts that are pulled in for google ads, google analytics, insight, newrelic, plus a whole bunch of others that I don&#39;t remember or recognize.<br /><br />Plus, if you&#39;re behind a corporate proxy/firewall, they can also inject into the DOM stream in order to do employee monitoring. And I&#39;m guessing that certain state actors may do the same.<br /><br />If you&#39;re running a browser like Chrome or Firefox and you have extensions installed, they too can manipulate the DOM also.<br /><br />The point is that while the tool might be seeing an unnamed iframe, it could be coming from anywhere. You have to have to tools and knowhow to track it down and see where it originates from.

David H Nebinger 2018-01-31T20:11:23Z Jose Jimenez https://liferay.dev/sv/c/message_boards/find_message?p_l_id=119785294&messageId=103380238 2018-01-31T19:22:21Z 2018-01-31T19:22:21Z

Hi Enrique,<br /><br />Could you attach the .html source code generated?<br /><br />Looking for <strong>style=&#34;display: none;&#34;</strong> in the Liferay source code, it doesn&#39;t seem to be used in conjunction with a iframe, anyway the html can helps <img alt="emoticon" src="@theme_images_path@/emoticons/happy.gif" ><br /><br />Best,<br />Jose

Jose Jimenez 2018-01-31T19:22:21Z Juan Gonzalez https://liferay.dev/sv/c/message_boards/find_message?p_l_id=119785294&messageId=103306678 2018-01-30T09:32:17Z 2018-01-30T09:32:17Z

Interesting. Then, it will probably be rendered by some javascript component.

Juan Gonzalez 2018-01-30T09:32:17Z Enrique Rodríguez Vallejo https://liferay.dev/sv/c/message_boards/find_message?p_l_id=119785294&messageId=103304333 2025-12-17T15:05:27Z 2018-01-30T08:09:38Z

<div class="quote-title">David H Nebinger:</div><blockquote>It&#39;s not an OOTB liferay thing, so it was likely injected by your own code/libs.</blockquote><br /><br />I&#39;ve run <strong>several tests</strong> to rule out IFRAME being injected by my own code. <strong>In a clean installation of Liferay 7CE the IFRAME is still present, and giving the same error of accessibility</strong>.<br /><br /><img src="http://oi64.tinypic.com/mb2t1z.jpg" /><br /><br />I have reviewed my code from top to bottom, the IFRAME is injected by Liferay for some reason I don&#39;t know.<br /><br />Thanks for &#34;help&#34;…

Enrique Rodríguez Vallejo 2018-01-30T08:09:38Z David H Nebinger https://liferay.dev/sv/c/message_boards/find_message?p_l_id=119785294&messageId=103283835 2018-01-29T17:36:21Z 2018-01-29T17:36:21Z

Who knows? I mean, it may be instantiated or removed via javscript. Kind of looks like some sort of tracking thing to me since it has display:none.<br /><br />It&#39;s not an OOTB liferay thing, so it was likely injected by your own code/libs.

David H Nebinger 2018-01-29T17:36:21Z Enrique Rodríguez Vallejo https://liferay.dev/sv/c/message_boards/find_message?p_l_id=119785294&messageId=103283311 2025-12-17T15:05:27Z 2018-01-29T16:30:22Z

<html><head></head><body>Hi all,<br>I'm reviewing the accessibility of a portal in Liferay 7 CE. I have the following error in the checkup:<br><br><pre><code>WCAG2AA.Principle2.Guideline2_4.2_4_1.H64.1 error: Iframe element requires a non-empty title attribute that identifies the frame. &lt;iframe src="" style="display: none;"&gt;&lt;/iframe&gt;</code></pre><br><br>I'm trying to find that IFRAME but it's impossible. When I search in HTML markup, the IFRAME does not appear.<br>Where is this IFRAME and how can I edit it to pass the accessibility test?</body></html>

Enrique Rodríguez Vallejo 2018-01-29T16:30:22Z