WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: WCAG2 and Section 508

for

Number of posts in this thread: 4 (In chronological order)

From: Isabel Holdsworth
Date: Wed, Aug 08 2018 8:28AM
Subject: WCAG2 and Section 508
No previous message | Next message →

Hi all,

Apologies if this question has already been done to death.

If my web application conforms to WCAG 2.0 (or better still 2.1) at
Level AA, does it automatically comply with Section 508?

If not, are there any succinct and specific guidelines I can refer to
in order to be confident that my application complies with US law?

Cheers, Isabel

From: Jonathan Avila
Date: Wed, Aug 08 2018 8:33AM
Subject: Re: WCAG2 and Section 508
← Previous message | Next message →

> If my web application conforms to WCAG 2.0 (or better still 2.1) at Level AA, does it automatically comply with Section 508?

If your application allows for authoring of content then Chapter 504 of the revised Section 508 standards would apply to web as well.

Section 508 revised also has requirements around support and documentation (Chapter 6) that aren't as clearly called out by the WCAG conformance requirements.

Jonathan

Jonathan Avila
Chief Accessibility Officer
Level Access
= EMAIL ADDRESS REMOVED =
703.637.8957 office

Visit us online:
Website | Twitter | Facebook | LinkedIn | Blog

Looking to boost your accessibility knowledge? Check out our free webinars!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

From: Ryan E. Benson
Date: Thu, Aug 09 2018 12:39AM
Subject: Re: WCAG2 and Section 508
← Previous message | Next message →

It should be noted that 504 also applies to tools developing the
system/output. Section 508 always had documentation requirements. Under the
old standards, if 1194.2x was applicable, 1194.31 and .41 were by default.
The same goes for the new standards, if Chapter 2 applies, Chapter 6 does,
which invokes 205.4:

Electronic content shall conform to Level A and Level AA Success Criteria
and Conformance Requirements in WCAG 2.0 (incorporated by reference, see
702.10.1).

EXCEPTION: Non-Web documents shall not be required to conform to the
following four WCAG 2.0 Success Criteria: 2.4.1 Bypass Blocks, 2.4.5
Multiple Ways, 3.2.3 Consistent Navigation, and 3.2.4 Consistent
Identification
Since most people who are just creating documents are not developers, many
agencies have created checklists for popular formats.

--
Ryan E. Benson


On Wed, Aug 8, 2018 at 10:33 AM Jonathan Avila < = EMAIL ADDRESS REMOVED = >
wrote:

> > If my web application conforms to WCAG 2.0 (or better still 2.1) at
> Level AA, does it automatically comply with Section 508?
>
> If your application allows for authoring of content then Chapter 504 of
> the revised Section 508 standards would apply to web as well.
>
> Section 508 revised also has requirements around support and documentation
> (Chapter 6) that aren't as clearly called out by the WCAG conformance
> requirements.
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> Level Access
> = EMAIL ADDRESS REMOVED =
> 703.637.8957 office
>
> Visit us online:
> Website | Twitter | Facebook | LinkedIn | Blog
>
> Looking to boost your accessibility knowledge? Check out our free webinars!
>
> The information contained in this transmission may be attorney privileged
> and/or confidential information intended for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any use, dissemination,
> distribution or copying of this communication is strictly prohibited.
>
>

From: Isabel Holdsworth
Date: Thu, Aug 09 2018 1:56AM
Subject: Re: WCAG2 and Section 508
← Previous message | No next message

Thanks guys - that's very helpful.

On 09/08/2018, Ryan E. Benson < = EMAIL ADDRESS REMOVED = > wrote:
> It should be noted that 504 also applies to tools developing the
> system/output. Section 508 always had documentation requirements. Under the
> old standards, if 1194.2x was applicable, 1194.31 and .41 were by default.
> The same goes for the new standards, if Chapter 2 applies, Chapter 6 does,
> which invokes 205.4:
>
> Electronic content shall conform to Level A and Level AA Success Criteria
> and Conformance Requirements in WCAG 2.0 (incorporated by reference, see
> 702.10.1).
>
> EXCEPTION: Non-Web documents shall not be required to conform to the
> following four WCAG 2.0 Success Criteria: 2.4.1 Bypass Blocks, 2.4.5
> Multiple Ways, 3.2.3 Consistent Navigation, and 3.2.4 Consistent
> Identification
> Since most people who are just creating documents are not developers, many
> agencies have created checklists for popular formats.
>
> --
> Ryan E. Benson
>
>
> On Wed, Aug 8, 2018 at 10:33 AM Jonathan Avila < = EMAIL ADDRESS REMOVED = >
> wrote:
>
>> > If my web application conforms to WCAG 2.0 (or better still 2.1) at
>> Level AA, does it automatically comply with Section 508?
>>
>> If your application allows for authoring of content then Chapter 504 of
>> the revised Section 508 standards would apply to web as well.
>>
>> Section 508 revised also has requirements around support and
>> documentation
>> (Chapter 6) that aren't as clearly called out by the WCAG conformance
>> requirements.
>>
>> Jonathan
>>
>> Jonathan Avila
>> Chief Accessibility Officer
>> Level Access
>> = EMAIL ADDRESS REMOVED =
>> 703.637.8957 office
>>
>> Visit us online:
>> Website | Twitter | Facebook | LinkedIn | Blog
>>
>> Looking to boost your accessibility knowledge? Check out our free
>> webinars!
>>
>> The information contained in this transmission may be attorney privileged
>> and/or confidential information intended for the use of the individual or
>> entity named above. If the reader of this message is not the intended
>> recipient, you are hereby notified that any use, dissemination,
>> distribution or copying of this communication is strictly prohibited.
>>
>>