- From: John Foliot <john.foliot@deque.com>
- Date: Thu, 8 Feb 2018 17:37:04 -0600
- To: Jim Allan <jimallan@tsbvi.edu>
- Cc: W3C WAI Accessible Platform Architectures <public-apa@w3.org>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>, Nigel Megitt <nigel.megitt@bbc.co.uk>
- Message-ID: <CAKdCpxx3pj5nwc8JqF_+dVGy7ph4h1zPP0uR50YdBv-gV-eUVQ@mail.gmail.com>
Hi Jim, I just tested that Brightcove video on my Samsung Note 8, and I *was* able to enlarge the captions on my device. FWIW. JF On Feb 8, 2018 4:23 PM, "Jim Allan" <jimallan@tsbvi.edu> wrote: > comments inline > > On Thu, Feb 8, 2018 at 3:28 PM, John Foliot <john.foliot@deque.com> wrote: > >> Hi Jim & LVTF, >> >> Thanks for this - much appreciated. >> >> I was able to find a live instance of the Brightcove player with the >> caption settings control (click on the CC button to expand the menu), and >> was pleasantly surprised to see it supported magnification up to 400% - >> woot woot!! >> > another plus for me is seeing > > an implementation (several) of UAAG 1.1.6 Use Configurable Text for > Time-based Media Captions: and 1.1.7 Allow Resize and Reposition of > Time-based Media Alternatives (https://www.w3.org/TR/UAAG20/ > #gl-access-alternative-content) > >> >> Q: while SC 1.4.4 excludes captions specifically, would 'magnified >> captions' be covered by SC 1.4.10 Reflow, even if indirectly? >> > > Hmm... that's interesting. We did not call out or specifically remove > captions, however browser zoom does not impact captions much. they grow > with with video when zoomed. In my testing with zoom and youtube the 400% > captions created by the player were significantly larger than zooming the > video. different mechanisms and perhaps different user agents. How ever, > at least in youtube, if I change the setting to make captions 400% they > wrap automagically! double WOOT!! > I think in answer to your question... perhaps indirectly. different > mechanism. the permutations are complicated. sticking with youtube... > browser at 100%, video is roughly 25% of the screen. captions default to > 100%. If I go to full screen video goes to 200%, and captions get a bit > bigger - doesn't look 200%.- I didn't get out my ruler. I can still go into > the player settings and change the captions to 200%. The already larger > captions (because of full screen) will now double in size. I could go on... > but too many variables. The bottom line is - You don't lose content and > you don't scroll horizontally - so it works like it should. > I thought this would be a boon for mobile. alas no. there are no settings > for captions other than on/off in the app or desktop view. One hopes soon. > Today the desktop.... tomorrow the phone! > >> >> @nigel, have you seen this? >> >> - Press Release: https://www.3playmedia.com/2014/05/09/brightcove- >> responds-user-control-mandate-launching-customizable-closed-captions/ >> <https://www.3playmedia.com/2014/05/09/brightcove-responds-user-control-mandate-launching-customizable-closed-captions/> >> - Live Example: https://www.3playmedia.com/solutions/features/ >> integrations/brightcove-integration/ >> <https://www.3playmedia.com/solutions/features/integrations/brightcove-integration/> >> >> >> JF >> >> On Thu, Feb 8, 2018 at 2:49 PM, Jim Allan <jimallan@tsbvi.edu> wrote: >> >>> Hi John, >>> We had a good discussion about this today on the LVTF call [1]. >>> The LVTF does not believe that author testing with screen magnification >>> will have any benefit for users. Screen magnification software will >>> pixelate captions as it does the video and pictures. We don't know of >>> anything the author could do to the captions that would prevent the >>> pixelation. >>> >>> It seems the issue has been taken over by laws and technological >>> advancements because of CVAA and 2014 FCC rules mandating user control of >>> caption adjustments [2]. As examples, see 3PlayMedia's discussion of user >>> interface controls for caption adjustments [3] and YouTubes caption >>> settings [4]. Users are able to adjust captions to a significant degree. >>> >>> 1. https://lists.w3.org/Archives/Public/public-low-vision-a1 >>> 1y-tf/2018Feb/0014.html >>> 2. http://www.fcc.gov/document/closed-captioning-quality-rep >>> ort-and-order-declaratory-ruling-fnprm >>> 3. https://www.3playmedia.com/2014/05/09/brightcove-responds >>> -user-control-mandate-launching-customizable-closed-captions/ >>> 4. https://support.google.com/youtube/answer/100078?co=GENIE >>> .Platform%3DDesktop&hl=en >>> >>> Jim Allan, Chair Low Vision Task Force. >>> >>> On Wed, Feb 7, 2018 at 2:46 PM, John Foliot <john.foliot@deque.com> >>> wrote: >>> >>>> (copying the WCAG Low Vision TF) >>>> >>>> All, >>>> >>>> As you are possibly aware, we are currently closing off some old >>>> comments with the VTT Working Group (with spill-over to the TTML / IMSC >>>> Working Group) around the ability to enlarge caption text to support Low >>>> Vision users. >>>> >>>> Sylvia Pfeiffer responded with the following: >>>> >>>> If I understand correctly, you'd like me to add authoring guidance >>>> around magnification and its potential impact. >>>> >>>> Could it be done with a single paragraph such as: >>>> *"Authors of WebVTT caption and subtitle files are encouraged to test >>>> the rendering of their files using Assistive Technology. Specifically, the >>>> use of magnification tools by low-vision users may require editing their >>>> files to allow for sufficient space within cue lines and cue line heights. >>>> It is recommended to allow for a 200% magnification without clipping."* >>>> >>>> My personal opinion is that this is effectively what we seek (Ref: WCAG >>>> SC 1.4.4 Resize Text), but before I respond more formally to the GitHub >>>> issue (https://github.com/w3c/webvtt/issues/426) I'd welcome some >>>> feedback. >>>> >>>> LVTF, does this sound right? LV members, have you encountered something >>>> like this previously? (the ability to enlarge caption files independent of >>>> the video?) >>>> >>>> APA - are we comfortable with Sylvia's proposal? Would something like >>>> this also meet our needs with the TTML / IMSC group? >>>> >>>> Given that the VTT WG are keen on disposing with all comments, I'd like >>>> to try and resolve this one fairly quickly. >>>> >>>> Thoughts? >>>> >>>> JF >>>> -- >>>> John Foliot >>>> Principal Accessibility Strategist >>>> Deque Systems Inc. >>>> john.foliot@deque.com >>>> >>>> Advancing the mission of digital accessibility and inclusion >>>> >>> >>> >>> >>> -- >>> Jim Allan, Accessibility Coordinator >>> Texas School for the Blind and Visually Impaired >>> 1100 W. 45th St., Austin, Texas 78756 >>> <https://maps.google.com/?q=1100+W.+45th+St.,+Austin,+Texas+78756&entry=gmail&source=g> >>> voice 512.206.9315 <(512)%20206-9315> fax: 512.206.9452 >>> <(512)%20206-9452> http://www.tsbvi.edu/ >>> "We shape our tools and thereafter our tools shape us." McLuhan, 1964 >>> >> >> >> >> -- >> John Foliot >> Principal Accessibility Strategist >> Deque Systems Inc. >> john.foliot@deque.com >> >> Advancing the mission of digital accessibility and inclusion >> > > > > -- > Jim Allan, Accessibility Coordinator > Texas School for the Blind and Visually Impaired > 1100 W. 45th St., Austin, Texas 78756 > <https://maps.google.com/?q=1100+W.+45th+St.,+Austin,+Texas+78756&entry=gmail&source=g> > voice 512.206.9315 <(512)%20206-9315> fax: 512.206.9452 > <(512)%20206-9452> http://www.tsbvi.edu/ > "We shape our tools and thereafter our tools shape us." McLuhan, 1964 >
Attachments
- image/jpeg attachment: Screenshot_20180208-173145.jpg
Received on Thursday, 8 February 2018 23:37:30 UTC