DisneyNOW Design : Test Feature

• Theming (color of background image and navigation bar) changes when hero slide updates. 
• IX: Recommend that we do not auto advance hero carousel when the component is not in view thereby eliminating the case of the background changing / motion while the user is browsing content elsewhere on the page:

Hero carousel can support a max of 10 slides.

• At the start of a user session, when user navigates to the home screen/page, hero displays first slide.
• When page is refreshed (on Web) OR user navigates away from the home screen/page and then comes back, the next programmed hero displays.

• IX: Recommend a max of 5 (NNGroup, Carousel Usability, 2013)

As a user, I want to be able to navigate to the hero I want so that I can see it.

• User can navigate back and forth through the programmed hero slides.

As a user, I want the hero to rotate so that I know there is more content to view.

• Auto-rotation should ONLY occur when hero is in view. 
• Hero slides should auto-rotate every five seconds (for web and mobile app) and seven to ten seconds (for OTT app) to the next programmed hero.
  • Notes: Time is variable. Product team would like to test auto-rotate time in QA to determine best user experience per platform.
• Auto-rotation should stop after any active user interaction (manual-rotation) with hero slides.
  • For Web, Auto-rotation should pause on hover for desktop users.
  • Auto-rotation resumes when user's mouse is not over hero.
• When hero slide rotates, the next programmed slide displays. If the last programmed slide is shown, display first slide again. 
• Hero should NOT display the first slide again UNLESS the user was on the last programmed hero slide.

IX:

• Is this same as Rie’s logic or is this an update?

• Auto-forwarding causes many usability problems (NNGroup 2013)

When in view, the hero carousel should auto-rotate every five seconds (for web and mobile app) and seven to ten seconds (for TV app) to the next programmed hero. (Time is variable and to be tested in QA.) Requirement: Auto-rotation should pause at any user interaction: focus, hover, swipe, etc, and resumes on event triggered outside the component. e.g. For Web, Auto-rotation should pause on hover for desktop users, and resumes when user's mouse is not over hero.