• Hello,
    I chose Kadence as it was advertised as accessibility ready & now, we are running into major accessibility challenges. The following are the accessibility problems.

    1. Broken skip link, with screen reader when skip link is activated the focus of the screen reader does not move to expected region on the page. It can be main region landmark or heading level1. The screen just scrolls visually. Keyboard focus must move to the element when skip link is triggered.
    2. Back to scroll not working, similar issue mentioned above. Page just scrolls visually; focus do not move either to skip link or heading level1.
    3. Tables are broken on mobile; tables are not responsive. This is due to using wordbreak as 100%.
    4. The carousel of similar posts has next & previous buttons, these buttons are not keyboard focusable. Checking the code, the following is observed:
    Pressing tab moves focus to the div that contains buttons as div is given tabindex=0. This is a failure of accessibility.
    Both previous & next buttons are provided with tabindex=-1. They do not need tabindex as they are <button tags & are accessible by default. Please note that Native HTML elements are accessible to all assistive technologies.

    <div class=”tns-controls” aria-label=”Carousel Navigation” tabindex=”0″><button type=”button” data-controls=”prev” tabindex=”-1″ aria-controls=”tns1″>prev</button><button type=”button” data-controls=”next” tabindex=”-1″ aria-controls=”tns1″>next</button></div>

Viewing 4 replies - 16 through 19 (of 19 total)
  • We are working on some more updates, the #kt-scroll-up will have aria-hidden, it’s only for visual users. As for the carousel this continues to get more changes.

    Ben

    Hello,

    Yes, we need aria-hidden, I provide the same fix in my site. I also changed the role=tablist to role=toolbar in carousel & it is working as expected. The carousel is fully accessible with that minor change.

    Thanks!

    @tarkham Glad you’re here giving advice. I’m a fan of your articles and I’ve referred to them many times. I was wondering if the updates over the last few months covered all the deficiencies your testing had found?

    @britner Huge fan of Kadence, I’ve been sending people to this theme for the last year, and thanks to your theme builder, I’ve helped dozens of companies get online for free when they couldn’t afford my agency (we built free themes on Kadence and released them). Just wanted to say, the OP here is giving you accurate feedback, and I’m happy to see you’re working with him to resolve things.

    Thank you both!

    Thread Starter raghavendra satish peri

    (@tarkham)

    Hello Michael,
    Yes, most of the major issues have been resolved. Got few minor one & I will revisit them after March. Ben here is very helpful & prompt with updates. Thanks to him for Kadence being more accessible than other themes.

    Good to know that you like my articles on accessibility. This encourages me to keep going.

    Thank You!

Viewing 4 replies - 16 through 19 (of 19 total)
  • The topic ‘Kadence Theme not Accessibility Ready yet!’ is closed to new replies.