kengdoj
commented
3 weeks ago There may be an HTML player capable of program selection available (now or in the future). I wouldn't say it’s always not applicable.
I also change 17C’s identify content guidance to say something like B or “and has controls to toggle audio descriptions.”
17.C's applicability (which is the same as 503.4.2) is not dependent on audio description controls being available:
Section 508 503.4.2 Audio Description Controls – Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.
The check for AD control is in 17.A. It's possible that 17.A passes because AD controls are provided and 17.C is not applicable because there is no program selection control.
if the “program selection” part isn’t applicable to websites, why is the text still included in the web baseline, or not addressed in a bullet in “Limitations, Assumptions, or Exceptions” section? The individual replied to my initial comment of “not applicable” with, “if it was not applicable, the baseline would have made that clear.”
I’d propose to add a bullet in the “Limitations, Assumptions, or Exceptions” section to say: Media players embedded in websites and applications are not meant to be used by the end user to play files stored on their computer, therefore the “program selection” term used in Section 508 503.4.1 and 503.4.2 are not applicable to baseline 17 B and C.
I also change 17C’s identify content guidance to say something like B or “and has controls to toggle audio descriptions.”
(Suggested by @rbenson )