terrill
commented
6 years ago @DBDeveloper87 thanks for your feedback. You've offered us a lot to consider! If you feel particularly strongly about one or more of these issues, I suggest creating a new issue focused exclusively on that issue. That way it will be easier to focus the conversation. Meanwhile, three of the issues you raised are particularly interesting to me, so I've offered responses to them below:
- Regarding the inability to start the video using chord-1,5,6: I have only limited experience with Braille input devices, but I believe that chord command is the one used to toggle play and pause within the iOS native player, correct? If so, Apple has specifically built support for that and many other Braille commands into iOS. These commands only work for native iOS apps though, not for websites. Able Player is an HTML5 media player that's built into web pages, so it can't be operated in the same way that accessible iOS apps can. In order to build in control for Braille commands, we would need to have Braille event listeners, and to my knowledge those don't currently exist. Why not? I don't know the answer to that, but it seems like an issue worthy of discussing.
- Regarding captions not being accessible through the iOS 11 Braille captions feature: Again, that's a feature that's probably built for the iOS media player, but I suspect it doesn't support video that's embedded into a web page, although I could be wrong about that. The Able Player demo pages includes one page that features the browser's native HTML5 video player, for comparison. Does the Braille caption feature work with the Native Browser Player Demo?
- Regarding the short phrases that comprise the interactive transcript as you experience it on a Braille device: That's because the transcript is assembled from timed text files (it parses the chapters, descriptions, and captions files and combines them into a transcript). Each individually caption is wrapped in a
<span>tag, which is what makes the transcript interactive (if the user clicks on a phrase it jumps to that point in the video.) I suspect you're getting just one span at a time, which is essentially one caption at a time, rather than a flowing stream of text. Is there a setting within your Braille device that would cause it to read everything more seamlessly (sort of like word wrap)? If not, I could add a Preference or feature to Able Player that would strip out all the<span>tags. However, that would also strip out the interactivity, and just leave you with a static transcript. Not necessarily a bad idea though.
DBDeveloper87
In testing Able Player with iOS VoiceOver using the examples page, especially the text-based audio descriptions example, I have found there are some issues with the player. Your documentation states that iOS plays in the OS's default player instead of the actual Able Player; however, this does not appear to be the case on IOS 11.4. Instead, it plays inside the actual Able Player. Issues I found: --I cannot start the video using chord-1, 5, 6; rather I have to physically navigate to the play button first. After that I can play/pause using this chord on a Braille display. --Capations do not appear to be accessible through the iOS 11 Braille captions feature. --If the settings are set to automatically pause the tape whenever auto-descriptions are active, I can navigate to the AD itself and read it. --Interactive Transcript did not want to appear at first, I had to invoke the button twice or thrice via the routing keys. Combining the captions/subtitles with the audio-descriptions through this Transcript is quite easy to read via the Braille display. --Invoking Full Screen means I can no longer access the player UI via the Braille display and it only expands to fit the Safari window but the top nav bar of Safari and bottom nav bar are still visible. I was forced to reload to go back to the non-full screen interface. --Regarding Interactive Transcripts. While the appear like "blocks" on the visual interface (almost like paragraphs), this is not the case on a Braille display. The whole block is not displayed across the full 40 cells, instead only two or three words usually appear if it is from the captions/subtitles portion. Audio Descriptions render correctly. In my experience with improving documents for VoiceOver, this is because the paragraph appears to VoiceOver as being broken up into different elements. I found copying and pasting it into TextEdit, then back into the Word processor application and applying the approiipate styling fixed that issue. So I think VoiceOver is reading the array of strings that make up the block of text as individual elements instead of a block. Perhaps using a function that converts that array of strings into a full, single string would fix this issue.