From 3e2d7b19f8d217758915f598b91fb8446d91d587 Mon Sep 17 00:00:00 2001 From: Jeanne Spellman Date: Thu, 31 Mar 2022 17:20:23 -0400 Subject: [PATCH 01/11] #297 typo Then need to work together changed to They need --- requirements/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements/index.html b/requirements/index.html index bd8a2c2d..67d19bdf 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -111,7 +111,7 @@

Usability

Conformance Model

-

There are several areas for exploration in how conformance can work. These opportunities may or may not be incorporated. Then need to work together, and that interplay will be governed by the design principles

+

There are several areas for exploration in how conformance can work. These opportunities may or may not be incorporated. They need to work together, and that interplay will be governed by the design principles

From 263196564d4cf3fe49b6ce5ce35ec583a2da4498 Mon Sep 17 00:00:00 2001 From: Jeanne Spellman Date: Thu, 31 Mar 2022 17:35:06 -0400 Subject: [PATCH 04/11] #300 remove "the" --- requirements/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements/index.html b/requirements/index.html index 6629e24d..5cee41d0 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -115,7 +115,7 @@

Conformance Model

From 9c8913fa6d4a002abb50aca9fed7ce63db02f2f5 Mon Sep 17 00:00:00 2001 From: Jeanne Spellman Date: Thu, 31 Mar 2022 17:45:55 -0400 Subject: [PATCH 05/11] #296 --- requirements/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements/index.html b/requirements/index.html index 5cee41d0..29f0d36e 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -80,7 +80,7 @@

WCAG 3.0 Scope

Silver Task Force Research

Introductory text about the research efforts undertaken, with pointers to methodology and results

The research done in 2017-2018 by the Silver Task Force, the Silver Community Group, and the research partners was used to identify the key problem statements related to the current accessibility guidelines (WCAG 2.x, ATAG 2.0 and UAAG 2.0). See the Silver Research Summary slides for more detailed information. These problem statements were used to identify the opportunities for WCAG 3.0 to address that will improve accessibility guidance.

-

During the year of WCAG 3.0 research, a recurring theme was the popularity and quality of the guidance in WCAG 2.0. Most of the opportunities identified in the research were improvements in the structure and presentation accessibility guidance to improve usability, to support more disability needs, and to improve maintenance.

+

A recurring theme identified in the year of WCAG 3.0 research was the popularity and quality of the WCAG 2.0 guidance. Most of the opportunities identified in the research were improvements in the structure and presentation of accessibility guidance to improve usability, support more disability needs, and improve maintenance.

Large and Dynamic Sites

From 128fd678faed2370b9ab7fb4d9892ce69d913ac5 Mon Sep 17 00:00:00 2001 From: Jeanne Spellman Date: Thu, 31 Mar 2022 17:53:43 -0400 Subject: [PATCH 06/11] #295 punctuation in lists --- requirements/index.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/requirements/index.html b/requirements/index.html index 29f0d36e..65a95afa 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -35,12 +35,12 @@

Introduction

Comparison to WCAG 2.x Requirements

WCAG 3.0 builds on the WCAG 2.0 Requirements of 2006. The WCAG 2.0 requirements are:

    -
  1. Ensure that requirements may be applied across technologies
    2. -
  2. Ensure that the conformance requirements are clear
    3. -
  3. Design deliverables with ease of use in mind
    4. -
  4. Write to a more diverse audience
    5. -
  5. Clearly identify who benefits from accessible content
    6. -
  6. Ensure that the revision is "backwards and forward compatible"
    7. +
  7. Ensure that requirements may be applied across technologies.
    8. +
  8. Ensure that the conformance requirements are clear.
    9. +
  9. Design deliverables with ease of use in mind.
    10. +
  10. Write to a more diverse audience.
    11. +
  11. Clearly identify who benefits from accessible content.
    12. +
  12. Ensure that the revision is "backwards and forward compatible".

WCAG 3.0 wishes to advance the WCAG 2.0 Requirements of:

    From 7a2f1bf222c461a81b1b88d96cc1d0d651a0515b Mon Sep 17 00:00:00 2001 From: Jeanne Spellman Date: Thu, 31 Mar 2022 18:10:58 -0400 Subject: [PATCH 07/11] #295 Changed ul to be one comma separated sentence. Changed ol to be sentence structure for each item. --- requirements/index.html | 52 ++++++++++++++++++++--------------------- 1 file changed, 26 insertions(+), 26 deletions(-) diff --git a/requirements/index.html b/requirements/index.html index 65a95afa..094946c8 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -11,9 +11,9 @@

    The Requirements for WCAG 3.0 document is the next phase in the development of the next major upgrade to accessibility guidelines that will be the successor to Web Content Accessibility Guidelines (WCAG) 2 series. The Silver Task Force of the Accessibility Guidelines Working Group and the W3C Silver Community group have partnered to incubate the needs, requirements, and structure for the new accessibility guidance. To date, the group has:

      -
    1. Researched accessibility guidance needs
      2. -
    2. Developed problem statements and opportunities to improve accessibility guidance
      3. -
    3. Received input from industry leaders for directions to proceed
      4. +
    4. Researched accessibility guidance needs.
      5. +
    5. Developed problem statements and opportunities to improve accessibility guidance.
      6. +
    6. Received input from industry leaders for directions to proceed.
    7. Drafted these high-level requirements for the next phase of the project, the prototyping and public input.
    @@ -43,19 +43,19 @@

    Comparison to WCAG 2.x Requirements

  1. Ensure that the revision is "backwards and forward compatible".

WCAG 3.0 wishes to advance the WCAG 2.0 Requirements of:

-
    -
  1. applied across technologies
    2. -
  2. clear conformance
    3. -
  3. ease of use
    4. -
  4. diverse audience
    5. -
  5. identify who benefits
    6. -
+
    +
  • applied across technologies,
    • +
  • clear conformance,
    • +
  • ease of use,
    • +
  • diverse audience, and
    • +
  • identify who benefits.
    • +

WCAG 3.0 does not want to advance the WCAG 2.0 requirement: "Ensure that the revision is 'backwards and forward compatible'" . The intention is to include WCAG 2.x content, but migrate it to a different structure and conformance model.

The WCAG 2.1 Requirements are very specific to WCAG 2.1 and will not be advanced by WCAG 3.0. WCAG 3.0 plans to migrate the content of WCAG 2.1 to WCAG 3.0, but the WCAG 2.1 Requirements document referred to structural requirements which are specific to WCAG 2.x.

The WCAG 2.1 Requirements are:

    -
  1. Define a clear conformance model for WCAG 2.1/dot.x releases
    2. -
  2. Ensure the conformance structure utilizes the WCAG 2.0 A / AA / AAA model
    3. +
  3. Define a clear conformance model for WCAG 2.1/dot.x releases.
    4. +
  4. Ensure the conformance structure utilizes the WCAG 2.0 A / AA / AAA model.
@@ -65,12 +65,12 @@

WCAG 3.0 Scope

  • Disability Needs: An improved measurement and conformance structure that includes guidance for a broad range of disabilities. This includes particular attention to the needs of low vision and cognitive accessibility, whose needs don't tend to fit the true/false statement success criteria of WCAG 2.x.
  • Emerging Technologies: Flexibility to include emerging technologies, such as augmented/virtual reality(AR/VR/XR) and voice assistants
  • Support for the Technologies that Impact Accessibility: Advice for all levels of the accessibility technology stack who wish to support the WCAG 3.0 core Guidelines including:
      -
    • digital content, including guidance currently addressed by WCAG 2.x
      • -
    • authoring tools, such as content management systems
      • -
    • user agents, such as browsers and media players
      • -
    • assistive technologies, such as screen readers, screen magnifiers, and assistants for memory, organization, or simplification
      • -
    • software and web applications, including mobile apps
      • -
    • operating systems and other platforms who may want advice for features to better support people with disabilities
      • +
    • digital content, including guidance currently addressed by WCAG 2.x;
      • +
    • authoring tools, such as content management systems;
      • +
    • user agents, such as browsers and media players;
      • +
    • assistive technologies, such as screen readers, screen magnifiers, and assistants for memory, organization, or simplification;
      • +
    • software and web applications, including mobile apps; and
      • +
    • operating systems and other platforms who may want advice for features to better support people with disabilities.
    • @@ -98,10 +98,10 @@

    Opportunities for WCAG 3.0

    Usability

    • Readable: When guidelines are easier to read and understand, users – especially people in the development cycle who are less technical – are more likely to implement accessibility. When all audiences are considered in the language and terminology used in the guidelines, the likelihood increases that they will:
        -
      • reach a larger audience
        • -
      • be better understood
        • -
      • be easier to translate
        • -
      • be interpreted as easier to implement
        • +
      • reach a larger audience,
        • +
      • be better understood,
        • +
      • be easier to translate, and
        • +
      • be interpreted as easier to implement.
    • On-ramp for Beginners: When beginning users can develop understanding and mastery of the accessibility guidance, this leads to faster and greater acceptance of accessibility. This also creates the opportunity to convince developers and project managers to include accessibility at the beginning of a project instead of the end.
      • @@ -198,7 +198,7 @@

      Scope

      Change Log

      Changes Prior to First Public Working Draft

      -
        +
        1. Moved the Opportunity for Evolving Technologies to Maintenance; added new opportunity for Flexibility in the Conformance section; and minor grammar corrections. (9 July 2018)
        2. Added headings to individual requirements (25 June 2018)
        3. Added section on Comparison to WCAG 2.x (25 June 2018)
          4. @@ -214,16 +214,16 @@

          Changes Prior to First Pu
        4. Clarify the broader definition of "disabilities" based on input from public comments and group discussion. The definition sentence in the Introduction paragraph is a proposal for group discussion.
        5. Change "future" to "unanticipated" in Requirements #2 and add subsequent sentence.
        6. Change the Requirements Intro paragraph to remove the specific sentence on conformance and pass/fail tests and give greater context on the source of the Requirements.
          7. -

      +

      Changes Prior to Second Version of Requirements

      -
        +
        1. New requirements for Readability, Regulatory Environment, Motivation, and Scope.
        2. Added paragraph explaining the differences between Design Principles and Requirements as a result of requests from the AGWG face-to-face meeting of 11 and 12 March 2019.
        3. Added new Design Principles and Requirements and changed wording of existing Design Principles and Requirements based on feedback from AGWG in Q1 and Q2 2019
        4. Added a new Scope section to the Introduction that clarifies that WCAG 3.0 plans to address Authoring Tools, User agents and Apps. (26 April 2019)
        5. Reworded Technology Neutral to bring it more in line with the original WCAG 2.0 Requirements wording. (26 April 2019)
        6. changed Design Principle 9 to more clearly show that there will not be a hierarchy of disabilities and that when there is no research, how we will address that.
          7. -
      +
    From 1880f998bac9e093c0c8f76b9ecf6d8b6159aaea Mon Sep 17 00:00:00 2001 From: Jeanne Spellman Date: Thu, 31 Mar 2022 18:13:19 -0400 Subject: [PATCH 08/11] #293 --- requirements/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements/index.html b/requirements/index.html index 094946c8..dd8d3f6f 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -30,7 +30,7 @@

    Introduction

  • explains what causes these barriers and who they impact, and
  • suggests how the problems they pose can be solved.
    • -

    The Web Content Accessibility Guidelines (WCAG) 2.0 were designed to be technology neutral, and has stayed relevant for over 10 years. The Authoring Tool Accessibility Guidelines (ATAG) 2.0 has been implemented in the open source authoring tool communities (chiefly Wordpress and Drupal) with little known uptake in commercial authoring tools. UAAG 2.0 offers useful guidance to user agent developers and has been implemented on an individual success criterion basis. There is no known user agent that has implemented all of UAAG 2.0.

    +

    The Web Content Accessibility Guidelines (WCAG) 2.0 were designed to be technology neutral, and has stayed relevant for over 10 years. The Authoring Tool Accessibility Guidelines (ATAG) 2.0 has been implemented in the open source authoring tool communities (chiefly Wordpress and Drupal) with little known uptake in commercial authoring tools. User Agent Accessibility Guidelines (UAAG) 2.0 offer useful guidance to user agent developers and has been implemented on an individual success criterion basis. There is no known user agent that has implemented all of UAAG 2.0.

    Comparison to WCAG 2.x Requirements

    WCAG 3.0 builds on the WCAG 2.0 Requirements of 2006. The WCAG 2.0 requirements are:

    From 38871a621f1d002434b5da8dda1a2424f2a431ab Mon Sep 17 00:00:00 2001 From: Jeanne Spellman Date: Thu, 31 Mar 2022 18:21:45 -0400 Subject: [PATCH 09/11] #292 - singular guidelines I also removed all the "The" before the guideline names as required in Manual of Style. --- requirements/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements/index.html b/requirements/index.html index dd8d3f6f..d0cd7080 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -30,7 +30,7 @@

    Introduction

  • explains what causes these barriers and who they impact, and
  • suggests how the problems they pose can be solved.
    • -

    The Web Content Accessibility Guidelines (WCAG) 2.0 were designed to be technology neutral, and has stayed relevant for over 10 years. The Authoring Tool Accessibility Guidelines (ATAG) 2.0 has been implemented in the open source authoring tool communities (chiefly Wordpress and Drupal) with little known uptake in commercial authoring tools. User Agent Accessibility Guidelines (UAAG) 2.0 offer useful guidance to user agent developers and has been implemented on an individual success criterion basis. There is no known user agent that has implemented all of UAAG 2.0.

    +

    Web Content Accessibility Guidelines (WCAG) 2.0 was designed to be technology neutral, and has stayed relevant for over 10 years. Authoring Tool Accessibility Guidelines (ATAG) 2.0 has been implemented in the open source authoring tool communities (chiefly Wordpress and Drupal) with little known uptake in commercial authoring tools. User Agent Accessibility Guidelines (UAAG) 2.0 offers useful guidance to user agent developers and has been implemented on an individual success criterion basis. There is no known user agent that has implemented all of UAAG 2.0.

    Comparison to WCAG 2.x Requirements

    WCAG 3.0 builds on the WCAG 2.0 Requirements of 2006. The WCAG 2.0 requirements are:

    From 7f06e6cc6261669461f5c673fdd986f240ba84cf Mon Sep 17 00:00:00 2001 From: Jeanne Spellman Date: Thu, 31 Mar 2022 18:29:32 -0400 Subject: [PATCH 10/11] #290 - abstract plain language Also fixed the first acronym use of WCAG3 --- requirements/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements/index.html b/requirements/index.html index d0cd7080..1ff1f4cc 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -9,7 +9,7 @@
    -

    The Requirements for WCAG 3.0 document is the next phase in the development of the next major upgrade to accessibility guidelines that will be the successor to Web Content Accessibility Guidelines (WCAG) 2 series. The Silver Task Force of the Accessibility Guidelines Working Group and the W3C Silver Community group have partnered to incubate the needs, requirements, and structure for the new accessibility guidance. To date, the group has:

    +

    The Requirements for W3C Accessibility Guidelines (WCAG) 3.0 documentation is the next phase of development of the next major upgrade to accessibility guidelines. WCAG 3.0 will be the successor to the Web Content Accessibility Guidelines (WCAG) 2 series. The Silver Task Force of the Accessibility Guidelines Working Group and the W3C Silver Community group have partnered to incubate the needs, requirements, and structure for the new accessibility guidance. To date, the group has:

    1. Researched accessibility guidance needs.
    2. Developed problem statements and opportunities to improve accessibility guidance.
      3. From 5010559fae6c8e0c3dd16af149ffec865e36040d Mon Sep 17 00:00:00 2001 From: Alastair Campbell Date: Tue, 20 Feb 2024 15:32:11 +0000 Subject: [PATCH 11/11] Update requirements/index.html --- requirements/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements/index.html b/requirements/index.html index 1ff1f4cc..63b036da 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -113,7 +113,7 @@

      Usability

      Conformance Model

      There are several areas for exploration in how conformance can work. These opportunities may or may not be incorporated. They need to work together, and that interplay will be governed by the design principles

        -
      • Measurable Guidance: Certain accessibility guidance is quite clear and measurable. Others, far less so. Some needs of people with disabilities, especially cognitive and low vision disabilities, are not well served by guidance that can only be measured by a true/false statement. If we allow Multiple means of measurement, in addition to true/false statements, then we may include new accessibility guidance that benefits groups that may have been underserved in the past.
        • +
      • Measurable Guidance: Certain accessibility guidance is quite clear and measurable. Others, far less so. Some needs of people with disabilities, especially cognitive and low vision disabilities, are not well served by guidance that can only be measured by a true/false statement. If we allow multiple means of measurement, in addition to true/false statements, then we may include new accessibility guidance that benefits groups that may have been underserved in the past.
      • Task-Based Assessment: Moving away from strictly web pages and web sites as a collection of web pages, WCAG 3.0 could set the scope of conformance as a comprehensive set of tasks defined by the author of the site or application. A properly marked up button doesn't help anybody if the user can't complete the task at hand. Task-based assessment allows flexibility for the conformance of complex applications that are not conducive to component/tag assessment or full-page assessment.
      • Accessibility Supported: As technologies evolve, the interoperability of content, user agents, and assistive technology will continue to blur. Interoperability may be affected by any number of factors outside of the control of the author and publisher of digital content. WCAG 3.0 can include advice to user agents and assistive technology developers. Authors are not responsible for interoperability problems beyond a reasonable effort.