Skip to content

[WCAG 2.1]: Loading Indicators need to announce themselves to screen readers without taking focus #491

Open
@1Copenut

Description

@1Copenut

Bug Report

  • I’ve searched for any related issues and avoided creating a duplicate issue.

What happened

WCAG 2.1 success criteria 4.1.3: Status Messages states that things like loading indicators need to announce themselves to assistive technology without receiving keyboard focus.

What I expected to happen

Screen readers will need to announce our Loading Indicator component without us having to manage focus. This is possible if two conditions are met:

  1. The Loading Indicator role="progressbar" is changed to role="status" on line 44
  2. The spinner always has a visual text label with it

Acceptance Criteria

  • No breaks in the current usability on vets-website
  • Unit tests updated accordingly
  • 0 axe-core violations in the unit tests

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    508-issue-cognitionCognitive considerations - https://developer.paciellogroup.com/blog/2018/03/wcag-2-1-success-criteri508-issue-focus-mgmtFocus Management - https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.htmla11y-defect-3Medium-severity accessibility issue that should be fixed within 1 - 3 sprintsaccessibilityAny Section 508 or accessibility issuecomponent-updateChange to an existing component

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions