New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhance Video Controls for Video Audio Description #6080
Enhance Video Controls for Video Audio Description #6080
Conversation
src/js/languages/default.json
Outdated
@@ -66,6 +67,9 @@ | |||
"pauseButton": "pause", | |||
"playButton": "play", | |||
"volumeDown": "volume down", | |||
"volumeUp": "volume up" | |||
"volumeUp": "volume up", | |||
"description": "video audio description", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we are referring to it as "Video description" below, should we just say "video description" here? OR you mentioned that "Audio description" is more common, should we be saying that across the board?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leaning towards "Audio description" myself after doing some quick googling.
src/js/languages/default.json
Outdated
@@ -66,6 +67,9 @@ | |||
"pauseButton": "pause", | |||
"playButton": "play", | |||
"volumeDown": "volume down", | |||
"volumeUp": "volume up" | |||
"volumeUp": "volume up", | |||
"description": "video audio description", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we call this key audioDescription
to tie in with the accessibility language?
@@ -1683,6 +1684,7 @@ export const generate = (baseSpacing = 24, scale = 6) => { | |||
play: Play, | |||
reduceVolume: VolumeLow, | |||
volume: Volume, | |||
description: AssistListening, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes this icon would be preferred. what is the timeline/process for getting this added to grommet icons?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would create an issue for this on grommet-icons and add it to the backlog
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From some research I was doing on where "Audio Descriptions" have already been successfully implemented (Netflix, among others), it seems like it's more of a supplemental audio track that is announced real time with the video as opposed to text on the screen like we are doing here.
For users who are deaf, closed captioning is helpful to show what is being said.
For users who are blind, audio descriptions are helpful to describe what is being shown.
The behavior seems somewhat standardized and so showing text on the screen like we are in this PR seems to deviate from that and we would want to instead support the option for someone to add an audio description track and for a user to be able to toggle that on/off in the controls. However, did any of this come up in your discussion w Bill and what he expects from an Audio Description?
for testing, i updated the Video/Controls Below story to include a to test:
things to note:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a minor comment, otherwise looks good
src/js/languages/default.json
Outdated
"showDescription": "Video description opened below video", | ||
"hideDescription": "Video description closed" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need these?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed!
… feat/video-controls-6059
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
What does this PR do?
Adds the ability to pass in a video audio description for video controls.
Where should the reviewer start?
Video.js
What testing has been done on this PR?
Manual Storybook testing
How should this be manually tested?
Storybook
Do Jest tests follow these best practices?
screen
is used for querying.userEvent
is used in place offireEvent
.asFragment()
is used for snapshot testing.Any background context you want to provide?
What are the relevant issues?
#6059
Screenshots (if appropriate)
Do the grommet docs need to be updated?
Yes
Should this PR be mentioned in the release notes?
Yes
Is this change backwards compatible or is it a breaking change?
Compatible, new feature