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

Usability testing on EPUB #1144

Closed
9 of 12 tasks
mbakeryo opened this issue Aug 22, 2017 · 4 comments
Closed
9 of 12 tasks

Usability testing on EPUB #1144

mbakeryo opened this issue Aug 22, 2017 · 4 comments

Comments

@mbakeryo
Copy link

mbakeryo commented Aug 22, 2017

Conduct basic usability testing with 4-5 users on accessing and reading an EPUB in heliotrope.

Tasks to test:

  • finding an EPUB to read
  • launching the EPUB in the reader
  • using table of contents to get to chapter
  • paging through EPUB
  • user can identify their location within EPUB (progress indicator)
  • searching within EPUB
  • citing the EPUB and using permalink
  • changing display modes (font size, colors)
  • scroll mode
  • closing E-Book Reader

Other things to do:

  • Conduct exit interview to gather basic feedback on the experience
  • When completed, create new tickets reflecting necessary changes to the EPUB reading experience
@jmcglone
Copy link
Member

jmcglone commented Nov 13, 2017

Some initial feedback from Charleston Jury Product Development Forum:

https://docs.google.com/a/umich.edu/document/d/1PHglPUPb78pR-_7LDts95JCekKn6wLu884SWN-TGSQA/edit?usp=sharing

Tickets that resulted out of this usability testing:

Heliotrope: #1366, #1365, #1364, #1363
Cozy Sun Bear: CSB#102, CSB#101, CSB#100

@mbakeryo mbakeryo modified the milestones: Fall, Winter Dec 6, 2017
@mbakeryo mbakeryo removed the ready label Dec 6, 2017
@mbakeryo mbakeryo added the ready label Jan 31, 2018
@mbakeryo
Copy link
Author

MSU UARC activity will cover some of this.

@jmcglone
Copy link
Member

@mbakeryo is this ticket complete now that UARC is done? Do we wait until the report is delivered to close it?

@mbakeryo
Copy link
Author

@jmcglone If you feel like the actual testing we wanted was done, we could probably close this and when we get the report, create the necessary tickets.

@jmcglone jmcglone removed the ready label Feb 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants