Search code examples
accessibilitywcagwcag2.0

1.3 and 2.1.1 parts of wcag 2.0

I'm reading WCAG 2.0 guidelines located here(click me) and some parts of it isn't clear to me.

1) As I understand from 1.3 section, I should make content that would be visible properly without css, for example. How is it "technology-agnostic" I wonder? Simply, I MUST use javascript in some cases in order to some of my css cool stuff will work. So if I wanna make my site independent of JS - I simply can't. Also if I'm using something that is JS-coded, I can't be sure it will work with some screen readers. So again, it is technology depended. Am I missing here something?

2) About the 2.1.1 part. If for example I have a slider on my site and I can't make it accessible from keyboard for some reason, but it has no keyboard trap and the content the slider represents has no critical value(it can be accessed from other links on the site). Would this be fine to success the criteria? In the description of the 2.1.1 section, it says "wherever possible", so my guess it is totally fine, but yet I'm not sure.

Solution
    1. WCAG is "technology-agnostic", but your site does not have to be.

    You can see from WCAG's website an example of declaration of "relied-upon technologies" : https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html

    1. Hard to answer this question without experimenting the user experience. You have to remember that the keyboard-only navigation is not intended to be used only by blind people. So it can be very frustrating to view a slider and have no way to interact with it.

    For a "screen reader" perspective, you can choose to ignore elements if they are purely used for decoration or redundant (aria-hidden attributes), but it does not mean that you can ignore keyboard accessibility for those elements.