RE: SC for user agent dependence

Hi Jason,

I'm not referring to conforming alternates at all.  Just as with the note added, I'm referring to things like media queries which can change a page significantly based on screen size.  The note says that both the mobile version and the desktop version must conform, but only a success criteria can specify that I should be able to access the same content and functionality through each version.


From: White, Jason J []
Sent: Wednesday, July 26, 2017 3:15 PM
To: Repsher, Stephen J <>;
Subject: RE: SC for user agent dependence

From: Repsher, Stephen J []
Sent: Wednesday, July 26, 2017 2:19 PM
I thought a little more about the recent CFC which passed to add a note to the "Full Page" conformance requirement.  I realized that we probably do need a success criterion in addition to this note in order to fully address user needs.

The issue fixed by the added note makes it clear that all versions of the page that have a programmatic dependence need to conform in order for the "full page" to conform.  However, what if those different versions have significantly different content or functionality?
[Jason] In that case, one version would not be a "conforming alternate version" of the other, since the definition of "conforming alternate version" (see the glossary) requires content and functional equivalence. This answer assumes, of course, that the two renderings of the page constitute two different versions of it for purposes of WCAG. If we need to clarify this further, and I'm not sure whether we do, I think it belongs in the Conformance section rather than in the success criteria.


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.


Received on Wednesday, 26 July 2017 19:23:51 UTC