From 7b42d0c84a8ca3948afb389067ea7fd4d1a203b1 Mon Sep 17 00:00:00 2001 From: Alastair Campbell Date: Tue, 23 Jan 2024 14:48:45 +0000 Subject: [PATCH 1/4] Adding a requiement --- requirements/index.html | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/requirements/index.html b/requirements/index.html index 0e95b33b..a0e93078 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -231,9 +231,14 @@

Regulatory Environment

Motivation

The Guidelines motivate organizations to go beyond minimal accessibility requirements by providing a scoring system that rewards organizations which demonstrate a greater effort to improve accessibility.

-
-

Scope

+
+

Scope

The guidelines provide guidance for people and organizations that produce digital assets and technology of varying size and complexity. This includes large, dynamic, and complex websites. Our intent is to provide guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more.

+
+
+

Backwards compatibility

+

The WCAG 3 guidelines will not be backwards-compatible with WCAG 2.x. After the first publication of WCAG 3 guidance and conformance model the guidelines may have backwards-incompatible changes in future versions. Where there are backwards-incomptible changes, the detailed changes will be included in the publication materials so that users of the guidelines know exactly what has changed.

+
From 15c400422a4ae55eaf62b6a45b82c2a8388fcb99 Mon Sep 17 00:00:00 2001 From: Alastair Campbell Date: Tue, 30 Jan 2024 14:50:35 +0000 Subject: [PATCH 2/4] Moved the backwards compat to 2.3 --- requirements/index.html | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/requirements/index.html b/requirements/index.html index a0e93078..92cf95e8 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -128,6 +128,9 @@

Maintenance

  • Evolving Technology: WCAG 3.0 needs a flexible design that can be updated as new technologies emerge, assistive technologies improve, and changing technologies produce new barriers for people with disabilities. Accessibility guidance and all supporting documentation should anticipate common scenarios like new technology and the introduction of new modalities like surface reaction and ultrahaptics. As content technology evolves, it must be re-evaluated against assistive technology for compatibility. Likewise, as assistive technology evolves or emerges, it must be evaluated against the backward compatibility of various content technology.
  • Governance: Utilize tools that allow interested parties to predict when issues important to them are being discussed. Maintain a backlog that reflects issues along with their status.
    • +
  • + Backwards compatibility The WCAG 3 guidelines will take a cautious approach to backwards compatibility. After the first publication of WCAG 3 guidance and conformance model the guidelines may have backwards-incompatible changes in future versions. Where there are backwards-incomptible changes, the changes will be included in the publication materials so that users of the guidelines know exactly what has changed. +
    • @@ -235,10 +238,6 @@

    Motivation

    Scope

    The guidelines provide guidance for people and organizations that produce digital assets and technology of varying size and complexity. This includes large, dynamic, and complex websites. Our intent is to provide guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more.

    -
    -

    Backwards compatibility

    -

    The WCAG 3 guidelines will not be backwards-compatible with WCAG 2.x. After the first publication of WCAG 3 guidance and conformance model the guidelines may have backwards-incompatible changes in future versions. Where there are backwards-incomptible changes, the detailed changes will be included in the publication materials so that users of the guidelines know exactly what has changed.

    -
    From d87c1bce072b31e700d135c61b221ec6d00990e0 Mon Sep 17 00:00:00 2001 From: Alastair Campbell Date: Tue, 30 Jan 2024 14:52:44 +0000 Subject: [PATCH 3/4] Terminology update --- requirements/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements/index.html b/requirements/index.html index 92cf95e8..a060b53e 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -129,7 +129,7 @@

    Maintenance

  • Governance: Utilize tools that allow interested parties to predict when issues important to them are being discussed. Maintain a backlog that reflects issues along with their status.
  • - Backwards compatibility The WCAG 3 guidelines will take a cautious approach to backwards compatibility. After the first publication of WCAG 3 guidance and conformance model the guidelines may have backwards-incompatible changes in future versions. Where there are backwards-incomptible changes, the changes will be included in the publication materials so that users of the guidelines know exactly what has changed. + Backwards compatibility The WCAG 3 guidelines will take a cautious approach to backwards compatibility. After the first publication of WCAG 3 guidance and conformance model the guidelines aim to be backwards compatible. However, it will not be bound to backwards compatibility if a better, more accessible outcome can be achieved. Where there are backwards-incompatible changes, the changes will be included in the publication materials so that users of the guidelines know exactly what has changed.
    • From 5e61f45edd01d9a16b8186f05077b7629fa82ac6 Mon Sep 17 00:00:00 2001 From: Alastair Campbell Date: Tue, 30 Jan 2024 15:24:34 +0000 Subject: [PATCH 4/4] 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 a060b53e..9ffc3c5e 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -129,7 +129,7 @@

    Maintenance

  • Governance: Utilize tools that allow interested parties to predict when issues important to them are being discussed. Maintain a backlog that reflects issues along with their status.
  • - Backwards compatibility The WCAG 3 guidelines will take a cautious approach to backwards compatibility. After the first publication of WCAG 3 guidance and conformance model the guidelines aim to be backwards compatible. However, it will not be bound to backwards compatibility if a better, more accessible outcome can be achieved. Where there are backwards-incompatible changes, the changes will be included in the publication materials so that users of the guidelines know exactly what has changed. + Backwards compatibility The WCAG 3 guidelines will take a cautious approach to backwards compatibility to early versions of WCAG 3. After the first publication of WCAG 3 guidance and conformance model the guidelines aim to be backwards compatible. However, it will not be bound to backwards compatibility if a substantially more accessible outcome can be achieved. Where there are backwards-incompatible changes, the changes will be highlighted in the supplementary materials so that users of the guidelines know exactly what has changed.