Previewer metadata - Missing 'Captions and subtitles' info for an .mp3 resource

[pcenov]

Observed behavior

The 'Captions and subtitles' info for an .mp3 resource is not being displayed in the previewer. This is working correctly for .mp4 files.

Expected behavior

Unless otherwise specified the 'Captions and subtitles' metadata should be displayed as specified in Figma.

Steps to reproduce the issue

1. Go to https://hotfixes.studio.learningequality.org/en/accounts/#/ and sign in
2. Open a channel with an .mp3 resource with added captions and subtitles and click the resource to see the previewer.
3. Observe the lack of 'Captions and subtitles' data

Additional information

Usage Details

• OS: Windows 10, Ubuntu
• Browser: Chrome, Firefox
• URL: https://hotfixes.studio.learningequality.org/

[pcenov]

@radinamatic

[radinamatic]

In addition, the edit modal for audio files is missing the section with the option to add the accessibility metadata, that is to correctly annotate the audio resource which is accessible because it has the VTT file with captions.

Technically, audio resource could have the sign language captions too, but then it would become a video, and I'm unsure if our current architecture supports that 🙂
So for the time being let's fix the missing ability to add the proper accessibility metadata for the audio files.

cc @bjester for the patch/iteration planning.

[bjester]

I did bring up that the 'Has captions or subtitles' accessibility option could apply to audio as well, but the product feedback I received was that the option was focused on videos given its textual description and that a 'Has transcript' option would be better suited for audio. Therefore this is working as it was intended from the product perspective.

[radinamatic]

Thanks for the background info, can't say I recall that conversation 🤔

As it stands now, we do not have the Has transcript accessibility metadata category, and for the user who needs this feature, the difference between captions and transcript is trivial. Having neither is an accessibility barrier, therefore I don't see the reason NOT to have the captions option just because the transcript could be seen as slightly better.

Moreover, the feature to display available captions as an interactive transcript is of your own making, so where exactly is the problem? 🙂

Actually, we do have a (bigger) problem, as the videoJS implementation for audio files in both Studio and Kolibri does not seem to display the captions even when the VTT file is uploaded in the edit modal. Big faux pass, how did I miss that...??? 😞

[bjester]

Yes, I understand we don't have a Has transcript label. If it is indeed better, which it seems so, then it's best we go the route of adding the new label. It's prudent because once we migrate everything, we won't know the difference between something a user explicitly set versus something we migrated to have the label, meaning it isn't alterable.