[X] Team name, product name, and feature name have been added to the title of this issue.
[X] 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?
David Kennedy
Use of color and color contrast checks
[X] All text of 20px or smaller has a 4.5:1 contrast ratio to its background (or better)
[X] All text of 20px or larger has a 3:1 contrast ratio to its background (or better)
[X] Non-text elements have a 3:1 contrast ratio to their background and to neighboring elements (or better)
[X] Color is not the only way to distinguish links from other text (eg. links are underlined)
[X] Any charts, maps, infographics, and tables convey all information without only relying on color
[X] Content does not refer to color, especially when providing user instructions (eg. "Click the blue button")
How did color testing go?
No issues here. Using the standard design system components and no additional elements.
Who completed the axe scans?
David Kennedy
axe checks
[X] Each page has been scanned using axe (results shared below)
[X] axe is integrated into your end-to-end testing
axe DevTools scan results
No issues found.
How did axe testing go?
Also tested with HeadingsMap tool to scan for proper heading structure. No issues there either. Lastly, I did some testing with the ARC Toolkit accessibility scanner on pages. I found a few issues with design system components and stray aria-describedby attributes. I'll file those tickets separately with the design system, and link them here when done.
Who completed the content zoom and reflow test?
David Kennedy
Content zoom and reflow checks
[X] All page elements are readable and usable at 200% zoom
[X] All page elements are readable and usable at 300% zoom
[X] All page elements are readable and usable at 400% zoom
How did content zoom and reflow testing go?
No issues found.
Who completed the keyboard navigation test?
David Kennedy
Keyboard navigation checks
[X] Each link, button, form input, checkbox, radio button, select menu, and custom element can receive keyboard focus
[X] Each link, button, form input, checkbox, radio button, select menu, and custom element responds to expected keys
[X] All elements under focus have a visible focus indicator
[X] The order of [Tab] stops made sense and was appropriate for completing tasks
How did keyboard testing go?
No issues found.
Do you have any other results to share?
I did screen reader testing with Safari and VoiceOver on Mac and Chrome and JAWS on Windows. No issues discovered there.
davidakennedy
commented
1 month ago
Product information
Who completed the use of color and color contrast test?
David Kennedy
Use of color and color contrast checks
How did color testing go?
No issues here. Using the standard design system components and no additional elements.
Who completed the axe scans?
David Kennedy
axe checks
axe DevTools scan results
No issues found.
How did axe testing go?
Also tested with HeadingsMap tool to scan for proper heading structure. No issues there either. Lastly, I did some testing with the ARC Toolkit accessibility scanner on pages. I found a few issues with design system components and stray
aria-describedbyattributes. I'll file those tickets separately with the design system, and link them here when done.Who completed the content zoom and reflow test?
David Kennedy
Content zoom and reflow checks
How did content zoom and reflow testing go?
No issues found.
Who completed the keyboard navigation test?
David Kennedy
Keyboard navigation checks
How did keyboard testing go?
No issues found.
Do you have any other results to share?
I did screen reader testing with Safari and VoiceOver on Mac and Chrome and JAWS on Windows. No issues discovered there.