Okay
  Public Ticket #3222101
Accessibility
Closed

Comments

  • Kai started the conversation

    Hi, I love this theme and I'm using it for a public company - and by law, we have to follow the WCAG 2.2 guideline for all public websites. We have tested all requirements, and found  issues that means that the theme is not compliant to WCAG 2.2 (and even 2.1 and 2.0).

    There are 4 issues I have discovered:

    1.3.1 - Info and relationships
    Some headings (like "Related articles" are coded as H2, which break the use of titles). It would be better than these headings are not coded as H-tags, or have a setting in theme to set what tag to use to meet the requirements
    https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html

    2.4.1 - Bypass blocks
    It is not possible to buypass blocks, like to skip the mainmenu and jump right to content
    https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html

    2.4.3 - Focus order
    Using the TAB key, it seems that you go through the main menu (even if you use the hamburger icon with open menu on right side), and even the focus area is invisible
    https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html

    2.4.7 - Focus Visible
    The focus is not visible when using TAB key for most browsers. I have tested this with Firefox and Edge for Windows 11 (latest versions)
    https://www.w3.org/WAI/WCAG22/Understanding/focus-visible.html

    According to latest changelog, I find this:

    • NEW: Accessibility Ready — Kalium is accessible and follows WCAG 2.0 standards. It meets the AA level which is essential for usability.
  • [deleted] replied

    Hi Kai,

    Sorry for the late response.

    We are always looking to make the theme more accessible, and I will try to assist you so we can improve the theme through theme updates.

    Can you please tell us if you used any tool to perform those tests?

    Now, to improve the focus, please add this CSS code to your Custom CSS area:

    *:focus:not(:focus-visible) {
        outline: auto;
    }
    a:active, a:focus, a:hover, input[type=checkbox]:active, input[type=checkbox]:focus, input[type=radio]:active, input[type=radio]:focus {
        outline: auto;
    }

    Thanks!

  • Kai replied

    Hi Ylli, thanks for your feedback.

    Yes, this custom code works for focus when using TAB (except the hamburger menu - partly fixed for 2.4.7 - Focus Visible).

    I did not use a tool for this. I am using the WCAG checklist and test manually.

  • [deleted] replied

    Hi Kai,

    We are preparing a big update of Kalium for many months now, and it will also include the focus fix.

    We are also interested to improve accessibility as much as we can and we will concentrate on improving accessibility in a separate update once we release the big update next month.

    I also added your input to that to-do list.

    Thanks!