Open paulhiggs opened 9 months ago
@andreastai Do you have any comments?
Thanks @jpiesing for the pointer!
@paulhiggs wrote:
We don't include accessibility information in DVB DASH and there is no requirement for the reference app to interpret this new signalling.
To demonstrate the benefits of DVB-I for inclusion it would be important that the reference client uses the extended options to signal access services. An ideal use case would be the interaction between accessibility user preference and the selection of instances of a service. For this use case it would also be good to have accessibility services/metadata in DASH streams.
<AcessibilityAttributes>
are added to some of the services in the DVB-DASH reference service list - backend/servicelists/TM-STREAM0075r1%20DVB-DASH_Reference_Streams.xml
AccessibilityAttributes are now included in Service Lists and Content Guide metadata and shown in the Reference Application
@paulhiggs Thanks for adding the accessibility metadata in the reference client.
Some comments and observations:
Some comments and observations:
- The heading Accessibility is not necessary and possibly also sometimes misleading because "Translation" subtitles are usually not seen as an access service.
The translatable accessibility label is removed in commit [paulhiggs/dvb-i-reference-client@36c1909]
- It would be better to write out the features in the detail view (e.g. "Subtitles, Spoken Subtitles, Audio Description...") rather than using icons. Icons maybe good in an overview view of the program. They are also not always recognized internationally.
Icons will be removed entirely in an upcoming update
- Information on languages should be written out instead of using acronyms (e.g. "English" instead of "eng")
Added in a few long form language names in commit [paulhiggs/dvb-i-reference-client@be1bd45]
- In international content services the subtitle purpose "translation" is usually not mentioned but the default (so just "English"). If it is for hard of hearing it is indicated as "English (hard of hearing).
- For the user the carriage and the format of the subtitles are not relevant. For demonstration purposes this may be interesting but for the general user it may be irritating. This also true for all other technical details of access services.
- I don't think that it is needed to signal to the user that a subtitle service can be used for text to speech. It is more important for the device if it can generated spoken subtitles from it (at least this my understanding)
This was just indicating the <SuitableForTTS>
value but has been removed in commit [paulhiggs/dvb-i-reference-client@d053fc8]
- The closed caption icon is used for signing but belongs to subtitles.
Signing has a specific attribite @closed
indicating that captions are closed, but subtitles use Subtitle.Purpose
. Closed caption icon is added to the subtitle information presentation in commit [paulhiggs/dvb-i-reference-client@bb4c964]
Thanks for addressing the comments @paulhiggs I will review asap.
https://github.com/paulhiggs/DVB-I-Reference-Client/commit/bff1dc597f8663fe8194e47c4c30588d958792c2 removes AudioAttributes elements that are not included in clause 6.10.10 of A177, leaving only Coding, MixType and Language
All updates above are on http://paulhiggs.ddns.net:8877/pauls/frontend/android/player.html
The commercial requirement for V&V of the Signalling of Applications for Accessibility Services states
Adding
<AccessibilityAttributes>
elements in various places should suffice. We don't include accessibility information in DVB DASH and there is no requirement for the reference app to interpret this new signalling.