WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: EN 301 549 Video requirements discussion


From: Steve Green
Date: Sep 13, 2021 4:52PM

The solution to all these issues would be to use open captions because there are exemptions for captions that are "displayed as unmodifiable characters". Of course that would be a terrible solution, but the bad drafting of the standard forces you down that route if you want to claim full compliance.

I thought that only clause 9 applied to websites, but I can't find anything to support that assertion even though it would seem to be obvious. It is possible that other legislation that refers to EN 301 549 only requires websites to comply with clause 9. That said, the UK public sector website accessibility regulations contain no such restriction, yet the Government Digital Service interpret them as only requiring conformance with WCAG 2.1 AA.

Steve Green
Managing Director
Test Partners Ltd

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Patrick H. Lauke
Sent: 13 September 2021 19:56
Subject: Re: [WebAIM] EN 301 549 Video requirements discussion

On 13/09/2021 15:46, Jonathan Avila via WebAIM-Forum wrote:
> Hi all,
> EN 301 549 criterion 7.1.5 indicates that subtitles and captions need to be spoken. This requirement is aimed at making sure that foreign language subtitles are available to people who are blind or visually impaired. The requirement seems to use the word "sub titles" in the heading but in the actual criterion seems to state "captions" and also uses the word "captions" in Appendix C for test steps. This would seem to indicate that spoken captions could be interpreted as needed for all web content that has captions or subtitles under EN 301549 V3.1.1 (and that are programmatically available ).
> Is there any different interpretations of this requirement for web sites? Even if the requirement is for sub-titles only it would seem that you'd have to implement some approach where the sub-titles could be announced either through a button to speak them in an audio track or by using a live region to have the screen reader announce them. The latter being difficult in some situations due to timing.
> Also criterion 7.1.4 indicates that captions need to be adjustable to user settings - the criterion lists some items that can be used to contribute to meeting the criterion - but doesn't clearly state what is or is not actually required to meet it. While all of the items listed are useful including being able to change the font outline, color, size, background, and opacity - it fails to state explicitly if all of those are actually required. So it would seem that all web video players would need to support some level of customization to meet this criterion but there may be inconsistency in how it is interpreted.

Have to admit that these criteria feel very much like they were crafted for actual operating systems/hardware devices, and not much time was spent hammering out what the repercussions for web-based content would be...sigh.

Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke