web/video.js
1
0
Fork 0
mirror of https://github.com/videojs/video.js.git synced 2024-12-23 02:04:34 +02:00
Code Releases Activity
eb8f802391
video.js/docs/translations-needed.md

888 lines
98 KiB
Markdown
Raw Normal View History

@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
# Translations needed
The currently available translations are in the lang dir. This table shows the completeness of those translations. Anything not listed does not exist yet, so go ahead and create it by copying `en.json`.
fix(lang): append UKR translations and fix check translations command (#5642)
2018-12-05 22:03:03 +02:00
If you add or update a translation run `npm run docs:lang` to update the list and include this modified doc in the pull request.
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
## Progress Bar Translations
docs: fix links in generated docs (#4200)
2017-03-21 23:13:06 +02:00
fix(time-display): restore hidden label text for screen readers. (#5157) Restore hidden label text for screen readers that describes what the button control does. Renames the Duration Time language item to Duration. Deprecate controlText_ property. Fix a typo in translations-needed.md. Add a space in the hidden label for live-display, so that it doesn't run together with the visible "LIVE" indication. Fixes #5135
2018-05-11 20:02:52 +02:00
The progress bar has a translation with a few token replacements.
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
They key is `progress bar timing: currentTime={1} duration={2}` and the default English value is `{1} of {2}`.
This default value is hardcoded as a default to the localize method in the SeekBar component.
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
## Status of translations
<!-- START langtable -->
feat: Add a player option `noUITitleAttributes` to prevent title attributes in the UI (#7134) Fixes #6767
2021-03-23 23:47:16 +02:00
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| Language file | Missing translations |
| ----------------------- | ----------------------------------------------------------------------------------- |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| ar.json (missing 3) | progress bar timing: currentTime={1} duration={2} |
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| ba.json (missing 63) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
| | Replay |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Descriptions |
| | descriptions off |
| | Audio Track |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | The media is encrypted and we do not have the keys to decrypt it. |
| | Play Video |
| | Close |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Close Modal Dialog |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Modal Window |
| | This is a modal window |
| | This modal can be closed by pressing the Escape key or activating the close button. |
| | , opens captions settings dialog |
| | , opens subtitles settings dialog |
| | , opens descriptions settings dialog |
| | , selected |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| bg.json (missing 63) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
| | Replay |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Descriptions |
| | descriptions off |
| | Audio Track |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | The media is encrypted and we do not have the keys to decrypt it. |
| | Play Video |
| | Close |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Close Modal Dialog |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Modal Window |
| | This is a modal window |
| | This modal can be closed by pressing the Escape key or activating the close button. |
| | , opens captions settings dialog |
| | , opens subtitles settings dialog |
| | , opens descriptions settings dialog |
| | , selected |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| ca.json (missing 63) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
| | Replay |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Descriptions |
| | descriptions off |
| | Audio Track |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | The media is encrypted and we do not have the keys to decrypt it. |
| | Play Video |
| | Close |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Close Modal Dialog |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Modal Window |
| | This is a modal window |
| | This modal can be closed by pressing the Escape key or activating the close button. |
| | , opens captions settings dialog |
| | , opens subtitles settings dialog |
| | , opens descriptions settings dialog |
| | , selected |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| cs.json (missing 4) | Seek to live, currently behind live |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently playing live |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| cy.json (missing 4) | Seek to live, currently behind live |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently playing live |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| da.json (missing 63) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
| | Replay |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Descriptions |
| | descriptions off |
| | Audio Track |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | The media is encrypted and we do not have the keys to decrypt it. |
| | Play Video |
| | Close |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Close Modal Dialog |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Modal Window |
| | This is a modal window |
| | This modal can be closed by pressing the Escape key or activating the close button. |
| | , opens captions settings dialog |
| | , opens subtitles settings dialog |
| | , opens descriptions settings dialog |
| | , selected |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
fix(lang): Add PiP to de (#6803)
2020-08-13 14:47:11 +02:00
| de.json (Complete) | |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| el.json (missing 49) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
| | Replay |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| es.json (missing 2) | Exit Picture-in-Picture |
| | Picture-in-Picture |
| fa.json (Complete) | |
| fi.json (missing 63) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
| | Replay |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Descriptions |
| | descriptions off |
| | Audio Track |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | The media is encrypted and we do not have the keys to decrypt it. |
| | Play Video |
| | Close |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Close Modal Dialog |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Modal Window |
| | This is a modal window |
| | This modal can be closed by pressing the Escape key or activating the close button. |
| | , opens captions settings dialog |
| | , opens subtitles settings dialog |
| | , opens descriptions settings dialog |
| | , selected |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| fr.json (missing 5) | Seek to live, currently behind live |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently playing live |
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| gd.json (missing 2) | Exit Picture-in-Picture |
| | Picture-in-Picture |
| gl.json (missing 2) | Exit Picture-in-Picture |
| | Picture-in-Picture |
| he.json (missing 5) | Seek to live, currently behind live |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently playing live |
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| hr.json (missing 63) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
| | Replay |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Descriptions |
| | descriptions off |
| | Audio Track |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | The media is encrypted and we do not have the keys to decrypt it. |
| | Play Video |
| | Close |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Close Modal Dialog |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Modal Window |
| | This is a modal window |
| | This modal can be closed by pressing the Escape key or activating the close button. |
| | , opens captions settings dialog |
| | , opens subtitles settings dialog |
| | , opens descriptions settings dialog |
| | , selected |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
fix(lang): improve Hungarian translation (#7289)
2021-06-29 23:52:47 +02:00
| hu.json (Complete) | |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| it.json (missing 63) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
| | Replay |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Descriptions |
| | descriptions off |
| | Audio Track |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | The media is encrypted and we do not have the keys to decrypt it. |
| | Play Video |
| | Close |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Close Modal Dialog |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Modal Window |
| | This is a modal window |
| | This modal can be closed by pressing the Escape key or activating the close button. |
| | , opens captions settings dialog |
| | , opens subtitles settings dialog |
| | , opens descriptions settings dialog |
| | , selected |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| ja.json (missing 63) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
| | Replay |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Descriptions |
| | descriptions off |
| | Audio Track |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | The media is encrypted and we do not have the keys to decrypt it. |
| | Play Video |
| | Close |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Close Modal Dialog |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Modal Window |
| | This is a modal window |
| | This modal can be closed by pressing the Escape key or activating the close button. |
| | , opens captions settings dialog |
| | , opens subtitles settings dialog |
| | , opens descriptions settings dialog |
| | , selected |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| ko.json (missing 63) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
| | Replay |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Descriptions |
| | descriptions off |
| | Audio Track |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | The media is encrypted and we do not have the keys to decrypt it. |
| | Play Video |
| | Close |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Close Modal Dialog |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Modal Window |
| | This is a modal window |
| | This modal can be closed by pressing the Escape key or activating the close button. |
| | , opens captions settings dialog |
| | , opens subtitles settings dialog |
| | , opens descriptions settings dialog |
| | , selected |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| nb.json (missing 2) | Exit Picture-in-Picture |
| | Picture-in-Picture |
| nl.json (missing 5) | Seek to live, currently behind live |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently playing live |
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| nn.json (missing 2) | Exit Picture-in-Picture |
| | Picture-in-Picture |
| oc.json (missing 2) | Exit Picture-in-Picture |
| | Picture-in-Picture |
| pl.json (missing 55) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
| | Replay |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Descriptions |
| | descriptions off |
| | Audio Track |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | The media is encrypted and we do not have the keys to decrypt it. |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Close Modal Dialog |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | , opens descriptions settings dialog |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
fix(lang): Add PiP to de (#6803)
2020-08-13 14:47:11 +02:00
| pt-BR.json (missing 2) | Seek to live, currently behind live |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently playing live |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| pt-PT.json (missing 48) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| ru.json (missing 4) | Seek to live, currently behind live |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently playing live |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| sk.json (missing 4) | Seek to live, currently behind live |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently playing live |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
feat(lang): add Slovene language translation (#6959) Co-authored-by: Iztok <iztok@abelium.com>
2020-12-11 22:57:34 +02:00
| sl.json (missing 6) | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| sr.json (missing 63) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
| | Replay |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Descriptions |
| | descriptions off |
| | Audio Track |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | The media is encrypted and we do not have the keys to decrypt it. |
| | Play Video |
| | Close |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Close Modal Dialog |
@mister-ben added task to maintain translations. closes #3572
2016-08-25 21:49:40 +02:00
| | Modal Window |
| | This is a modal window |
| | This modal can be closed by pressing the Escape key or activating the close button. |
| | , opens captions settings dialog |
| | , opens subtitles settings dialog |
| | , opens descriptions settings dialog |
| | , selected |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | captions settings |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | subtitles settings |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | descriptions settings |
| | Text |
| | White |
| | Black |
| | Red |
| | Green |
| | Blue |
| | Yellow |
| | Magenta |
| | Cyan |
| | Background |
| | Window |
| | Transparent |
| | Semi-Transparent |
| | Opaque |
| | Font Size |
| | Text Edge Style |
| | None |
| | Raised |
| | Depressed |
| | Uniform |
| | Dropshadow |
| | Font Family |
| | Proportional Sans-Serif |
| | Monospace Sans-Serif |
| | Proportional Serif |
| | Monospace Serif |
| | Casual |
| | Script |
| | Small Caps |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: localize all strings in captions settings (#3974)
2017-01-25 20:54:21 +02:00
| | Done |
| | Caption Settings Dialog |
| | Beginning of dialog window. Escape will cancel and close the window. |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| sv.json (missing 2) | Exit Picture-in-Picture |
| | Picture-in-Picture |
feat(lang): add thai language translations (#6945) Also, update translations needed docs page.
2020-11-16 21:38:02 +02:00
| th.json (Complete) | |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| tr.json (missing 13) | Audio Player |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Video Player |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently behind live |
| | Seek to live, currently playing live |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Progress Bar |
feat: allow tokens in localize, localize progress bar time (#4060) It allows you to use string as an key for the language files but have a default value that's different. In this case, we have a key of progress bar timing: currentTime={1} duration={2} which is used so that we have a descriptive key to what is happening. The default value matches that default value in en.json: {1} of {2}. The reason for the default value is so that the translation uses {1} of {2} for the actual localization without requiring en.json to be included in videojs by default. Fix #4024.
2017-02-21 23:17:00 +02:00
| | progress bar timing: currentTime={1} duration={2} |
fix: localize aria-labels (#4027) Fixes #2728.
2017-02-09 00:29:32 +02:00
| | Volume Level |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | Reset |
fix: Update translations to match correct string (#4383) The lang files were translating "all settings to the default values" instead of "restore all settings to the default values".
2017-06-28 08:31:44 +02:00
| | restore all settings to the default values |
feat: fix accessibility of the captions setting dialog (#4050) This fixes a lot of the issues from #2746 by making the dialog inherit from our actual ModalDialog which now has tab focus trapping. The Captions Settings dialog has some accessibility issues: - Field labels and fields are not explicitly associated - Keyboard focus does not move into the dialog when it is opened - Keyboard focus is not trapped inside the dialog while it is open - Keyboard focus does not return to the control which opened the dialog when it is closed - The extent (top and bottom) of the dialog is not indicated to screen readers - The dialog cannot be closed with the Esc key - The meaning of '---' in the select fields is not clear - The control to close the dialog is labeled "Done" rather than "Close" - The purpose of the "Defaults" button may not be obvious, and its effect may not be apparent to screen reader users - Focus highlighting (outline) on the Default and Done buttons is *very* hard to see - Pressing the Done button doesn’t seem to have the same effect as pressing the Close (x) button; does it trigger the same focus movement - This requirement to move it back to the triggering element is tricky, since clicking on that item in the CC menu dismisses the CC menu. I need to think about this a little more - either the menu should open again, or the focus should go to the main CC Menu Button - The focus outline on the whole dialog goes too far to the left (all the way to the edge of the video window, not just to the edge of the dialog) Fixes #2746.
2017-02-21 22:58:04 +02:00
| | End of dialog window. |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| uk.json (missing 4) | Seek to live, currently behind live |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently playing live |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
| vi.json (missing 5) | Seek to live, currently behind live |
fix(a11y): make seek-to-live better announce itself to screen reader users (#5651) To make the seek-to-live component more accessible, we hide the text that says "LIVE" from screen readers and make it be purely for sighted users. Then set the control text to be either "Seek to live, currently playing live" or "Seek to live, currently behind live" to indicate what this control does and be informative around whether we are at edge or not. Then use aria-disabled on control if we are at edge.
2018-12-11 23:40:56 +02:00
| | Seek to live, currently playing live |
fix: Add alternate text to the loading spinner. (#4916) This is a first in a few changes related to #4902. This just adds a text alternative to the loading spinner. In future PRs, we would make it alert to screen readers and potentially have a generic alerting mechanism.
2018-02-22 23:19:35 +02:00
| | {1} is loading. |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| | Exit Picture-in-Picture |
| | Picture-in-Picture |
feat(lang): add thai language translations (#6945) Also, update translations needed docs page.
2020-11-16 21:38:02 +02:00
| zh-CN.json (Complete) | |
fix(lang): improve Persian translation (#6468)
2020-02-25 00:48:01 +02:00
| zh-TW.json (missing 2) | Exit Picture-in-Picture |
| | Picture-in-Picture |
feat: Add a player option `noUITitleAttributes` to prevent title attributes in the UI (#7134) Fixes #6767
2021-03-23 23:47:16 +02:00
feat(lang): Complete work translated into traditional Chinese (#3718)
2016-11-03 22:00:29 +02:00
<!-- END langtable -->
Copy Permalink