Accessibility check for CTJ MVP1

[xxl228]

Overview

We decided to conduct a quick accessibility check on the current design of MVP1.

Action Items

• check color accessibility manually
• check font accessibility manually

The research team will check accessibility for the current design, including sign- page, and current skill matrix prototype pages, and inform designers and the rest of the product team with the findings.

Resources/Instructions

Accessibility check tool:
WebAIM
https://webaim.org/resources/contrastchecker/

detailed documentation about accessibility standard WCAG: https://webaim.org/resources/

[nooriaali9]

@xxl228 - Can this issue be assigned to just one person & the rest of the folks could be tagged as the issue continues?
We want one person to lead the whole issue.

[xxl228]

@nooriaali9 Is it better now? Please let me know how to do this correctly if it is not right. Thank you!

[xxl228]

Rishi will update the accessibility test plan in google drive. Will continue the discussion next week.

[rishi222k]

Adding all accessibility research docs on drive folder. Updated 2 docs:

• List of WCAG standards(2.2) relevant to our accessibility test (design).
• Accessibility test (design) checklist.

Next Steps:

• Review and update WCAG list and testing checklist
• Discuss on testing plan for MVP 1

[xxl228]

We will start with the checking design accessibilities of current prototype, which is the one that we are conducting usability test on, using [the guidelines that Rishi created].

Rishi will cover pages that use text, which are the select practice area pages, the rating skills pages, and the modify preference pages.
Vivian will cover pages that contains mostly non-text, which are the log-in page, the page selecting availability, and also the error message page.

[rishi222k]

@xxl228 and I conducted an accessibility test on the current prototype. We had a discussion on initial findings and results based on our prepared guidelines and outside research. We need to conduct further research on guidelines for inactive/disabled UI states

Starting a spreadsheet here to document our initial results

[xxl228]

Additional resources found on the inactive state of the components are imbedded in the spreadsheet.