7.3 new note language for notes 1 and 3

in response to comments from others to EN 301 549

the following note language is being proposed for  7.3

if you have any issue with it  please respond to all ASAP..

Gregg


Note 1:  Media players would meet the precondition of this requirement because their primary purpose is to play audiovisual materials, but a preview feature in a file utility that shows quick views in a pop-up of the contents of files as you select them, (including playing a video file in the popup without controls) would not, because its primary function is file management, and the primary function of the preview function is to let you peek into any type of file to identify it, not view AV.

Note 2:  (no change)

Note 3:  change  “by default”  to  “when the ICT is turned on” so it read   (and change   “mechanisms” to  “a mechanism"

Note 3: It is best practice for ICT to include a mechanism to enable the user to select whether subtitles or other accessibility features are turned on or off when the ICT is turned on.



==================================================================
FOR CONVENIENCE  here is the language for 7.3  BEFORE the above edits


7.3          <>User control of audiovisual accessibility features <>
Where ICT primarily displays video with synchronized audio <>, and has control over the activation of subtitles and or audio description,
the ICT shall provide at least one means of operation that allows the activation of the user’s choice of either subtitles or audio description with a single user operation <applewebdata://06E2AF5C-35C0-4092-8519-6B71E669F263#singleuseroperation> that is at the same level as the volume control and that meets the other accessibility requirements of the present document.

NOTE 1: Media players are ICT that primarily display video with synchronized audio. <>
NOTE 2:  It is best practice to allow other accessibility features to also be chosen with a single user operation.

NOTE 3:    It is best practice for ICT to include mechanisms to enable the user to select whether subtitles and other accessibility features are turned on or off by default.

NOTE  4:    There could be separate methods for activating and deactivating these functions.

NOTE 5: The ability to use spoken commands is best practice to include because it makes it possible to have all accessibility functions available instantly, but since all speech control also requires a non-speech alternative (clause 5.1.7) it cannot be the only method for meeting clause 7.3.

EXAMPLE:       One solution would be to have a single button at the volume control level, bring up a list of accessibility features if it was held down for more than 2 seconds.  The user could activate any accessibility feature from that menu - as well as chose an accessibility feature that would be turned on and off with a single short press of the same button that was used to bring up the menu with a long press. (If this was standardized across manufacturers it would facilitate dissemination of information about this feature and provide cross-manufacturer consistency) .   It is best practice to have a dedicated button for doing the above (providing single button to both chose and then later activate the single chosen function with a simple press),  but a button that exists in a current design, like the mute button,  could be repurposed for this where a remote has only a few buttons and a dedicated button cannot be provided.