Some changes to make the errors displayed more useful/clear/readable:
1. Add a background box that is similar the one used on the Splash Screen
- Same Transparent White Background
- Rounded Corners
- Black Text
Currently the white text is not readable on top of white slides.
2. Update the Error Text
- Error describes the "media" that did not load
- Error provides help for students
image-audio
The audio for this Storybook Page could not be loaded. Please try refreshing your browser. Contact support if you continue to have issues.
Expected audio: assets/pages/slide17.mp3
The image for this Storybook Page could not be loaded. Please try refreshing your browser. Contact support if you continue to have issues.
Expected image: assets/pages/slide17.svg
The audio and image for this Storybook Page could not be loaded. Please try refreshing your browser. Contact support if you continue to have issues.
Expected audio: assets/pages/slide17.mp3
Expected image: assets/pages/slide17.svg
Video
The video for this Storybook Page could not be loaded. Please try refreshing your browser. Contact support if you continue to have issues.
Expected video: assets/pages/slide17.mp4
I understand what the intent of the original error was, but we have to recognize these errors will occur for end users too. We can figure out what's going on while developing, and don't need to be told that our file format is wrong.
I also understand that you might not have anything in place to differentiate between audio and images. Please look into adding that functionality. It would go a long way to making sure a student knows that the error displaying is not intact an error in-itself. They might link "oh, I see the slide, the error must be wrong… and it's in the way of the slide text!" When in fact they should know the audio that goes on that Storybook Page is not loaded.
Remember how Crystal didn't understand the Table of Contents? We are thinking of users like that.