search

hackforla / CivicTechJobs

CivicTechJobs will be a platform to help prospective volunteers find interdisciplinary projects that will be useful for their career development while contributing to positive civic impact, and also a CMS (Content Mgmt System) for Hack for LA projects to be able to list their open roles.
https://civictechjobs.org
GNU General Public License v2.0
18 stars 23 forks source link

Accessibility check for CTJ MVP1 #594

Open xxl228 opened 1 month ago

xxl228 commented 1 month ago

Overview

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

Action Items

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 commented 1 month ago

@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 commented 1 month ago

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

xxl228 commented 4 weeks ago

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

rishi222k commented 3 weeks ago

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

Next Steps:

xxl228 commented 2 weeks ago

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 commented 6 days ago

@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 commented 6 days ago

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