From c476658e06932982b38f78317c68e2db3339743d Mon Sep 17 00:00:00 2001 From: fstrr Date: Fri, 2 Sep 2022 09:48:34 -0700 Subject: [PATCH 1/5] Initial commit of issue severity subgroup update Also corrected typos in two existing `id` attributes --- requirements/index.html | 45 +++++++++++++++++++++++++++++++++++++++-- 1 file changed, 43 insertions(+), 2 deletions(-) diff --git a/requirements/index.html b/requirements/index.html index 3544c05a..8328dd79 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -109,7 +109,7 @@

Usability

  • Advocacy Tool: Usability oriented toward a broad audience for WCAG 3.0 can help improve the general advocacy of digital accessibility. Improving the reach of WCAG 3.0 can help improve the awareness of accessibility considerations. Compelling information that is contextually relevant to the standards may also aid in convincing audiences of any type.
    • -
    +

    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

      @@ -118,7 +118,7 @@

      Conformance Model

    • Accessibility Supported: As the 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.
    -
    +

    Maintenance

    • @@ -130,6 +130,47 @@

      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.
    +
    +

    Issue Severity

    + +
    +

    This section is exploratory. Outstanding questions that need to be addressed include:

    +
      +
    1. What to do with non-critical issues.
      2. +
    2. How to deal with people having have different ideas on what is critical.
      3. +
    3. How do we incorporate context / process?
      4. +
    4. Can the matrix inform designation of functional categories, for example: the Text Alternative Available outcome.
      5. +
    5. How to include context/task. Is that part of scoping, or issue severity. Both are important to the end result.
      6. +
    +
    + +

    The Issue Severity Subgroup:

    + +
      +
    1. Demonstrated that it is possible to categorize tests by severity. See the critical severity worksheet for this information.
      2. +
    2. This is best done at the test level. The higher the level the impact is assessed at, the less it aligns with the experience.
      3. +
    3. It would be best to incorporate task/context for the best alignment. This does depend on scoping and how to define the task/process.
      4. +
    4. It will be a lot of work to categorize each test with an impact level and the functional needs affected. It maybe best to focus on the critical issues. It would also be best to do as we go along when creating tests.
      5. +
    5. This could contribute towards scoring, but there are many other questions to do with scoring.
      6. +
    6. This could also contribute towards prioritization, which could replace A/AA/AAA (at the test level)
      7. +
    + +
    +
    Proposed updates
    + +
      +
    • For the process of creating this: focus on critical issues. Don't try to rate high / medium / low.
      • +
    • Use the critical severity matrix to categorize tests. (At least set up that process to define each test by functional need and impact).
      • +
    • We could use Critical / High for a level of conformance. For example: +
        +
      • "Bronze" could be an absence of any critical or high issues;
        • +
      • "Silver" could be an absence of any critical, high, or medium issues.
        • +
      +
      • +
    • We could use the severity scales as input to a post-testing process where you prioritize issues based on your context and tasks.
      • +
    +
    +

    Design Principles

    From f96a941c3b0f9e5fbcfe342feb1f42b71665d265 Mon Sep 17 00:00:00 2001 From: fstrr Date: Fri, 2 Sep 2022 15:13:15 -0700 Subject: [PATCH 2/5] Add critical failures to two outcomes 1. Outcome: Text alternative available 2. Outcome: Translates speech and non-speech audio --- methods/functional-images/tests.html | 6 +++++- methods/text-equiv/tests.html | 13 ++++++------- requirements/index.html | 1 + 3 files changed, 12 insertions(+), 8 deletions(-) diff --git a/methods/functional-images/tests.html b/methods/functional-images/tests.html index 06be64b0..a564e2e5 100644 --- a/methods/functional-images/tests.html +++ b/methods/functional-images/tests.html @@ -51,7 +51,11 @@

    Procedure for Technology Agnostic

    Expected Results

    -

    Checks #2 and #3, or #2 and #4, or #2 and #5 are true.

    +
      +
    • Checks #2 and #3, or #2 and #4, or #2 and #5 are true.
      • +
    • Critical issue if #2, #3, and/or #5 is false and a functional image is needed to complete a task.
      • +
    +

    diff --git a/methods/text-equiv/tests.html b/methods/text-equiv/tests.html index cb0caad8..ff5a2d3d 100644 --- a/methods/text-equiv/tests.html +++ b/methods/text-equiv/tests.html @@ -23,19 +23,18 @@

    Atomic Tests

  • Check that the captions can be turned on and off
    • Closed captions can be turned on and off
    • Open captions cannot be turned off
      • -
    • + +

    Rating:

    -

    We want public feedback about whether Open Captions (burned in captions) pass for Bronze level. Open captions are not text and cannot be customized for people with low vision or routed to a braille display for people who are blind-deaf.

    diff --git a/requirements/index.html b/requirements/index.html index 8328dd79..2e5b30a9 100644 --- a/requirements/index.html +++ b/requirements/index.html @@ -148,6 +148,7 @@

    Issue Severity

    1. Demonstrated that it is possible to categorize tests by severity. See the critical severity worksheet for this information.
      2. +
    2. Added examples of critical failures to the tests for Text Alternative Available and Translates Speech And Non-Speech Audio.
    3. This is best done at the test level. The higher the level the impact is assessed at, the less it aligns with the experience.
    4. It would be best to incorporate task/context for the best alignment. This does depend on scoping and how to define the task/process.
    5. It will be a lot of work to categorize each test with an impact level and the functional needs affected. It maybe best to focus on the critical issues. It would also be best to do as we go along when creating tests.
      6. From c0be88cbdbf331aaa3ecc5220a19a0e4be76bf81 Mon Sep 17 00:00:00 2001 From: Sarah Horton <69357922+gradualclearing@users.noreply.github.com> Date: Mon, 5 Sep 2022 08:48:24 +0100 Subject: [PATCH 3/5] Added critical issue to expected results for all procedures --- methods/functional-images/tests.html | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/methods/functional-images/tests.html b/methods/functional-images/tests.html index a564e2e5..5d4d985f 100644 --- a/methods/functional-images/tests.html +++ b/methods/functional-images/tests.html @@ -53,7 +53,7 @@

      Procedure for Technology Agnostic

      Expected Results

      @@ -81,7 +81,11 @@

      Procedure [for HTML]

      Expected Results

      -

      Checks #1 and #2 are true

      +
        +
      • Checks #1 and #2 are true
        • +
      • Critical issue if #2, #3, or #5 is false and a functional image is needed to complete a task.
        • +
      +
      • If a functional image is not purely decorative and CSS is used instead of an img or input (type=”image”) element, that does not pass.
      • If a functional image is not purely decorative and the img or input (type=”image”) element doesn’t have an alt attribute, that does not pass.
        • @@ -101,7 +105,10 @@

        Procedure [Technology Agnostic]

      Expected Results

      -

      Checks #2 and #3, or #2 and #4, or #2 and #5 are true.

      +
        +
      • Checks #2 and #3, or #2 and #4, or #2 and #5 are true.
        • +
      • Critical issue if #2, #3, or #5 is false and a functional image is needed to complete a task.
        • +
      @@ -113,4 +120,4 @@

      Holistic Tests

      - \ No newline at end of file + From eaaffb496dd54fa1f5f021155e4f5df8a99ea9b9 Mon Sep 17 00:00:00 2001 From: Sarah Horton <69357922+gradualclearing@users.noreply.github.com> Date: Mon, 5 Sep 2022 08:53:42 +0100 Subject: [PATCH 4/5] Added one more critical issue, changed "a" to "the" --- methods/functional-images/tests.html | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/methods/functional-images/tests.html b/methods/functional-images/tests.html index 5d4d985f..fd81a29a 100644 --- a/methods/functional-images/tests.html +++ b/methods/functional-images/tests.html @@ -37,7 +37,11 @@

      Procedure for HTML

      Expected Results

      -

      Check #2 and #3 are true.

      +
        +
      • Check #2 and #3 are true.
        • +
      • Critical issue if #2 is false and the functional image is needed to complete a task.
        • +
      +

      Procedure for Technology Agnostic

      @@ -53,7 +57,7 @@

      Procedure for Technology Agnostic

      Expected Results

      • Checks #2 and #3, or #2 and #4, or #2 and #5 are true.
        • -
      • Critical issue if #2, #3, or #5 is false and a functional image is needed to complete a task.
        • +
      • Critical issue if #2, #3, or #5 is false and the functional image is needed to complete a task.

      @@ -83,7 +87,7 @@

      Procedure [for HTML]

      Expected Results