Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

StepActorActionResultMobile DesignAlternate FlowAccessibility Notes
1patronlogs in and navigates to the library catalog
  • displays header/facet with 'Books' format selected by default
  • ebooks are displayed in the lanes
  • Interface can be read by a screen reader:
    • component must announce that it is a menu,
    • indicates the current selection as "books"  

 

  • displays header/facet with selectable options for:
    • Books
    • Audiobooks
  • Books is selected by default
  • ebooks are displayed
  • Selectable interface is accessible and can be read by a screen reader
    • Screen reader must announce if selected.
    • Should indicate how many selections in list, ex "Books, selected, 1 of two"
    • Selected state displays with an inner shadow as shown


Image RemovedImage Added

 

If audiobooks are turned off in the circulation manager for the library, then no entry point will exist for audiobooks. In this case, the facet/header should be hidden.

(Willa will advise if it should say "Format, books" and also display the word format somewhere so that users know what the menu is called.)

2patron

clicks header/facet button to view menu

displays menu with selectable options for:
    • Books
    • Audiobooks
  • Interface can be read by a screen reader:
    • focus should be trapped
    • announces the title of the menu
    • announces which is selected
    • Should indicate how many selections in list, ex "Books, selected, 1 of two"
   
3patronselects "Audiobooks"
  • audiobooks displays in selected state
  • audiobooks are displayed in the lanes
  • Icons must be accessible: Book format, indicated with small red icon, should also be represented as programmatically accessible text. So a screen reader would hear "title of book"+"audiobook" or "title of book"+"ebook".
  • Screen reader:
    • focus stays on the drop down component
    • announces "audiobooks selected"
 

If no audiobooks are available at a library, then UI presents a message, "Sorry, no audiobooks were found."

Image RemovedImage Added

 

When a user selects a new tab, the focus should stay on that tab (is screen reader user isn't bumped back to top of page) KW: this may not be applicable if we aren't using tabs?

When a user selects a new format, once the new books load that is announced to a user of a screen reader. Chat about best approach.

...