Skip to content

For future consideration: Implications for removing "Check that the meaning of the content (in context) is preserved ." from test 18 #553

@KMSOC

Description

@KMSOC

Description
Currently, we propose re-writing test 18.B so that there is only one check: Check that the programmatically determined reading order and meaning of the content (in context) is correct. [SC 1.3.2]

In doing so, we remove the bifurcated check of:

  1. Check that the reading order of the content (in context) is correct. [SC 1.3.2]
  2. Check that the meaning of the content (in context) is preserved. [SC 1.3.2]

When collapsing into one check, are we losing an example that may pass test 1 but fail test 2 or vice versa?

Opening this issue to track any instances that may support keeping 2 distinct tests, one for reading order and one for meaning.

Which Baseline
To help us address your issue more effectively, please identify which Baseline has the issue:

  • All

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions