Skip to content

Accessibility Testing for [Identity, Sign in page and sign in modal, MHV credential deprecation] #95929

Open
@claytonzook

Description

@claytonzook

Product information

  • Team name, product name, and feature name have been added to the title of this issue.
  • Team label, product label and feature label (if applicable) have been added to this issue.

Who completed the use of color and color contrast test?

@claytonzook

Use of color and color contrast checks

  • All text of 20px or smaller has a 4.5:1 contrast ratio to its background (or better)
  • All text of 20px or larger has a 3:1 contrast ratio to its background (or better)
  • Non-text elements have a 3:1 contrast ratio to their background and to neighboring elements (or better)
  • Color is not the only way to distinguish links from other text (eg. links are underlined)
  • Any charts, maps, infographics, and tables convey all information without only relying on color
  • Content does not refer to color, especially when providing user instructions (eg. "Click the blue button")

How did color testing go?

Colorblindly app doesn't seem to be working currently (it's recommended in this ticket and on the Platform page linked)

Who completed the axe scans?

@claytonzook

axe checks

  • Each page has been scanned using axe (results shared below)
  • axe is integrated into your end-to-end testing

axe DevTools scan results

No issues found

How did axe testing go?

No response

Who completed the content zoom and reflow test?

@claytonzook

Content zoom and reflow checks

  • All page elements are readable and usable at 200% zoom
  • All page elements are readable and usable at 300% zoom
  • All page elements are readable and usable at 400% zoom

How did content zoom and reflow testing go?

No response

Who completed the keyboard navigation test?

Clayton Zook

Keyboard navigation checks

  • Each link, button, form input, checkbox, radio button, select menu, and custom element can receive keyboard focus
  • Each link, button, form input, checkbox, radio button, select menu, and custom element responds to expected keys
  • All elements under focus have a visible focus indicator
  • The order of [Tab] stops made sense and was appropriate for completing tasks

How did keyboard testing go?

No response

Do you have any other results to share?

Mac VoiceOver testing seemed to all go well, scrolling the page element by element or by headers, buttons or links.

Separate of our teams product, I did notice in the footer there is a Veterans Crisis Line link, or at least it visually shows as a link, that Voiceover called out as a button. All other links in the footer call out as links. Pointing this out in case that's not meant to be, that would be an important one to make sure is set how the VA wants it to be set.

Activity

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

Metadata

Metadata

Labels

IdentityAll Identity related ticketsa11y-testingFoundational accessibility testing completed prior to a staging reviewidentity-uxsign-in-page

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions