Removal of Stylesheet

This is a technique for testing:

WCAG 2.0: Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure. Understanding Guideline 1.3

1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A) How to Meet 1.3.1 | Understanding 1.3.1

1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A) How to Meet 1.3.2 | Understanding 1.3.2

3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA) How to Meet 3.2.3 | Understanding 3.2.3

Overview

Cascading Style Sheets (CSS) allow developers to design their web pages and keep the presentation, font types, sizes and general style, colour and menu elements separate from the content. This means there can be a template that works across a whole website and changes can be made easily. There are many samples of accessible CSS templates on the web to help web developers and the W3C has a CSS Template Layout Module. Users can even develop their own style sheet with the JISC TechDis User Style Sheet Wizard.

Method

This is a relatively easy test to undertake. Nearly all the accessibility toolbars offer a chance to remove the style sheet as in the Firefox Web Developer toolbar or disable styles in the Webaim WAVE toolbar so you have text only without structure.

In Internet Explorer the AIS Web Accessibility Toolbar disable CSS menu offers the same features.

style sheet removed

Advice