Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rendered notebook user testing - Round 2 #147

Closed
5 tasks done
isabela-pf opened this issue Jul 21, 2022 · 3 comments
Closed
5 tasks done

Rendered notebook user testing - Round 2 #147

isabela-pf opened this issue Jul 21, 2022 · 3 comments
Assignees
Labels
area: user testing 🧕🏼 STCI 🔭 type: deliverable 📦 Marks an issue as a deliverable for the grant

Comments

@isabela-pf
Copy link
Contributor

isabela-pf commented Jul 21, 2022

Summary

This is a part of the STScI collaborative rendered notebook research. We're working together to run accessibility-focused user testing on static forms of notebooks. The aim is to provide open research for the betterment of the community and to learn more about accessibility needs in all notebooks by starting with their static versions. I've been asked to open issues for these tasks in this repo for easier tracking.

The second user test will explore notebook content types. Goals for this set of tests include

  • To explore a how wide range of notebook content types are rendered, especially cell outputs
  • To better understand the rendered status of all supported notebook content types
  • To better understand what content have access to and what might be missing
  • To identify user pain points and needs for interacting with a range of content types

Acceptance Criteria

This issue may be closed when all user testing information for this round is stored in the project repo and recorded/linked in this issue.

(If you can think of something else, let me know!)

Tasks to complete

  • User testing script is completed
  • Test logistics finalized
  • All round 2 tests have been run
  • Process all round 2 test data (and store!) (PR for test 2 results.)
  • All public (and non-identifiable info) is stored in the project repo and linked as resources from jupyter/accessibility
@isabela-pf isabela-pf added the status: needs triage 🚦 Someone needs to have a look at this issue and triage label Jul 21, 2022
This was referenced Jul 27, 2022
@trallard trallard added STCI 🔭 and removed status: needs triage 🚦 Someone needs to have a look at this issue and triage labels Aug 4, 2022
@trallard trallard moved this from Todo 📬 to In Progress 🏃🏽‍♀️ in Jupyter a11y CZI grant 🚀 Aug 4, 2022
@isabela-pf
Copy link
Contributor Author

This is in progress! The test script is in progress, but I will keep this updated as we work.

@trallard
Copy link
Member

Missing - link to these resources from jupyter/accessibility

@isabela-pf
Copy link
Contributor Author

Test 2 results have been merged!

I won't close this because of the above comment that they need to be linked in jupyter/accessibility. But I will return to close it then.

@trallard trallard moved this from In Progress 🏗 to Done 💪🏾 in Jupyter a11y CZI grant 🚀 Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: user testing 🧕🏼 STCI 🔭 type: deliverable 📦 Marks an issue as a deliverable for the grant
Projects
Status: Done 💪🏾
Development

No branches or pull requests

2 participants