Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discuss options for heading text and levels on report pages #999

Closed
mcking65 opened this issue Oct 19, 2023 · 1 comment
Closed

Discuss options for heading text and levels on report pages #999

mcking65 opened this issue Oct 19, 2023 · 1 comment

Comments

@mcking65
Copy link
Contributor

mcking65 commented Oct 19, 2023

Consider the report for JAWS and Chrome for Action Menu Button Example Using aria-activedescendant.

There is a level 2 heading for each test like:

Navigate forwards to a menu button in reading mode (8 passed, 0 failed)

Under that heading is a level 3 heading with text like:

B Results: 2 passed, 0 failed

For some readers, it may not be clear that "B" is a command and what follows is the results from testing the command "B". When reporting on test plans in the V2 format, it might be a little more clear because the heading would be:

B with Virtual Cursor Active Results: 2 passed, 0 failed

Goals

Discuss heading options that will:

  • Improve clarity of content
  • Avoid increasing the amount of repetitive text in the headings

Option A

Change the level 3 heading to:

Command B: 2 passed, 0 failed

Option B

Add a new level 3 heading:

Results for each command

Then Change the level of the heading for each command to 4, keeping the same text as today:

B Results: 2 passed, 0 failed

Note, there is another level 3 heading for each test, "Run History", so there would be two level 3 headings for each test, one for results by command and one for run history.

@mcking65
Copy link
Contributor Author

CG discussed in a meeting (sorry don't have reference to minutes handy). Option b was chosen and implemented. Closing as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant