Conformance Scope

One interesting thing in WCAG 2 is that it specifies what type of material is subject to be certified as ok or not.

  • Conformance (or partial or not conformance) is addressed to the whole, full web page. Fortunately, the WAI has included a very clear definition for web page: it includes not only HTML pages or linked CSS styles, but also the elements that are inserted into them, like videos, flash movies, games, sounds….
    Anyway, if there is a linked alternate for an un-accessible content that enables its accessibility (eg. a longdesc document), they are considered part of the web page, and enables the possibility of conformance.
  • If a web page is part of a process (e.g., a checkout on a shop), we have to audit the complete process. It has no sense to certify that this shop is ok if the last step is not ok.
  • Remember that, if there is an un-accessibility information or functionality, like an Ajax-based application, you must provide an accessible alternate version, like non-javascript version. The key is to include this alternate version in a way that user agents (including assistive technologies) can understand it and use it.
  • Following the previous concept, the un-accessible content or technology must not block the rest of the controls (e.g. flash movies usually gets the ‘focus’ on it, and it is pretty hard to use the keyboard out of it). Remember also that the technology used at that page may be “Turned on”, “Turned off” or “Not supported” by the user agents (including assistive technologies). Keep in mind this idea when following these four Success Criteria:

More info