Target release	June-16
User Story	SWIK-190 - Getting issue details... STATUS
Document status	IN PROGRESS
Date	28 April 2016
Document owner	Abi James
Designer
Developers	Huw Fryer
QA
Work Package & deliverables	D4.3: First stable version of SlideWiki usable, accessible and ubiquitous user interface WP 2, 3, 4

Summary

- to present a deck as a full-screen slide show
- As a user I want to be able to present a presentation in various screen sizes, lay-outs, and using various controls/controllers.

Background and goals

This will be the main view for learners to access content. It will also be used to present content on a full screen

Assumptions

- Slides will be presented full screen with no additional information on display.
- Must be able to trigger controls such as video players, animations, external links, from within the presentation.
- Must be able to accurately present all the content entered into a slide with the authoring tool.

Requirements

#	Title	Task User Story	Importance	Notes	JIRA
1	Play	When I select play on the deck screen, presentation mode is launched in full-screen	Must have		SWIK-134 Create a prototype for SlidePresentation component
2	Progress	When I move through a desk I want to see how far I have progressed through the deck e.g. progress bar or number of slides	Should have
3	Scale	When I view a presentation on different devices (e.g. mobiles, tablets, TVs) I want to the contents to scale appropriately	Should have		SWIK-77 Handle scaling of content (different screen sizes) in slide presentation mode
4	Start	When I want to start a presentation slideshow, I press play on the deck page. The slide show should start from the current slide.	Must have
5	A11y-present	As a presenter who does not use a mouse, I need to be able to move between slides using keyboard shortcuts. As a presenter and screen-reader user, I need to be able to move between slides using keyboard shortcuts when my screen reader is running.	Must have
6	A11y-user	As a screen reader user, I want to hear the contents on the slides read aloud.	Should have	If this is not possible then a screen reader user can use the deck view to hear the slides as an alternative (but this could impact user management)
7	Exit	As a presenter I want to be able to exit a presentation quickly. Ideally through on-screen control (e.g. X button) and a keyboard option e.g. ESC	Must have
8	Jump	As a presenter I want to be able to jump to a different slide in the deck	Should have	The list of slides should differentiate between section heading slides and slides
9	Activate	As a user I want to be able to activate interactive elements within slides. I may be using a touch-screen device, mouse or a keyboard.	Must have	As well as embedded interactive elements, this also includes videos

User interaction and design

Description of fields/input/elements + validation + test scenarios

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question	Asked by	Outcome
On a small-screen, should the slide re-size but retain layout or reflow and retain font size? current practice in other tools is to re-size with fixed layout and support zoom tools	Abi James
Should presentation mode run in the same or new tab? In SW v1.0 a slide show opened in a new tab	Abi James

Question

Asked by

Outcome

On a small-screen, should the slide re-size but retain layout or reflow and retain font size?

current practice in other tools is to re-size with fixed layout and support zoom tools

Abi James

Should presentation mode run in the same or new tab? In SW v1.0 a slide show opened in a new tab

Abi James

Not Doing / future developments

Feature	Status
View speaker notes	Future development
Auto-play and timed presentations	Proposal
Like or share individual slides to social channels	Proposal
View data sources or questions related to slide	Future development
As a learner I want to be able to annotate contents within a slide	Future development

Other related tasks

Task	Relationship
SWIK-135 Discuss/Choose the best libraries for playing the presentations	sub-task

Source material for user/stakeholder feedback

Requirements (/user stories) from pilot roadmap:

Compatibility with Screen readers like Jaws and Voice Over (ACC)

Evaluation/improvements by Farid Hasanov master thesis :

None

Evaluation at UniBonn :

19. What do you find most frustrating about SlideWiki?

● Most of the comments concerned:

○ The slowness of loading slides and downloading the PDFs.

○ The incorrect rendering of slides, especially of the downloaded PDF version.

● Some comments are on the layout and organization:

○ The popups that appear on every slide click.

○ Having to scroll down the page to get the arrow to navigate to the next slide.

Browser not supported