Increasingly video content is becoming part of the enterprise web environment. The promise of HTML5's video element was supposed to solve a lot of the issues around serving videos to the web. But has it succeeded? And what of Accessibility?
This seminar will cover the state of video delivery on the web today, the issues, the promises, and, importantly, how to ensure that it all meets accessibility requirements.
“On January 12, 2012, the FCC adopted rules requiring captioned programs shown on TV to be captioned when re-shown on the Internet.” —FCC.gov
Providing accessible media is not just a federal requirement, but it's good business; 48M people in the US (up to 15% of your site's visitors) are deaf or have some degree of hearing loss.
Learn about making your video accessible to a broader audience and in compliance with the 21st Century Communication and Video Accessibility Act (CVAA).
HEVC, also known as x265 is a new and upcoming video compression algorithm. It boasts about 50% more video file
size reduction, as compared to its predecessor x264, which is an "Industry Standard" currently.
As Flash continues to decline, HTML5 video technologies increasingly bring promise of heightened performance and better QOE. This workshop provides an in-depth look at HTML5 players, their features and strengths, as well as the open-source media engine frameworks available on the market today. We begin by examining the main components in a video player. We then discuss how to choose a player adapted to one’s use case, examining how several open-source solutions compare. Finally, we use an interactive example to build features and demonstrate several optimizations, offering tips and best practices and pointing out potential production issues as we go along.
“On January 12, 2012, the FCC adopted rules requiring captioned programs shown on TV to be captioned when re-shown on the Internet.” —FCC.gov
Providing accessible media is not just a federal requirement, but it's good business; 48M people in the US (up to 15% of your site's visitors) are deaf or have some degree of hearing loss.
Learn about making your video accessible to a broader audience and in compliance with the 21st Century Communication and Video Accessibility Act (CVAA).
HEVC, also known as x265 is a new and upcoming video compression algorithm. It boasts about 50% more video file
size reduction, as compared to its predecessor x264, which is an "Industry Standard" currently.
As Flash continues to decline, HTML5 video technologies increasingly bring promise of heightened performance and better QOE. This workshop provides an in-depth look at HTML5 players, their features and strengths, as well as the open-source media engine frameworks available on the market today. We begin by examining the main components in a video player. We then discuss how to choose a player adapted to one’s use case, examining how several open-source solutions compare. Finally, we use an interactive example to build features and demonstrate several optimizations, offering tips and best practices and pointing out potential production issues as we go along.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.Dylan Wilbanks
The moment we start creating a website, we’re setting ourselves up for failure later. Bad code creates middle of the night fire drills. Lack of thinking about accessibility gets our employer sued. Not thinking ahead on mobile generates rework.
We accept this as the normal course of business — but is there any way we could prevent (or lower) this cost? Is there anything we can learn from the building codes that dictate how our built environment is constructed?
A quick tour of how we got where we are with the web, and perhaps some valuable takeaway points.
Getting Things Done for Technical Communicators at TCUK14Karen Mardahl
My presentation at TCUK14 in Brighton in September 2014 - technicalcommunicationuk.com. It is an update of my similar presentation in June at UA Europe.
What are the features in HTML5 that have the potential to:
make it easier for developers to provide a more accessible user experience?
make it harder for developers to provide a more accessible user experience?
Where does WAI-ARIA fit into the HTML5 accessibility story? How can WAI-ARIA fill the gaps in HTML5 UI accessibility?
Presentation on how usability and accessibility problems are related. Including people with disabilities in usability testing can reveal deeper insights into the kinds of problems users might encounter
Getting Things Done for Technical CommunicatorsKaren Mardahl
A TCUK15 workshop by John Kearney and Karen Mardahl at the ISTC's technical communication conference on September 29th in Glasgow, Scotland. Script for the workshop is at http://www.mardahl.dk/2015/10/29/the-getting-things-done-workshop-at-tcuk15/.
Given from a developer's perspective, this presentation will address the concept of responsible web design as an approach to the authoring of accessible web sites.
Designing with Empathy [Reasons to be Creative 2013]Aaron Gustafson
Every decision we make affects the way real people experience our products.
We've all heard the rallying cry for user-centered design, but even those of us who ascribe to that ideal often fall back on our own biases and instincts when it comes to making decisions about how people experience our content and our services.
Sadly, this often means we make decisions we think will be good for our "users" - that anonymous, faceless crowd - rather than actually trying to understand the perspectives, surroundings, capabilities, and disadvantages of the actual people who we are here to serve.
In this session, Aaron will explore why empathy is a good thing, how empathy empowers creativity, and how we, as a community, can inject more empathy into our work.
Almost all Browsers allow you to install Extensions/Add-ons to make them more powerful by adding new functionality. Dirk Ginader will show you how he built build such an Browser extension to add a feature all modern Browsers lack, and how you can do the same by using basic web technologies and how to make them run in every Browser.
This presentation covers various methods for making your infographics not only accessible, but also shareable. This presentation was developed for the CSUN 2013 conference. The accessible version of this presentation is at http://www.last-child.com/accessible-infographics/csun-2013-presentation/
A Web for Everyone: Accessibility as a design challengeWhitney Quesenbery
Let's get past the idea that checklists and compliance all there is to accessibility. Designing for accessibility is a user experience design problem, starting with understanding how people with disabilities use your products. If we aim to design for all senses we can focus on easy interaction, helpful wayfinding, clean presentation, plain language and media instead of "rules." Doing so, we can create a web for everyone and a delightful user experience where accessibility and usability work together.
Updated January 21
Replay of the O'Reilly webcast: http://www.oreillynet.com/pub/e/2992
Transcript of the O'Reilly webcast: http://www.wqusability.com/handouts/AWFE-Challenge-OReilly-Transcript.pdf
In this month's YDN Tuesday Dirk Ginader, Web Developer and part of the Accessibility Task Force at Yahoo!, will talk about Web Accessibility.
Starting with basic markup and ending with accessible javascript and WAI ARIA he'll cover best practices and lots of tips and tricks to make your websites and web applications accessible to everyone.
Get more information about the event here:
http://skillsmatter.com/event/ajax-ria/web-accessibility
Universal media access as proposed almost two decades ago is now reality. We can generate, distribute, share, and consume any media content, anywhere, anytime, and with/on any device. A technical breakthrough was the adaptive streaming over HTTP resulting in the standardization of MPEG-DASH, which is now successfully deployed in a plethora of environments. The next big thing in adaptive media streaming is virtual reality applications and, specifically, omnidirectional (360°) media streaming, which is currently built on top of the existing adaptive streaming ecosystems. This tutorial provides a detailed overview of adaptive streaming of both traditional and omnidirectional media. The tutorial focuses on the basic principles and paradigms for adaptive streaming as well as on already deployed content generation, distribution, and consumption workflows. Additionally, the tutorial provides insights into standards and emerging technologies in the adaptive streaming space. Finally, the tutorial includes the latest approaches for immersive media streaming enabling 6DoF DASH through Point Cloud Compression (PCC) and concludes with open research issues and industry efforts in this domain. More information available at: https://multimediacommunication.blogspot.com/2019/07/acmmm19-tutorial-journey-towards-fully.html
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.Dylan Wilbanks
The moment we start creating a website, we’re setting ourselves up for failure later. Bad code creates middle of the night fire drills. Lack of thinking about accessibility gets our employer sued. Not thinking ahead on mobile generates rework.
We accept this as the normal course of business — but is there any way we could prevent (or lower) this cost? Is there anything we can learn from the building codes that dictate how our built environment is constructed?
A quick tour of how we got where we are with the web, and perhaps some valuable takeaway points.
Getting Things Done for Technical Communicators at TCUK14Karen Mardahl
My presentation at TCUK14 in Brighton in September 2014 - technicalcommunicationuk.com. It is an update of my similar presentation in June at UA Europe.
What are the features in HTML5 that have the potential to:
make it easier for developers to provide a more accessible user experience?
make it harder for developers to provide a more accessible user experience?
Where does WAI-ARIA fit into the HTML5 accessibility story? How can WAI-ARIA fill the gaps in HTML5 UI accessibility?
Presentation on how usability and accessibility problems are related. Including people with disabilities in usability testing can reveal deeper insights into the kinds of problems users might encounter
Getting Things Done for Technical CommunicatorsKaren Mardahl
A TCUK15 workshop by John Kearney and Karen Mardahl at the ISTC's technical communication conference on September 29th in Glasgow, Scotland. Script for the workshop is at http://www.mardahl.dk/2015/10/29/the-getting-things-done-workshop-at-tcuk15/.
Given from a developer's perspective, this presentation will address the concept of responsible web design as an approach to the authoring of accessible web sites.
Designing with Empathy [Reasons to be Creative 2013]Aaron Gustafson
Every decision we make affects the way real people experience our products.
We've all heard the rallying cry for user-centered design, but even those of us who ascribe to that ideal often fall back on our own biases and instincts when it comes to making decisions about how people experience our content and our services.
Sadly, this often means we make decisions we think will be good for our "users" - that anonymous, faceless crowd - rather than actually trying to understand the perspectives, surroundings, capabilities, and disadvantages of the actual people who we are here to serve.
In this session, Aaron will explore why empathy is a good thing, how empathy empowers creativity, and how we, as a community, can inject more empathy into our work.
Almost all Browsers allow you to install Extensions/Add-ons to make them more powerful by adding new functionality. Dirk Ginader will show you how he built build such an Browser extension to add a feature all modern Browsers lack, and how you can do the same by using basic web technologies and how to make them run in every Browser.
This presentation covers various methods for making your infographics not only accessible, but also shareable. This presentation was developed for the CSUN 2013 conference. The accessible version of this presentation is at http://www.last-child.com/accessible-infographics/csun-2013-presentation/
A Web for Everyone: Accessibility as a design challengeWhitney Quesenbery
Let's get past the idea that checklists and compliance all there is to accessibility. Designing for accessibility is a user experience design problem, starting with understanding how people with disabilities use your products. If we aim to design for all senses we can focus on easy interaction, helpful wayfinding, clean presentation, plain language and media instead of "rules." Doing so, we can create a web for everyone and a delightful user experience where accessibility and usability work together.
Updated January 21
Replay of the O'Reilly webcast: http://www.oreillynet.com/pub/e/2992
Transcript of the O'Reilly webcast: http://www.wqusability.com/handouts/AWFE-Challenge-OReilly-Transcript.pdf
In this month's YDN Tuesday Dirk Ginader, Web Developer and part of the Accessibility Task Force at Yahoo!, will talk about Web Accessibility.
Starting with basic markup and ending with accessible javascript and WAI ARIA he'll cover best practices and lots of tips and tricks to make your websites and web applications accessible to everyone.
Get more information about the event here:
http://skillsmatter.com/event/ajax-ria/web-accessibility
Universal media access as proposed almost two decades ago is now reality. We can generate, distribute, share, and consume any media content, anywhere, anytime, and with/on any device. A technical breakthrough was the adaptive streaming over HTTP resulting in the standardization of MPEG-DASH, which is now successfully deployed in a plethora of environments. The next big thing in adaptive media streaming is virtual reality applications and, specifically, omnidirectional (360°) media streaming, which is currently built on top of the existing adaptive streaming ecosystems. This tutorial provides a detailed overview of adaptive streaming of both traditional and omnidirectional media. The tutorial focuses on the basic principles and paradigms for adaptive streaming as well as on already deployed content generation, distribution, and consumption workflows. Additionally, the tutorial provides insights into standards and emerging technologies in the adaptive streaming space. Finally, the tutorial includes the latest approaches for immersive media streaming enabling 6DoF DASH through Point Cloud Compression (PCC) and concludes with open research issues and industry efforts in this domain. More information available at: https://multimediacommunication.blogspot.com/2019/07/acmmm19-tutorial-journey-towards-fully.html
In familiar applications such as digital versatile disc (DVD), digital video can be found in digital TV, Internet video streaming, digital high-definition television is defined formula. Digital video sharing digital format all functions, including lossless transmission, lossless storage, easy to edit.Currently in many applications, including video conferencing, video games entertainment, DVD discs, digital video broadcasting. As digital video compression format storage requirements prohibitive, lossy digital video compression technology commonly used as the data transmission rate and a compromise between quality. In this paper, we compare and analyze the MPEG-2 , H.261 and H.264 video compression standards.After the Compression , We get the result that the compression of H.264 is better than other two but it take much time as compare to H.261 on higher cost.
Hear how to develop and implement WebRTC using the new IETF and W3C standards. This session will overview the concepts and structure of WebRTC and how it is defined in the emerging standards. The session will bring everyone up to a clear understanding of WebRTC for the technical discussions in the next session.
This workshop will include specific examples of how to code and create real-time interactions. The session will be interactive, allowing for open and clear discussion.
WebRTC Webinar & Q&A - All About Microsoft & WebRTC Hosting Guest Speaker Ja...Amir Zmora
On this session we had guest speaker James Cadd who leads the Open Source WebRTC for Windows effort at Microsoft.
James talked about Microsoft's support for WebRTC. Among other things his presentation includes:
Review of current state of Microsoft's work on WebRTC
API compatibility and WebRTC code used for adding WebRTC to Microsoft's products, source code availability & sample codes
Microsoft's plans for Open Source WebRTC
HTML5 Video Accessibility: Updates, Features, & Guidelines3Play Media
What are the best practices for making web-based video and audio accessible? In this webinar, John Foliot, a video accessibility expert and contributor to the W3C's new Media Accessibility User Requirements (MAUR), will go over the latest updates to HTML5 video as well as new guidelines for making media accessible on the web.
This webinar will cover:
HTML5 video updates
Accessibility features of HTML5
Vetted, best practices information from the W3C
The new Media Accessibility User Requirements (MAUR), and what that means for you
Best practices for online video accessibility
Closed captioning guidelines according to MAUR and the W3C
Resources for making your web-based media accessible
Kranky Geek WebRTC 2015 - What's next for WebRTC?Kranky Geek
lways the highlight of this event, Google provides the nitty gritty details on what they are doing to progress WebRTC and their internal developments to help your application succeed. We'll cover more details on the recently announced Alliance for Open Media, an effort to create royalty-free video codecs.
Google Team
This presentation is devoted to the architecture of streaming services, special features of adaptive streaming, benefits and disadvantages of various streaming technologies and specific issues of media streaming apps development.
This presentation by Nazariy Mamrokha, GlobalLogic expert, was delivered at GlobalLogic Lviv C++ TechTalk on September 15, 2016. Learn more here: https://www.globallogic.com/ua/gl_news/globallogic-lviv-c-techtalk-summary/
IBM Connect session
See also Call Speed Bandwidth Calculator spreadsheet
https://greenhouse.lotus.com/files/app#/file/a5817fad-b7b4-4fe5-94ce-00c11cf20ba4
Getting ahead of the curve - Scalable, Accessible, Enterprise-class Video on ...John Foliot
John Foliot, a video accessibility expert and contributor to the W3C’s new Media Accessibility User Requirements (MAUR), will go over the latest updates to HTML5 video as well as new guidelines for making media accessible on the web.
Similar to Accessible Video in The Enterprise (20)
SAP Sapphire 2024 - ASUG301 building better apps with SAP Fiori.pdfPeter Spielvogel
Building better applications for business users with SAP Fiori.
• What is SAP Fiori and why it matters to you
• How a better user experience drives measurable business benefits
• How to get started with SAP Fiori today
• How SAP Fiori elements accelerates application development
• How SAP Build Code includes SAP Fiori tools and other generative artificial intelligence capabilities
• How SAP Fiori paves the way for using AI in SAP apps
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Le nuove frontiere dell'AI nell'RPA con UiPath Autopilot™UiPathCommunity
In questo evento online gratuito, organizzato dalla Community Italiana di UiPath, potrai esplorare le nuove funzionalità di Autopilot, il tool che integra l'Intelligenza Artificiale nei processi di sviluppo e utilizzo delle Automazioni.
📕 Vedremo insieme alcuni esempi dell'utilizzo di Autopilot in diversi tool della Suite UiPath:
Autopilot per Studio Web
Autopilot per Studio
Autopilot per Apps
Clipboard AI
GenAI applicata alla Document Understanding
👨🏫👨💻 Speakers:
Stefano Negro, UiPath MVPx3, RPA Tech Lead @ BSP Consultant
Flavio Martinelli, UiPath MVP 2023, Technical Account Manager @UiPath
Andrei Tasca, RPA Solutions Team Lead @NTT Data
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
2. A (Very) Brief History
1999 – 2005: Competing, incompatible delivery platforms
2005: Launch of YouTube & Flash-based player brings some
commonality to delivery platform
3. A (Very) Brief History
2012/2014: W3C’s Standardization of HTML5
Apple drops Flash support / advances in Major
Browsers
4. Consideration #1 -
Streaming
Users Start Giving Up on Streaming Video If It Takes Two
Seconds to Load: (http://gizmodo.com/5959553/users-start-
giving-up-on-streaming-video-if-it-takes-two-seconds-to-load)
Research Data:
http://people.cs.umass.edu/~ramesh/Site/HOME_files/imc208-
krishnan.pdf
University of Massachusetts, Amherst & Akamai Technologies
5. Consideration #1 -
Streaming
Protocols:
HTTP (hyper text transfer protocol):
• chops web pages into packets for fast, asynchronous delivery
RTSP (Real Time Streaming Protocol):
• delivers continuous stream of multimedia data
• requires specialized streaming media server
Adaptive Bit-Rate - HTTP Live Streaming, Smooth Streaming and HTTP
Dynamic Streaming:
• HTTP Live Streaming is backed by Apple, Smooth Streaming is
backed by Microsoft and HTTP Dynamic Streaming is backed by
Adobe
• emergent solutions that are not yet standardized – not all
platforms are supported
• “fakes out” streaming by delivering “chunks” of content delivered
via HTTP that self-adjusts delivery packets
• requires additional production overhead and asset management
6. Consideration #1 -
Streaming
Adaptive bit-rate:
This delivery method is beginning to have a massive impact on
every aspect of Internet video delivery because it allows the
stream to actually adapt the video experience to the quality of the
network and the device's CPU.
7. Consideration #1 -
Streaming
Essentially, the video stream can increase or decrease the bit rate
and resolution of the video (its quality) in real time so that it’s
always streaming the best possible quality the available network
connection can support.
The better the network connection, the better the video image
quality.
The fact that the stream handles all of this complexity means the
mobile video viewer doesn’t have to do anything; everything is left
to the stream and the player.
11. Consideration #2:
Encoding Considerations
H.264:
considered to be the front-runner / industry standard
Licensed codec via MPEG LA – Royalty status remains vague
WebM:
“free” codec developed by Google
Royalty free for use by content producers
Ogg Theora:
Open Source codec
Considered ‘dated’ and support diminishing in favor of WebM
12. Consideration #2:
Encoding Considerations
The Bottom Line?
To provide full support today
to all users and user-
platforms we will need to
consider encoding videos at
least twice, in 2 formats.
Recommendation?
H.264 & WebM codecs
13. Consideration #3: Security
There are at least 2 types of
security concerns with
video delivery on the web:
Script Injections: Since many video
controls and captions use some form
of scripting, caution must be taken to
ensure that they do not introduce
security holes that can be exploited.
14. Consideration #3: Security
http vs. https: Since the video
and all related assets
(captions, transcripts, video
descriptions) are traditionally
served to the web browser as
discrete files, when we look
to embed a video on a secure
page, those supplemental
files will also need to be
served securely to avoid User
Security Warnings.
15. Consideration #4:
Accessibility
The W3C have
produced a
detailed list of all
requirements
various user-
groups would
need for full and
complete access
to multi-media.
http://www.w3.org/WAI/PF/media-a11y-reqs/
16. Consideration #4:
Accessibility
At a minimum, users
require accessible
media player controls
(start, stop, pause,
mute, etc), as well as
time-synched
captions, descriptive
audio, and full
transcripts of all
content delivered.
17. Consideration #4:
Accessibility
WCAG 1.2.1 Provide alternatives for Prerecorded Video:
Either an alternative for time-based media or an audio
track is provided that presents equivalent information for
prerecorded video-only content. (A)
WCAG 1.2.2 Captions: Captions are provided for all
prerecorded audio content in synchronized media. (A)
18. Consideration #4:
Accessibility
WCAG 1.2.3 Audio Description or Media Alternative: An
alternative for time-based media or audio description of
the prerecorded video content is provided for synchronized
media. (A)
WCAG 1.2.5 Audio Description: Audio description is
provided for all prerecorded video content in synchronized
media. (AA)
19. Definitions:
Closed Captions / Open
Captions:
Closed captions can be turned “on or off”
by the end user
Open Captions remain on-screen for all
users
Captions capture onscreen dialog and basic
sound effects (<<clapping>>, <<music>>,
<<laughter>>, etc.)
Resource:
http://www.dcmp.org/
captioningkey/
20. Definitions:
Caption Formats:
TTML (Timed Text Markup Language) –
XML based (includes DFXP, a standard for
Flash players)
WebVTT (Web Video Timed Text) –
emergent standard, text based, favored by
browser vendors
Other formats exist – conversion from
one format to the other is a mechanical
process
21. Definitions:
Transcripts:
Loosely defined in the web space
Generally are more complete than
captions – includes additional on-screen
information (descriptions of charts or other
visual assets for example)
Traditionally offered as a complementary
piece to the media asset (unlike captions
which are delivered in a synchronous fashion
with the media)
Usually provided as HTML or
downloadable text formats such as accessible
PDF
22. Definitions:
Descriptive Audio:
Supplemental audio track,
provided on demand, which
describes on-screen actions to the
non-sighted.
Specified as a WCAG
requirement (1.2.5), delivery
technologies remain rudimentary
with little practical support in the
wild.
23. Consideration #4:
Accessibility
Re: WCAG 1.2.5 Audio Description:
At this time, delivering on this AA Requirement is severely
frustrated due to the lack of robust native support in browsers
and mobile devices. Many entities are choosing to NOT require
this Success Criteria, including the Governments of Canada,
Ontario and Quebec.
The Access Board in the US will likely seek to maintain the
current requirement in provision 1194.24(b) that ICT hardware
support audio description , which might improve the current
situation. Fingers crossed.
24. Accessibility Production
Requirements: The most labor-intensive
aspect of ensuring
accessible media is the
generation of the text that
represents the audio (and
in some cases descriptions
of on-screen activity), to
be subsequently integrated
into the final on-screen
delivery to the end client.
Videos created from an approved script will already have text
to work with, however when no script is available the process
of ensuring accurate text transcription remains a manual
process.
25. Accessibility Production
Requirements:
While advances in speech to text have
come a long way, and continue to
evolve in terms or accuracy, at this time
the only dependable way of ensuring
accuracy is through the involvement of
human input.
26. Accessibility Production
Requirements: • Support for “Closed
Captions” on mobile devices
today is practically non-
existent.
• This means that for the
mobile platform today, we will
need to be able to offer the
end user a choice of the non-
captioned video, or an Open
Captioned video prior to the
launch of the video itself.
• The same technical limitations currently impact the
provisioning of descriptive audio as well.
27. Recap:
• Streaming solutions like Adaptive Bit-Rate delivery are
emerging as absolute requirements to address
different screen resolutions, bandwidth
considerations, etc.
• There are existing proprietary solutions in the market-
place that address some, but not all needs
• W3C’s Media Source Extension specification is at Last
Call, with minimal browser support today
28. Recap:
• The “codec wars” remain at a stalemate, necessitating
multiple encodings to support HTML5’s <video>
element
• H.264 and WebM codecs are the recommended
choices today
• Caution should be exercised with regard to security
considerations. Beware of script injection holes
• Videos served from a secure environment will need to
ensure that all supporting assets are also served
securely
29. Recap:
• At a minimum, users require accessible media player
controls (start, stop, pause, mute, etc), as well as time-
synched captions, descriptive audio, and full
transcripts of all content delivered.
• There is currently no native support in the browsers to
satisfy WCAG 1.2.5 (AA)
• The creation of text based alternatives remains for the
most part a manual process today
• Delivering Captioned videos on mobile currently
requires Open Caption alternatives
30. Recap:
Kind of disappointing, right?
While problems still exist, there
is forward movement at a
decent pace.
Remember, patience is a virtue.
31. Exciting developments to
watch: The A11yMetadata
Project seeks to
extend schema.org
by including new
properties to
address the
accessibility and
discoverability of
resources on the
Web.
http://www.w3.org/wiki/WebSchemas/Accessibility
32. The A11yMetadata Project
Specifying content features of the resource, such as accessible
media and alternatives:
<meta itemprop="mediaFeature" content="alternativeText">
PROPOSED VALUES:
alternativeText
audioDescription
braille
captions
ChemML
describedMath
displayTransformability
haptic
highContrast
largePrint
latex
longDescription
MathML
musicBraille
musicLargePrint
nemethBraille
signLanguage
structuralNavigation
tactileGraphic
tactileObject
transcript
33. Exciting developments to
watch: The Descriptive Video
Exchange project focuses
on crowd-sourced
techniques for describing
DVD media. CSD will
expand DVX to include
Internet-based media
such as YouTube, iTunes
U, and other streamed
video found on a wide
variety of web sites.
http://www.vdrdc.org/research/csd
34. Exciting developments to
watch: This new project aims to
demonstrate the
inclusion of
enhancements in ways
that are both visual and
non-visual, all of which
are screen-reader
accessible and delivered
using HTML5, JavaScript
and the Popcorn.js
HTML5 Media
Framework.
http://ncamftp.wgbh.org/rd/hgp/
Using HTML5 and JavaScript to
Deliver Accessible Supplemental
Materials
A Very Brief History: The evolution of video content delivered via the web remains in its infancy today, and a standardized solution for ubiquitous and simple delivery remains elusive. With the current transition towards HTML5 based solutions (which break from previous delivery mechanisms) there remains division in media encoding, with some browsers only supporting one encoding (H.264/MP4) and others only supporting a different encoding (VP8/WebM). It is further complicated by the fact that some operating systems (iOS) do not support the traditional Flash-based media players that have emerged over the past 5+ years, requiring additional production effort and scripted bridging solutions to achieve full coverage across the multiple delivery channels available to the end consumer today.
Video buffering (stalling) impacts on the user-experience in negative ways, as research confirms. As we add more video to our service and product offerings, this will increasingly be a delivery issue.Under normal circumstances, “web content” travels across the internet using the http:// protocol (you will often see this as the start of a web address). The http:// protocol “chops up” content and sends small packets of data across the web, and the browser collects those packets and re-assembles them on the client screen (well, not exactly, but close enough for this discussion). This is a very efficient and effective way of transmitting static content, however it is not so great when you want to stream content (like videos). What happens is that you create a situation where you get buffering – the video either gets choppy or “stalls” and you get the spinner on screen as the browser is waiting for the rest of the packets to arrive – I’m sure you’ve seen this before.
There are a number of different ways of addressing this problem, the most efficient being to use a different type of protocol. The ‘standard’ for streaming media is the Real Time Streaming Protocol (RTSP)- *BUT* to do RTSP you require a differently configured web-server, and instead of declaring the address of your asset as http://mysite.com/video.mp4 you would instead write rtsp://mysite.com/video.mp4. Other, newerformats/protocols such as HTTP Live Streaming, Smooth Streaming and HTTP Dynamic Streaming are also seeking to address the buffering problems by developing a HTTP delivery mechanism. Currently there are similar but competing solutions from Apple, Microsoft and Adobe. (There is another distinct advantage to progressive streaming when it comes to actual mobile delivery, where buffering is further complicated by bandwidth availability – 4G vs. 3G vs. Edge)
Another important consideration is file-size and compression, which will have a direct impact on our videos. With web content being consumed by an increasingly diverse collection of screens and connectivity combinations (from lean-back, large-screen delivery to hand-held mobile screens), there is a need to provide adaptive streams tailored to those platforms. For example, large screen displays (be they desktop or even home television screens) require a higher-definition video stream, resulting in larger files and increased demand for bandwidth. Conversely, serving streaming media to handheld devices over more restricted wireless networks requires smaller file sizes.
Systems are emerging today that provide different video compressions on demand – so-called Adaptive bit-rate delivery – to address this issue, although issues around codec support mean that none of these solutions are 100% supported across all browsers. Due to the way these systems work, there is some additional post-production overhead effort required, although tools to automate this are emerging.Despite some limitations today however, a robust, scalable video delivery solution will likely require some form of this type of service.
This specification extends HTMLMediaElement to allow JavaScript to generate media streams for playback. Allowing JavaScript to generate streams facilitates a variety of use cases like adaptive streaming and time shifting live streams.
This specification extends HTMLMediaElement to allow JavaScript to generate media streams for playback. Allowing JavaScript to generate streams facilitates a variety of use cases like adaptive streaming and time shifting live streams.
All web videos must be encoded into a format that works across all browsers and operating systems. Due to complicated legal and “political” reasons, not all browsers and operating systems today support the same encodings, and at this writing positions are fairly well entrenched in all corners, resulting in a need for multiple encodings to support all browsers and platforms. At issue is the need for a license to cover the patent on the H.264 codec, which is at odds with Free and Open Source software such as Linux and the Firefox browser, which for philosophical reasons cannot support that codec in their software stack(s). Firefox however currently provides limited support when hardware decoding is present on the host system (such as most handheld devices today – see: https://brendaneich.com/2012/03/video-mobile-and-the-open-web/).
However, for full coverage we should be expecting to deliver encoded videos in both the H.264/mpeg 4 and On2/Webm formats at minimum today. This will likely be an additional burden on the production process of all videos.
Videos and other multi-media content is increasingly becoming an integral part of modern web content as an effective means of engaging with our users. However due to it’s multi-modal nature, the use of video has a number of accessibility issues we must address in a holistic fashion. These issues include: * Deaf and hard-of-hearing users - these users cannot hear the audio track of your media presentation. We must ensure that captions and perhaps even transcripts are available for their use. * Blind and low-vision users - these users cannot see the presentation, although perhaps they can hear it. It is critical that any on-screen text, or import visual imagery (charts, graphs, etc.) also be communicated to them. This can be achieved via audio-description, or by ensuring supporting (text-based) documents [transcripts] are associated to the media asset and easy to access. * Mobility impaired users / keyboard only users - Media players must be constructed in such a way so that they can be interacted with via keyboard, avoiding keyboard ‘traps’, etc. A common, approved media player often addresses these issues at a global level.Other issues can include addressing the needs of users with atypical color perception, blind/deaf users, or users with cognitive and neurological disabilities. Each of these users groups will have potential strategies to ensure their access to multi-media content that we should be aware of.The W3C has created a Media Accessibility User Requirements document that outlines in more detail the challenges that these groups face, as well as potential strategies that should be used to address their needs.
The intent of Requirement 1.2.1 is to make information conveyed by prerecorded audio-only and prerecorded video-only content available to all users. Alternatives for time-based media that are text based make information accessible because text can be rendered through any sensory modality (for example, visual, auditory or tactile) to match the needs of the user. The intent of Requirement 1.2.2 is to enable people who are deaf or hard of hearing to watch synchronized media presentations. Captions provide the part of the content available via the audio track. Captions not only include dialogue, but identify who is speaking and include non-speech information conveyed through sound, including meaningful sound effects. It is acknowledged that at the present time there may be difficulty in creating captions for time-sensitive material and this may result in the author being faced with the choice of delaying the information until captions are available, or publishing time-sensitive content that is inaccessible to the deaf, at least for the interval until captions are available. Over time, the tools for captioning as well as building the captioning into the delivery process can shorten or eliminate such delays.
The intent of Requirement 1.2.3 is to provide people who are blind or visually impaired access to the visual information in a synchronized media presentation. This can be achieved using one of the following two processes: - One approach is to provide audio description of the video content. The audio description augments the audio portion of the presentation with the information needed when the video portion is not available. During existing pauses in dialogue, audio description provides information about actions, characters, scene changes, and on-screen text that are important and are not described or spoken in the main sound track. - The second approach involves providing all of the information in the synchronized media (both visual and auditory) in text form. An alternative for time-based media provides a running description of all that is going on in the synchronized media content. The alternative for time-based media reads something like a screenplay or book. Unlike audio description, the description of the video portion is not constrained to just the pauses in the existing dialogue. Full descriptions are provided of all visual information, including visual context, actions and expressions of actors, and any other visual material. In addition, non-speech sounds (laughter, off-screen voices, etc.) are described, and transcripts of all dialogue are included.The intent of Requirement 1.2.5 is to provide people who are blind or visually impaired access to the visual information in a synchronized media presentation. The audio description augments the audio portion of the presentation with the information needed when the video portion is not available. During existing pauses in dialogue, audio description provides information about actions, characters, scene changes, and on-screen text that are important and are not described or spoken in the main sound track.
There are a number of different ‘time-stamping’ formats that are used to deliver synchronized captions on the web today. The W3C have already produced an XML-based format (TTML – Timed Text Markup Language), of which a subset of that format – DFXP – is currently supported by most Flash-based players today. However other time-stamp formats are also in play at this time: .SRT and it’s successor WebVTT* are emerging as the de-facto standard for native HTML5 delivery, SMPTE-TT (a superset of TTML developed by the Society of Motion Picture and Television Engineers that has support in IE 10) as well as .SCC, a binary format that is required for iPhone captioning support today.
Along with the obvious need for captioned videos, our Accessibility requirements also call for provisioning of Transcripts.There are a number of experimental examples of “interactive” transcripts, that provide enhance functionality when delivered in synch with the video. Examples include a “follow-along” highlighting, hyperlinked transcripts (both static and timed), and the ability to highlight sections for truncated embedding (useful with longer-form videos). The potential for marketing uses of this type of interactive transcript should be considered as a ‘bonus’ consideration when investigating any solution moving forward.
Gov. of Canada = WCAG 2.0 AA minus Complex maps (1.1.1), Live Video Captions (1.2.4) and Audio-Descriptions (unless related to health or safety, 1.2.5)http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=23601&section=text#appB Ontario Gov. - AODA = Full fledged WCAG 2.0 AA, except for 1.2.4 and 1.2.5http://www.e-laws.gov.on.ca/html/source/regs/english/2011/elaws_src_regs_r11191_e.htm#BK15 Quebec Gov. - SGQRI 008-03 = limited to 1.2.1, 1.2.2 and 1.2.3 when it comes to audio/video http://www.tresor.gouv.qc.ca/fileadmin/PDF/ressources_informationnelles/AccessibiliteWeb/access_multimedia_ve.pdf (p.13)
While many aspects of the creation of accessible videos can be automated and systemized, the conversion of the spoken word (etc.) to a text based format remains a manual process, especially when specialized terms or other legal requirements demand accuracy. Whether done real time (CART services) or during the post-production process, it is a specialized skill-set that can either be brought in-house, or out-sourced to third-party firms that specialize in this service. Currently, while pricing is variable, there appears to be a leveling off at approximately $60 - $100 per hour of video content when out-sourced (pricing often dependant on volume of content, and turn-around time).Once the textual equivalent is produced, there are numerous services and systems that can apply the time-stamping to the content for final delivery.
For a variety of reasons (including lower CPU capacity on phones, bandwidth and network restrictions, and the complexities of keeping separate text tracks and media tracks in sync) support for “Closed Captions” on mobile devices today is practically non-existent today. This means that for the mobile platform, we will need to be able to offer the end user a choice of the non-captioned video, or an Open Captioned video.