W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2016

Re: WCAG compliance question

From: Durham, Heather <heather.durham@pearson.com>
Date: Fri, 26 Feb 2016 16:42:14 -0700
Message-ID: <CAOtaF1nOFTVOw-uAPgWsMtuBOr4MborJ1bMJBQXTimX_nc_bQg@mail.gmail.com>
To: Phill Jenkins <pjenkins@us.ibm.com>
Cc: WAI Interest Group <w3c-wai-ig@w3.org>
I believe you may have misunderstood. Disabling CSS is not a requirement,
but functionality that a user needs in order to use a web page shouldn't be
coded into the CSS layer, which would then be lost if CSS is disabled.

On Fri, Feb 26, 2016 at 3:32 PM, Phill Jenkins <pjenkins@us.ibm.com> wrote:

> well, the only reference to CSS in *1.3.1*
> <https://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html>that
> I found is an advisory technique to encourage actually using CSS correctly:
> [red underline highlighting added]
>
> *Additional Techniques (**Advisory**) for 1.3.1*
>
> Although *not required for conformance*, the following additional
> techniques should be considered in order to make content*more *accessible.
> Not all techniques can be used or would be effective in all situations.
>
>    - *C22: Using CSS to control visual presentation of text*
>    <http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/C22>(CSS)
>    - Using CSS rather than tables for page layout (future link)
>
>
> nothing abut disabling CSS as a requirement that I could find.
> ___________
> Regards,
> Phill Jenkins,
>
>
>
>
>
> From:        "Durham, Heather" <heather.durham@pearson.com>
> To:        Phill Jenkins/Austin/IBM@IBMUS
> Cc:        WAI Interest Group <w3c-wai-ig@w3.org>
> Date:        02/26/2016 04:25 PM
> Subject:        Re: WCAG compliance question
> ------------------------------
>
>
>
> It is what I understood from this:
> WCAG 2.0 – Level A - 1.3.1 Info and Relationships:
> Information, structure, and relationships conveyed through presentation
> can be programmatically determined or are available in text. (Level A)
>
>
> *https://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html*
> <https://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html>
>
> ​​
>
>
> On Fri, Feb 26, 2016 at 2:47 PM, Phill Jenkins <*pjenkins@us.ibm.com*
> <pjenkins@us.ibm.com>> wrote:
> > Here's my take: With CSS disabled, users must be able to view, reach,
> activate and interact . . .
>
> Are you suggesting a new success criteria for WCAG 2.x?
>
> or is that your individual interpretation?
>
> Otherwise, where in WCAG 2.0 does it require the web app to work with CSS
> disabled?
>
> ___________
> Regards,
> Phill Jenkins,
>
>
>
> --
>
> *Heather Durham*
> Accessibility SQA, HEd
>
> Pearson
> 2154 E. Commons Ave.
> Suite 4000
> Centennial, CO  80122
> USA
>
> *Learn more at **pearson.com* <http://pearson.com/>
>
>
>


-- 


*Heather Durham *Accessibility SQA, HEd

Pearson
2154 E. Commons Ave.
Suite 4000
Centennial, CO  80122
USA

*Learn more at pearson.com <http://pearson.com>*

[image: Pearson]
Received on Friday, 26 February 2016 23:43:20 UTC

This archive was generated by hypermail 2.3.1 : Friday, 26 February 2016 23:43:21 UTC