Quality in Use report Jan 2018: Identified issues and recommendations

1

Does not work in IE 11 -> The site would not load and sign in failed. This lack of access could affect between 7-12% of desktop users (the figures of IE usage vary enormously depending on the method used for calculating the statistics). According to a US based Webaim survey of screen reader users, 23% are still working with IE11 with around 4% using older versions of IE and only 0.5% using Edge.

Issue

(Issue: does not fail gracefully… blank screen)

2

Slide content should adjust correctly to Browser zoom function (up to 200%)

Other components must resize accurately (e.g. header)

Issues

3

Keyboard trap when tab into speaker notes on slide view

Issues

4

Zoom in edit mode -> edited content must also zoom when browser zoom up to 200%

Issues

5

Autosave feature

Improvement

6

Undo/redo in edit mode

7

Autcomplete on search box not read aloud / accessible. However, search is functional by typing in the term.

Improvement

8

reader/keyboard only user is currently unable to reach the Google+ or Github buttons so has to sign up using email and a password

Issue (minor)

9

User management button popup menu appears once the user selects the button. This is accessible to keyboard users, but is not read aloud to screen reader users.

Issue

SWIK-1500 - Getting issue details... STATUS

SWIK-1941 - Getting issue details... STATUS

10

Dropdown list "search selection" from semantic UI is not accessible. Use "selection" type only (and prefereably from react-semantic UI) as this type is accessible (used from themes in add-deck page

Issue

11

When a group is deleted or a settings change, then a SweetAlert message should appear and should be accessible.

Improvement

12

Keyboard only users are unable to delete members from a group as the delete button is not keyboard accessible

Issue

13

alt text on the thumbnail images to represent a deck could be improved as it currently contains the deck ID which is read out as a number by the screen reader.

Issue (minor)

14

For users choosing to upload an existing presentation, it would be helpful if there could be more feedback when the slide presentation file has not been accepted for upload.  

improvement

15

Progress as a file uploads, is not always announced to screen reader users

improvement

16

Edit deck - If users attempt to submit the form without completing compulsory fields, there is a visual warning but this is not communicated to screen reader users

Issue

17

create keyboard functionality to re-order slides so that the process does not rely on drag and drop using the mouse.

improvement / Issue

18

Edit decks -> All users are then required to select the confirm button to close the message window. Currently the message window is not announced to screen reader users.

Issue (minor)

19

20

Correct modal description for image upload 

Issue (minor)

21

Positioning of text boxes that are heard as sections, would be difficult for those with dexterity and visual impairment difficulties, so ideally a set layout with an image and a text box may be helpful, along with the other templates already provided

improvement

22

Presentation mode - accessing the first slide of the show as the screen reader may not be able to access the content unless they change the reading mode and it may not be until they reach the second slide that the content is read aloud

Issue (poss due to SW header/footing in the DOM)

23

There are shortcut keys to move between slides when in slideshow mode, making it accessible for keyboard users. However, there is the potential for these keys to conflict with screen readers and it is recommended that further work is undertaken to test and improve the navigation of slideshows by screen reader users.

improvement

24

The slideshow view does not magnify when the browser zoom function is used on a desktop computer nor will it react to pinch-zoom on a touch-screen. There is a built-in zoom function to the slideshow mode but this requires users to click via the mouse. The slideshow was found to zoom when using magnification tools and text can be re-sized using assistive technologies.

improvement

SWIK-1860 - Getting issue details... STATUS

SWIK-1852 - Getting issue details... STATUS

SWIK-1833 - Getting issue details... STATUS

25

sources, comments, slide/deck history, usage and questions.   -> All these features can be accessed and work with a screen reader, but fail to activate when used with just keyboard access and no speech output.  

Issue

26

the thumbnails of slides often appear in serif fonts

Issue

27

Colour contrast levels are not quite good enough in the top menu language item and the footer text

Issue

28

Some page titles are missing or are not unique. Headings are helpful and page structure is consistent

Issue (minor)

SWIK-2023 - Getting issue details... STATUS

SWIK-2040 - Getting issue details... STATUS

29

Several comments have been made about the ability to delete unwanted decks or forked items.  This is a complex subject as the intention of the SlideWiki platform is to enable slides to be reused, so to delete a deck that has been shared or forked could be considered problematical.  The collaboration and sharing component is a highly praised part of the Open Educational Resource element of SlideWiki, but the ability to delete decks that are redundant and have not been shared or forked (for example draft decks) needs to be addressed in the future.

improvement

30

the upload feature stops at 65% without a message appearing to tell the user that their connection speed is too slow and the upload has failed.  

improvement

31

some toolbars and graphical components need to respond to the reduced width of the screen to improve the aesthetics when viewed on small screens

responsive

SWIK-2042 - Getting issue details... STATUS

32

One user suggested they wished “…to delete the decks that do not interest me.”  Providing users with the option to delete decks that are felt to be inappropriate or not up to the required standard should be an option provided by a feedback mechanism, so that the request can be considered by a group of evaluators in a similar fashion to the system mentioned on the OER Commons repository.  

improvement

33

Ensure simultaneous edit of a deck by multiple users works appropriately.

improvement