Thread Subject: Re: Group B: 22(k) Text-only page

Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.

From: Sean Hayes
Date: Thu, Nov 16 2006 6:45 AM

Can somebody provide an example of how this would work in practice?

Not wishing to be contrarian; but if it is not possible to make a page comply, then I'm failing to see how it is possible to create a fully equivalent alternate that does comply; if this were possible, then surely the same technique could be used in the main page - what am I missing here?

Sean Hayes
Standards and Policy Team
Accessible Technology Group
Microsoft
Phone:
mob +44 7977 455002
office +44 117 9719730

-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Bailey Bruce
Sent: 16 November 2006 13:36
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Group B: 22(k) Text-only page

Just being picayune here...

Jonathan writes:
> I like the proposed 22(k) better than the w3c guideline. As
> a low vision user I don't consider a text only page even when
> total equivalent equal access.

I think you mean WCAG Checkpoint (not W3C guideline) but WCAG doesn't
use the term text only page. That misnomer was introduced by the 508
rephrasing of Checkpoint 11.4. Follows are the versions in
chronological order.

WCAG 1.0 11.4: If, after best efforts, you cannot create an accessible
page, provide a link to an alternative page that uses W3C technologies,
is accessible, has equivalent information (or functionality), and is
updated as often as the inaccessible (original) page.

1194.22(k): A text-only page, with equivalent information or
functionality, shall be provided to make a web site comply with the
provisions of this part, when compliance cannot be accomplished in any
other way. The content of the text-only page shall be updated whenever
the primary page changes.

WCAG 2.0 (working draft) 4.2.1: At least one version of the content
meets all level 1 success criteria, but alternate version(s) that do not
meet all level 1 success criteria may be available from the same URI.

WCAG 2.0 (editor's draft) 4.2.1: When multiple versions of the same
content are available, at least one version meets all level 1 success
criteria. Any version that does not meet all level 1 success criteria
provides a mechanism to obtain a version that does, and that mechanism
meets all level 1 success criteria.

Jim Thatcher's proposed rewrite of 22(k): Alternate versions of pages
which comply with these provisions with equivalent information and
functionality shall be provided when compliance cannot be accomplished
in any other way. The content of the alterative pages shall be updated
whenever the primary pages change and available with the same ease as
the primary pages.

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University