CivicTechJobs icon indicating copy to clipboard operation
CivicTechJobs copied to clipboard

Accessibility check for CTJ MVP1

Open xxl228 opened this issue 1 year ago • 3 comments

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/

xxl228 avatar Oct 04 '24 18:10 xxl228

@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.

nooriaali9 avatar Oct 04 '24 21:10 nooriaali9

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

xxl228 avatar Oct 06 '24 23:10 xxl228

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

xxl228 avatar Oct 11 '24 20:10 xxl228

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

rishi222k avatar Oct 15 '24 07:10 rishi222k

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.

xxl228 avatar Oct 19 '24 00:10 xxl228

@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

rishi222k avatar Nov 02 '24 01:11 rishi222k

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

xxl228 avatar Nov 02 '24 01:11 xxl228

Hey @xxl228 Have there been any updates / progress on this ticket? Please comment / move as needed!

nooriaali9 avatar Jan 31 '25 21:01 nooriaali9

Hey @nooriaali9,

We've completed the accessibility test for MVP1 (role qualifier flow) and believe this issue can be closed.

  • Based on our test results and our conversation with @xxl228 last month, we've narrowed down a final list of issues that need to be addressed for MVP1. Here’s the updated spreadsheet.
  • Lu and I are working on incorporating changes to address these issues in this iteration for MVP1.

rishi222k avatar Feb 10 '25 02:02 rishi222k