Skip to content

Commit f847e98

Browse files
authored
Merge pull request #107931 from IngridAtMicrosoft/azure-media-services-inhenkel-031320201
Migrating Azure media player docs Azure media services inhenkel 031320201
2 parents ed3f596 + f6f49aa commit f847e98

19 files changed

+2191
-0
lines changed
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
- name: Overview
2+
items:
3+
- name: Azure Media Player overview
4+
href: azure-media-player-overview.md
5+
- name: Release notes
6+
href: azure-media-player-release-notes.md
7+
- name: Changelog
8+
href: azure-media-player-changelog.md
9+
- name: Quickstarts
10+
items:
11+
- name: Azure Media Player quickstart
12+
href: azure-media-player-quickstart.md
13+
- name: Tutorials
14+
items:
15+
- name: Azure Media Player full setup
16+
href: azure-media-player-full-setup.md
17+
- name: Concepts
18+
items:
19+
- name: Playback technology
20+
href: azure-media-player-playback-technology.md
21+
- name: Protected content
22+
href: azure-media-player-protected-content.md
23+
- name: Feature list
24+
href: azure-media-player-feature-list.md
25+
- name: URL rewriter
26+
href: azure-media-player-url-rewriter.md
27+
- name: Accessibility
28+
href: azure-media-player-accessibility.md
29+
- name: Writing plugins
30+
href: azure-media-player-writing-plugins.md
31+
- name: Plugin gallery
32+
href: azure-media-player-plugin-gallery.md
33+
- name: Localization
34+
href: azure-media-player-localization.md
35+
- name: Reference
36+
items:
37+
- name: Samples
38+
href: https://github.com/Azure-Samples/azure-media-player-samples
39+
- name: API
40+
href: https://docs.microsoft.com/en-us/javascript/api/azuremediaplayer/?view=azure-node-latest
41+
- name: API methods
42+
href: azure-media-player-api-methods.md
43+
- name: Options
44+
href: azure-media-player-options.md
45+
- name: Error codes
46+
href: azure-media-player-error-codes.md
47+
- name: Known issues
48+
href: azure-media-player-known-issues.md
Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
title: Azure Media Player Accessibility
3+
description: Learn more about the Azure Media Player's accessibility settings.
4+
author: IngridAtMicrosoft
5+
ms.author: inhenkel
6+
ms.service: media-services
7+
ms.topic: overview
8+
ms.date: 04/20/2020
9+
---
10+
11+
# Accessibility #
12+
13+
Azure Media Player works with screen reader capabilities such as Windows Narrator and Apple OSX/iOS VoiceOver. Alternative tags are available for the UI buttons, and the screen reader is capable of reading these alternative tags when the user navigates to them. Additional configurations can be set at the Operating System level.
14+
15+
## Captions and subtitles ##
16+
17+
At this time, Azure Media Player currently supports captions for only On-Demand events with WebVTT format and live events using CEA 708. TTML format is currently unsupported. Captions and subtitles allow the player to cater to and empower a broader audience, including people with hearing disabilities or those who want to read along in a different language. Captions also increase video engagement, improve comprehension, and make it possible to view the video in sound sensitive environments, like a workplace.
18+
19+
## High contrast mode ##
20+
21+
The default UI in Azure Media Player is compliant with most device/browser high contrast view modes. Configurations can be set at the Operating System level.
22+
23+
## Mobility options ##
24+
25+
### Tabbing focus ###
26+
27+
Tabbing focus, provided by general HTML standards, is available in Azure Media Player. In order to enable tab focusing, you must add `tabindex=0` (or another value if you understand how tab ordering is affected in HTML) to the HTML `<video>` like so: `<video ... tabindex=0>...</video>`. On some platforms, the focus for the controls may only be present if the controls are visible and if the platform supports these capabilities.
28+
29+
Once tabbing focus is enabled, the end user can effectively navigate and control the video player without depending on their mouse. Each context menu or controllable element can be navigated to by hitting the tab button and selected with enter or spacebar. Hitting enter or spacebar on a context menu will expand it so the end user can continue tabbing through to select a menu item. Once you have context of the item you wish to select, hit enter or spacebar again to complete the selection.
30+
31+
### HotKeys ###
32+
33+
Azure Media Player supports controlling through keyboard hot key. In a web browser, the only way to control the underlying video element is by having focus on the player. Once there is focus on the player, hot key can control the player functionality. The table below describes the various hot keys and their associated behavior:
34+
35+
| Hot key | Behavior |
36+
|----------------------|-------------------------------------------------------------------------|
37+
| F/f | Player will enter/exit FullScreen mode |
38+
| M/m | Player volume will mute/unmute |
39+
| Up and Down Arrow | Player volume will increase/decrease |
40+
| Left and Right Arrow | Video progress will increase /decrease |
41+
| 0,1,2,3,4,5,6,7,8,9 | Video progress will be changed to 0%\- 90% depending on the key pressed |
42+
| Click Action | Video will play/pause |
43+
44+
## Next steps
45+
46+
<!---Some context for the following links goes here--->
47+
- [Azure Media Player Quickstart](azure-media-player-quickstart.md)
Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
---
2+
title: Azure Media Player API Methods
3+
description: The Azure Media Player API allows you to interact with the video through JavaScript, whether the browser is playing the video through HTML5 video, Flash, Silverlight, or any other supported playback technologies.
4+
author: IngridAtMicrosoft
5+
ms.author: inhenkel
6+
ms.service: media-services
7+
ms.topic: reference
8+
ms.date: 04/20/2020
9+
---
10+
11+
12+
# API #
13+
14+
The Azure Media Player API allows you to interact with the video through JavaScript, whether the browser is playing the video through HTML5 video, Flash, Silverlight, or any other supported playback technologies.
15+
16+
## Referencing the player ##
17+
18+
To use the API functions, you need access to the player object. Luckily it is easy to get. You just need to make sure your video tag has an ID. The example embed code has an ID of `vid1`. If you have multiple videos on one page, make sure every video tag has a unique ID.
19+
20+
`var myPlayer = amp('vid1');`
21+
22+
> [!NOTE]
23+
> If the player hasn't been initialized yet via the data-setup attribute or another method, this will also initialize the player.
24+
25+
## Wait until the player is ready ##
26+
27+
The time it takes Azure Media Player to set up the video and API will vary depending on the playback technology being used. HTML5 will often be much faster to load than Flash or Silverlight. For that reason, the player's 'ready' function should be used to trigger any code that requires the player's API.
28+
29+
```javacript
30+
amp("vid_1").ready(function(){
31+
var myPlayer = this;
32+
33+
// EXAMPLE: Start playing the video.
34+
myPlayer.play();
35+
});
36+
```
37+
38+
OR
39+
40+
```javacript
41+
var myPlayer = amp("vid_1", myOptions, function(){
42+
//this is the ready function and will only execute after the player is loaded
43+
});
44+
```
45+
46+
## API methods ##
47+
48+
Now that you have access to a ready player, you can control the video, get values, or respond to video events. The Azure Media Player API function names attempt to follow the [HTML5 media API](http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html). The main difference is that getter/setter functions are used for video properties.
49+
50+
```javacript
51+
// setting a property on a bare HTML5 video element
52+
myVideoElement.currentTime = 120;
53+
54+
// setting a property with Azure Media Player
55+
myPlayer.currentTime(120);
56+
```
57+
58+
## Registering for events ##
59+
Events should be registered directly after initializing the player for the first time to ensure all events are appropriately reported to the application, and should be done outside of the ready event.
60+
61+
```javacript
62+
var myPlayer = amp("vid_1", myOptions, function(){
63+
//this is the ready function and will only execute after the player is loaded
64+
});
65+
myPlayer.addEventListener(amp.eventName.error, _ampEventHandler);
66+
//add other event listeners
67+
```
68+
69+
## Next steps ##
70+
71+
<!---Some context for the following links goes here--->
72+
- [Azure Media Player Quickstart](azure-media-player-quickstart.md)

0 commit comments

Comments
 (0)