diff --git a/conformance-challenges/index.html b/conformance-challenges/index.html index 7a6ef09b7a..916aa5e23b 100644 --- a/conformance-challenges/index.html +++ b/conformance-challenges/index.html @@ -39,12 +39,19 @@ This document focuses primarily on challenges to large, highly complex, dynamic sites. Other efforts in WAI are looking at different aspects of conformance for other types of sites.

-

The challenges covered broadly fall into four main areas:

+

The challenges covered broadly fall into five main areas:

  1. Numerous provisions need human involvement to test and verify conformance, which is especially challenging to scale for large websites and for dynamic websites;
  2. Large and dynamic sites with their changing permutations may be difficult to validate;
  3. Third parties frequently add and change content on large and dynamic sites;
  4. Applying a web-based, and page-based conformance model can be challenging to do for non-web Information and Communications Technologies (ICT).
  5. +
  6. The centrality of Accessibility Supported in the many provisions +tied to use with assistive technologies and platform accessibility +features, combined with the lack of definition of what constitutes +Accessibility Supported, further exacerbates the need for expert +human judgement (\#1 above), as well as potential different and +non-overlapping sets of these features used when including 3rd +party content (\#3 above).

The purpose of this document is to help understand those challenges more holistically, and explore approaches for mitigating them so that we can address such challenges more fully in future accessibility guidelines including the forthcoming W3C Accessibility Guidelines (WCAG 3.0) (now in early development) where the W3C Working Group Charter expressly anticipates a new conformance model.

@@ -257,11 +264,11 @@

Silver Research Findings

yield consistent conclusions: Regardless of proficiency, there is a significant gap in how any two human auditors will identify a success or fail of criteria. - ... Ultimately, there is variance between: any two - auditors; ... Because there's so much room for human + … Ultimately, there is variance between: any two + auditors; … Because there's so much room for human error, an individual may believe they've met a specific conformance model when, in reality, thatâ– s not the - case. ... There isn't a standardized approach to how + case. … There isn't a standardized approach to how the conformance model applies to success criteria at the organizational level and in specific test case scenarios. @@ -473,7 +480,7 @@

Challenge #5: Accessibility Supported

Silver Research Findings

Silver concluded that Accessibility Supported is a conformance requirement -of WCAG 2 that is poorly understood and incompletely implemented, ... i.e. the role +of WCAG 2 that is poorly understood and incompletely implemented, … i.e. the role of AT in assessing conformance. See additional details in Appendix C below.

@@ -484,7 +491,7 @@

Mitigations

We know of no useable mitigations to achieve the Accessibility Supported conformance requirement for public facing web sites. WCAG-EM's Second Note suggests that: For some websites in closed networks, such as an intranet website, where both the users and the computers used to access the website are known, this baseline may be limited to the operating systems, web browsers and assistive technologies used within this closed network. It continues saying: However, in most cases this baseline is ideally broader to cover the majority of current user agents used by people with disabilities in any applicable particular geographic region and -language community. Beyond placing the responsibility on the evaluator to establish this baseline, Note 5 in Understanding Conformance 2.0 suggests that: One way for authors to locate uses of a technology that are accessibility supported would be to consult compilations of uses that are documented to be accessibility supported. ... Authors, companies, technology vendors, or others may document accessibility-supported ways of using Web content technologies. Unfortunately, we know of no such public repository. +language community. Beyond placing the responsibility on the evaluator to establish this baseline, Note 5 in Understanding Conformance 2.0 suggests that: One way for authors to locate uses of a technology that are accessibility supported would be to consult compilations of uses that are documented to be accessibility supported. … Authors, companies, technology vendors, or others may document accessibility-supported ways of using Web content technologies. Unfortunately, we know of no such public repository.

@@ -976,7 +983,7 @@

Audio Control

Where non-web software contains audio, especially audio that automatically plays in certain circumstances (e.g. making a ringing sound to indicate an -incoming call) ...

+incoming call) …

EDITOR'S NOTE
Section content yet to be written.