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
images proposed resolutions on big images #93
Comments
Agree to the resolutions.
|
|
Planning and audio image: I'm not fully convinced by it but I don't have a better idea. I'll leave it to the decision of the group. |
Planning and audio image: I like the map icon |
Resolutions accepted in 16 August 2019 EOWG teleconference |
(This is related to #9 , yet I didn't want to add clutter to that issue, so opened this issue instead.)
Please see the images under How to Make Audio and Video Accessible
Note: These are still drafts. Once we decide on the concepts, then the graphic artist will polish them up to have similar line widths, visual weight, etc.
EOWG previously agreed on the concepts for these images:
Two new images are available for review under How to Make Audio and Video Accessible:
Planning Audio and Video Media - based on the map image used in other Plan page
Audio Content and Video Content - covering creating new content
PROPOSED RESOLUTION: Use these 7 images.
New concepts for another image are right aligned with and under the heading:
8. Transcribing Audio to Text
Options:
8.a. Don't have an image with this page. (It's conceptually different than the other pages.)
8.b. Use the speaker|hello concept:
8.c. Use the sound waves|hello concept:
8.d. Try other concepts, for example:
8.d.1. change "hello" to "text"
8.d.2. try replacing "hello" with a keyboard
8.d.3. something else...
We are very tight on budget for the graphics for this resource. (We're not going to get all that we listed in #9 ) Therefore, I propose that for this version of the resource we go option 8.a. Don't have an image with this page.
PROPOSED RESOLUTION: No image for 8 for this release.
The text was updated successfully, but these errors were encountered: