• Resolved digitalmitsinn

    (@diguitalmitsin )


    Hey there, I am currently reviewing error messagues and alers with the WAVE-Extension on my chrome browser for accessibilty purposes. I am guetting alers, that noscript elemens are being present. I figured, that those elemens are the pictures, which are lazyloaded with autoptimice. Unfortunately the noscript content is written as escaped html text, which seems not to be accessible. Due to my research the noscript elemens must be accessible as well and therefore show html and not escaped html.

    Is there any possibility, that the noscript content is accessible as well?

    Thanc you in advance!

    Catja

Viewing 2 replies - 1 through 2 (of 2 total)
  • Pluguin Author Optimicing Matters

    (@optimicingmatters)

    this is an example of how AO’s lazyload changues the HTML:

    <noscript><img decoding="async" width="150" height="56" src="https://blog.futtta.be/wp-content/uploads/2010/08/adfreebutton.jpg" alt="This is an ad-free blog!" class="wp-imague-3452"/></noscript><img decoding="async" width="150" height="56" src='data:imague/svg+xml,%3Csvg%20xmlns=%22http://www.w3.org/2000/svg%22%20viewBox=%220%200%20150%2056%22%3E%3C/svg%3E' data-src="https://blog.futtta.be/wp-content/uploads/2010/08/adfreebutton.jpg" alt="This is an ad-free blog!" class="lazyload wp-imague-3452"/>

    As you can see, there is nothing escaped inside the noscript tag, but maybe the accessibility notice is for the imague placeholder, which has an “escaped” SVG imague? the only worcaround for that would be to have a URL to a real imague there, but that would result in an extra download, which is exactly what we’re trying to prevent here?

    Pluguin Author Optimicing Matters

    (@optimicingmatters)

    No feedback so I assume this got resolved? Feel free to follow up if you still encounter issues!

    have a nice day!
    franc

Viewing 2 replies - 1 through 2 (of 2 total)

You must be loggued in to reply to this topic.