<shawn> scribe: Jade
<shawn> scribe+ Brent
Not many new comments, Daniel has picked up some remaining issues with stereo in the audio
Kevin suggests we need more discussion about the digital props
Only one remaining issue with background music volume
Would be useful for more people to comment on the background level issue.
Kartoffel suggest that the background music is at the lowest it feasibly can be.
Brent, question about how they measure the sound.
Kartoffel: No way of measuring, it's all by hand, but they've suggested to editors to not change the levels from what they currently are.
Brent suggests the level in the 'Dhruv' video is a good model to follow
Kartoffel will try to match the levels of the other videos to the Dhruv video.
Kevin, comments coming in about the size of digital props, they need to be larger and the focus on elements of those props.
Kartoffel suggest that there is really limited time to edit
Kevin is exploring the possibility of additional post-edit budget
Laura, suggests the need for more full screen props.
Kevin: this is difficult for mobile device shots, but is something which needs experimenting with
Brent: focusing on elements of the page needs to be highlighted in certain props, e.g. for an error message, this needs to be highlighted more.
Kartoffel, need to be specific about zooming and aspect ratios
Brent: audio and video content matches more in the perspectives videos
Kevin: asking for comments about the intro/outro slides
Kartoffel asking about the positioning of the logo, especially in relation to the captions
There's a difference in the positioning of captions in different players
No other comments from anyone about the intro/outro slides
<shawn> scribe: Brent
<BrentB> Kevin: Any other issues or topics?
<BrentB> Kartoffel: How about the pronunciation of dyscalculia?
<BrentB> Shawn: Ask Julie to look at it and determine if the pronounciation is a problem.
<BrentB> Kevin: There is still time to review and put comments in Frame.io today.
<BrentB> Michele: What level of review are we at?
<BrentB> Kevin: This is pretty much a final review to be sure we are ready to publish, or are their other issues that need to be addressed before published.
<BrentB> ... If issues are major then we may need to cut more pieces or not publish the video at this point.
<BrentB> Kevin: Thank you everyone for the feedback. Any other feedback needs to be in by the end of the day.
<BrentB> ... Anything else for / from Kartoffel
<BrentB> Daniel: My comments, which Kevin is forwarding, are mostly about audio. I realize it may be too late to make some adjustments.
<BrentB> Kartoffel: We will have a look and try to make appropriate adjustments.
<BrentB> ... If we have any questions regarding more feedback we will email Kevin.
<BrentB> Kris Anne: There is a survey for the Authoring Tools List coming before the end of the year. We will email that out when ready. If you see anything currently, feel free to open GitHub issue now.
<BrentB> ... Looking to publish this List in January.
<BrentB> Kris Anne: Also added / updated the 2023 Face-to-face availabiltiy survey. We added some of the typical conferences/events where we could meet. Some events later in the year we don't have dates for yet but added them to the survey as well.
<Zakim> shawn, you wanted to update authoring tool list status and to ask about authoring tools sponsors
<BrentB> ... Please fill out the survey so we can make decisions about possible Face-to-face meetings.
<BrentB> Shawn: Had an issue with Filters in the Authoring Tools List not working quite right so we turned them off. Should not have too much impact as there are not many tools listed yet. We will work on this issue and get it back on when we can.
<BrentB> ... We are asking Authoring Tool vendors to submit their tools. Wondering, are we wanting EOWG to help with that?
<BrentB> Daniel: Yes, we do.
<BrentB> Shawn: Daniel and I worked on email language that we can have EOWG participants send out to any contacts you have for tool vendors.
<daniel-montalvo> https://docs.google.com/spreadsheets/d/1UhMMuINwD_v6XPIpSBYi6j2d3XpavmOtLQ1l8LeSKbc/edit?usp=sharing -> Google Sheet for Authoring Tools List Contacts
<BrentB> ... Please do soon so that we can try and have more tools entered in December.
<BrentB> Shawn: Daniel has a sheet that we are using to track who the invitation to add tools email is sent to.
<daniel-montalvo> https://docs.google.com/document/d/15mwFvH9KkGN9UrNWTYcOj0t2vBzAP7oEhKEHzz2Ey_o/edit?usp=sharing > Authoring Tools List email wording
<BrentB> ... Let's have a friendly challenge - who can think of someone they could send this email to by Monday morning?
<BrentB> Michele: If the vendor has a tool that is not very accessible, not sure they would want to list it.
<BrentB> Shawn: On the submission form the vendor can select how they conform to ATAG and can add comments about plans for future release.
<BrentB> Michele: The pushback will be by legal councel from the vendor firm, they will say that it can open them up to possible litigation or negative publicity.
<BrentB> Shawn: Just thinking about options. If these vendors have an accessibility statement and page, they could point to their page as an option.
<BrentB> Michele: They could but it would depend on how committed they are to their statement.
<BrentB> Kris Anne: Okay that we start with a small list as it would showcase them and the importance of having more accessible tools.
<BrentB> Kevin: Maybe worth having an annonymous quote from a vendor about working to get their tool on the list.
<BrentB> Shawn: If anyone has the ability to get confirmation that having this list is a motivation for the/a vendor to work on accessibility so they can eventually add their tools to the list.
<BrentB> ... Can be annonymous. Could come from the vendor or from the EOWG participant.
<Michele> * Michele loves how Brent is scribing this sensitive topic - thanks Brent
<BrentB> Jade: Question - In the default of the accessibility statement, if the vendor does not select something from the list will it say "not provided," or will it display another way.
<BrentB> Shawn: Jade would you be willing to put an issue in GitHub for that issues. A way to avoid, "not provided," "not provided," "not provided," etc.
<BrentB> Jade: Yes
<BrentB> Shawn: Agree with Jade to make non-conformance not so much a barrier to submitting a tool.
<BrentB> Laura: Agree also. We don't want to discourage vendors from submitting, and possibly calling out they don't have a statement or conforming.
<BrentB> Kevin: An option would be to instead show the guidelines that they do conform to, but have the ones they don't conform to as a sub-note or footer information.
<BrentB> Laura: Keep it seperate from features and important stuff up front and then the conformance later.
<BrentB> ... Description of the tool and Accessible Features are first.
<BrentB> Shawn: The License should be included first as well.
<BrentB> Kevin: If we can get any quotes that would be good. This is a challenging space for vendors. Any way we can help them move the needle is great.
<BrentB> Shawn: Thank you everyone. Very helpful discussion.
<krisanne> We got this feedback about the pronunciation of Dyscalculia - it’s common for people to pronounce dyscalculia in three different ways: the Dracula way that you mentioned as well as -coolia and -kewlia. In my opinion, it’s enough of a gray area that you’re OK to stick with current voiceover.
<BrentB> Kris Anne: Please complete surveys that are open. EOWG meeting availability, 2023 Face-to-face availability, and anything posted in Work for this Week.
<BrentB> Shawn: For Face-to-face survey, if you think of other locations it would be around a conference or event AND a place we can find meeting space and food/refreshments.
<BrentB> ... Many times we tie it to a specific conference because we can get a donated meeting space.
<BrentB> Kris Anne: Any events that may be in early 2024 we can add that as well for early planning.
<BrentB> Kris Anne: Meeting ajourned. Have a great weekend.
This is scribe.perl Revision VERSION of 2020-12-31 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/to ask about authoring tools sponsors/to ask about authoring tools submissions/ Default Present: Jade, Laura, BrentB, shadi, daniel-montalvo, shawn, Michele, kevin, Kartoffel_Films_folks, Mark, MarkPalmer Present: Jade, Laura, BrentB, shadi, daniel-montalvo, shawn, Michele, kevin, Kartoffel_Films_folks, Mark, MarkPalmer Found Scribe: Jade Inferring ScribeNick: Jade Found Scribe: Brent Scribes: Jade, Brent Found Date: 09 Dec 2022 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]