CODEWITHSUNDEEP
cssaccessibilitywcagwcag2.0
popiweho
popiweho

Reputation: 21

Is it recommended to disable CSS to check a website for accessibility?

Many developers/accessibility experts suggest to disable CSS for checking the website for accessibility, but no one explicitly says how it may actually be helpful in terms of web accessibility.

So here I am, asking you exactly that, because all my attempts to check this in reliable (I WANT TO BELIEVE!) sources like "w3.org", including their WCAG 2.0 recommendations, don't say anything about making website accessible without CSS. Moreover, they say it may be "relied upon" some technology, like CSS, for example.

Upvotes: 2

Views: 2689

Answers (3)

Valross.nu
Valross.nu

Reputation: 2299

If you use the accessibility testing tool Wave you can actually disable styles in the tool. So, as built in a testing tool it's a great way to test the structural element flow. There is no purpose in itself to disable CSS besides testing accessibility in this way.

Upvotes: 0

Josh
Josh

Reputation: 4322

You no longer need to explicitly verify that pages are readable without CSS, but it can be useful as a technique for ensuring correct reading order.

The requirement to make pages readable without CSS is a carryover from the days when Section 508 was the dominant accessibility standard.

36 CFR Parts 1193 and 1194 - Published February 18, 2017

There is no direct analogy in the WCAG 2.0 Success Criteria for section 1194.22(d) of the existing 508 Standards, which states: “documents shall be organized so they are readable without requiring an associated style sheet.” 36 CFR §1194.22(d).

https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/single-file-version

WCAG 2.0 addresses this same issue in a different way with Success Criterion 1.3.2 - Meaningful Sequence.

One of the techniques for meeting this criterion is making the DOM order match the visual order (C27), which is largely what this comes down to anyway.

Upvotes: 3

Valross.nu
Valross.nu

Reputation: 2299

I would say that a good reason to actually disable CSS in terms of checking accessibility is to see that your site structure is built up in a logical way.

On the other hand, a better way to test this is to use a screenreader and tab through the site using use tab / shift + tab with a keyboard. In that way you do not only get an eureka-moment on structural issues you also get the audio-feedback that will give you lots of AHA:s about phrasing, ARIA-issues and hidden elements not hidden in a accessible way.

I'd point you to try out ChromeVox

Upvotes: 1

Related Questions