Accessibilty and noscript Elements

  • Resolved digitalmitsinn

    (@digitalmitsinn)


    7 months, 1 week ago

    Hey there, I am currently reviewing error messages and alerts with the WAVE-Extension on my chrome browser for accessibilty purposes. I am getting alerts, that noscript elements are being present. I figured, that those elements are the pictures, which are lazyloaded with autoptimize. Unfortunately the noscript content is written as escaped html text, which seems not to be accessible. Due to my research the noscript elements 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?

    Thank you in advance!

    Katja

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    7 months, 1 week ago

    this is an example of how AO’s lazyload changes 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-image-3452"/></noscript><img decoding="async" width="150" height="56" src='data:image/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-image-3452"/>

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

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    6 months, 1 week ago

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

    have a nice day!
    frank

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

The topic ‘Accessibilty and noscript Elements’ is closed to new replies.