search

pulibrary / pulfalight

This is an implementation of the Princeton University Library Finding Aids (PULFA) service using ArcLight
Other
7 stars 1 forks source link

Draft an accessibility quality assurance script #237

Open tpendragon opened 4 years ago

tpendragon commented 4 years ago

https://docs.google.com/document/d/1V2yPYpX-YjzZ6fUPrTyhBWlzYAIUNZE3P9EenpqPxNY/edit#heading=h.h1kbujq3z7xy is what we started writing up

jrgriffiniii commented 4 years ago

Regarding accessibility, it would be ideal if an unsighted person could be recruited for testing, and then could use only the keyboard for navigating the interfaces with a screen reader.

jrgriffiniii commented 4 years ago

Please see the usability_testing_script in the shared Google Drive for an example usability testing script.

sdellis commented 3 years ago

@hackartisan the document you posted is titled as a QA/Accessibility Script, but the title of this issue says it's a Usability Testing Script. Since these are two different things, we should be clear on the goals. Are we drafting a checklist for QA sign-off, or a list of tasks to observe users try to complete?

hackartisan commented 3 years ago

@sdellis Ah, I see now there is a discrepancy. I think what we need most is the QA / Accessibility script. I'm going to change the title of this issue. I don't know of any plans to do usability testing at this time but if there are some let's create another issue

faithc commented 3 years ago

We are planning to do usability testing as well.

kelynch commented 3 years ago

Yes, I agree that it makes sense to split out accessibility and usability testing into two separate sets of considerations. We're prioritizing accessibility needs right now, and we can be more flexible for conducting usability testing, factoring in staff availability and when the ASpace/PULFAlight switchover will take place.