diff --git a/requirements/index.html b/requirements/index.html index 0e95b33b..8af52ce3 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -9,11 +9,11 @@
-

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. -
  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.
@@ -30,32 +30,32 @@

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.

    +

    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:

      -
    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:

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

    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:
    • @@ -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

    @@ -98,10 +98,10 @@

    Opportunities for WCAG 3.0

    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

    @@ -241,7 +241,7 @@

    Scope

    Change Log

    Changes Prior to First Public Working Draft

    - +

    Changes Prior to Second Version of Requirements

    - +