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

Assignment statistics are are unclear when read with a screen reader #266

Open
henrycatalinismith opened this issue Oct 15, 2022 · 0 comments · May be fixed by #279
Open

Assignment statistics are are unclear when read with a screen reader #266

henrycatalinismith opened this issue Oct 15, 2022 · 0 comments · May be fixed by #279

Comments

@henrycatalinismith
Copy link

Steps to reproduce

  1. Open an assignment.
  2. Press ⌘ + F5 to start VoiceOver.
  3. Read the assignment statistics.

Expected outcome

Each item in the list should be read as a single cohesive sentence.

995 people in target group.

0 calls made.

0 successful calls.

This falls under 1.3.1 Info and Relationships.

GIF showing VoiceOver reading each item in the list as a single cohesive item

Actual outcome

The number at the beginning and the label at the end are split into two separate pieces of content with no semantic relationship whatsoever, making for a confusing read if you can't see the visual relationships between the numbers and the text in the layout.

people in target group.

Calls made.

Successful calls.

GIF showing clunky VoiceOver interaction with twice as much keyboard usage

Severity

The success criterion covering this issue is WCAG level A – the minimum level. Most organizations aim for a conformance level of AA, which includes all level A criteria. Although it's unlikely that this issue is impeding task completion, the fact that it's a basic level A issue means it's still moderately severe.

Recommendation

This is caused by the use of <p> tags to wrap the labels, which semantically misleads the screen reader into thinking it's a separate paragraph from the number. Replacing those with <span> tags is how I produced the "Expected outcome" GIF above so that's one way to do it.

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

Successfully merging a pull request may close this issue.

1 participant