Bug report: SEO Optimization

  • After publishing the page containing slider Accessibility has dramatically decreased.

    Here is the list of discovered problems with PageSpeed Insights from Google:

    1. [aria-*]?attributes do not match their roles (related to active slick dot)

    <li aria-hidden="false" role="presentation" aria-selected="false" aria-controls="navigation01" id="slick-slide01" class="slick-active">

    2. Elements with an ARIA?[role]?that require children to contain a specific?[role]?are missing some or all of those required children (related to slick dots list and active slick dot)

    1 2 3 4
<ul class="slick-dots" style="" role="tablist">
    2
<li aria-hidden="false" role="presentation" aria-selected="false" aria-controls="navigation01" id="slick-slide01" class="slick-active">

    3. button,?link, and?menuitem?elements do not have accessible names (it’s about previous and next slick arrows of slider).

    div.wppsac-wrap > div#wppsac-post-carousel-1 > span.slick-prev
<span class="slick-prev slick-arrow" data-role="none" role="button" style="">
    div.wppsac-wrap > div#wppsac-post-carousel-1 > span.slick-next

<span class="slick-next slick-arrow" data-role="none" role="button" style="">

    4. [aria-hidden="true"]?elements contain focusable descendents (related to slick dots)

    1
<li class="" aria-hidden="true" role="presentation" aria-selected="true" aria-controls="navigation00" id="slick-slide00">
    1
<button type="button" data-role="none" role="button" tabindex="0">
    3
<li aria-hidden="true" role="presentation" aria-selected="false" aria-controls="navigation02" id="slick-slide02">
    3
<button type="button" data-role="none" role="button" tabindex="0">
    4
<li aria-hidden="true" role="presentation" aria-selected="false" aria-controls="navigation03" id="slick-slide03">
    4
<button type="button" data-role="none" role="button" tabindex="0">

    5. ARIA input fields do not have accessible names (related to slick tray)

    <div class="slick-track" style="opacity: 1; width: 7686px; transform: translate3d(-2562px, 0px, 0px);" role="listbox">
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Ketan Patel

    (@patelketan)

    Hello,

    actually, our plugin using third-party slider JS API(slick.js).

    Please check to below link…

    https://kenwheeler.github.io/slick/

    Thread Starter alivemcleod

    (@alivemcleod)

    Do I understand you right, that you’re using 3rd party library updated last time in 2017 (6 years ago so far) and not gonna do anything about that?

    I believe all the listed above issues are critical bugs since affect SEO metrics which leads to lower ranking in search result.

    I understand that’s easier is to leave it as-is.

    However, I’m asking you as a author of the plugin to fix it.

    Plugin Contributor Ketan Patel

    (@patelketan)

    Hello @alivemcleod,

    We have used Slick Slider JS’s latest jQuery version…

    Please see the below slick slider changelog.

    https://github.com/kenwheeler/slick/releases

    Thanks for informing. we will try to compare slick JS with Accessibility.

    Thanks,

    Thread Starter alivemcleod

    (@alivemcleod)

    Thank you!

    It just about make all changes centralized from the contributor

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Bug report: SEO Optimization’ is closed to new replies.