Skip to content
This repository has been archived by the owner on Mar 8, 2019. It is now read-only.

catch phrase #109

Closed
nitedog opened this issue Feb 25, 2016 · 31 comments
Closed

catch phrase #109

nitedog opened this issue Feb 25, 2016 · 31 comments

Comments

@nitedog
Copy link
Contributor

nitedog commented Feb 25, 2016

From @slhenry

Related point: "Actually, it might be really neat to have a catch phrase that communicates that point (vital for some; beneficial/useful for all/others) that we use in most or all of the videos..." #41

@nitedog
Copy link
Contributor Author

nitedog commented Feb 25, 2016

Do you mean something like "[video captions] are essential for people with disabilities and helps many more" being said at the end of each video?

@shawna-slh
Copy link
Contributor

yup! except catchier :-)

"[video captions]: essential for people with disabilities; helpful for all!"

@nitedog
Copy link
Contributor Author

nitedog commented Feb 25, 2016

Doesn't that get boring after the 2nd or 3rd video? How essential do you feel this is?

@shawna-slh
Copy link
Contributor

I think it's essential that the videos communicate that message -- as I've said in other GitHub issues. I do not think it's essential that there's the exact same catch phrase at the end of every video.

I'm not sure about the "get boring". I don't know how many people will watch most of the videos in one sitting. Maybe they will just watch the one or two that people point them to? Maybe they will read the page in between videos?

Maybe the repetition would be really neat and help to tie the videos together, in addition to getting across this important point?! Maybe we have a couple or few variations on the catch phrase that we use for different videos? -- e.g., "[Video Captions]: essential for people with disabilities; helpful for all!"; "[Colors with Contrast]: handy for all; important for people with disabilities." So we make the point very clearly and have the tie-in between the videos without negative repetition?

Perhaps the production company has good perspective on these ideas?

@yatil
Copy link
Contributor

yatil commented Feb 26, 2016

+1 to @slhenry

1 similar comment
@sharronrush
Copy link

+1 to @slhenry

@nitedog
Copy link
Contributor Author

nitedog commented Feb 28, 2016

@slhenry - scripts have been revised to address this issue. Do these endings address the issue?

@yatil
Copy link
Contributor

yatil commented Feb 29, 2016

(really mild suggestion) I am OK with the contents of the phrases, but I wonder if they can be catchier. Unfortunately I don’t have concrete suggestions to help with this. Maybe something like this could work: “Captions: Essentials for people with hearing impairments, beneficial to everyone.“

@iadawn
Copy link
Contributor

iadawn commented Feb 29, 2016

I think flagging who it is essential for may become self-limiting. Maybe something more generic such as:

Captions: essential for some, beneficial for all

Or, something more aspirational/abstract

Captions: making the web possible, making the web better

@yatil
Copy link
Contributor

yatil commented Feb 29, 2016

Thanks @iadawn, I think this could generally be the right direction.

@bakkenb
Copy link
Contributor

bakkenb commented Mar 2, 2016

+1 to simple ending like this on the videos... Good suggestion Kevin.

Captions: essential for some, beneficial for all

@AndrewArch
Copy link
Contributor

+1 to catch phrase, but keep it clear and simple and to the point

@susanatx
Copy link
Contributor

susanatx commented Mar 3, 2016

@iadawn's abstract suggestion is my first choice.

If we were leaning in the direction of generic reference to user needs here are some other variations:

Critical for some
Helpful for all

Needed by some
Useful for all

@bakkenb
Copy link
Contributor

bakkenb commented Mar 8, 2016

Currently each script has a different "version" of this catch phrase. It is a bit longer than some of the examples set forth in this issue conversation. I am okay with the phrasing of the current narration of the catch phrase. They are in alignment and 'spirit' of this thread. Just wanted to check to see if others feel they really should be as short as some of the comments listed above.

@shawna-slh
Copy link
Contributor

Maybe I'm not looking at the latest versions? It seems some don't have this at all (e.g., http://w3c.github.io/wai-showcase-examples/script4.html) and other ending narrations are not catchy and not meeting the point of this thread. They are too long and too different and too dull. "XYZ allows access for people with XYZ disabilities and many more." is wimpy and does not get across the points above.

I still think the endings should be short and more similar -- not exactly the same, but very similar and with similar cadence. Could be versions of this, depending on which words best fits the topic:

XYZ: [essential/vital/critical/important/needed(by)] for some, [beneficial/useful/helpful/handy] for [all/everyone]

(I agree with Kevin not to limit to specific disabilities.)

@bakkenb
Copy link
Contributor

bakkenb commented Mar 9, 2016

If we go with the short, snappy phrase, which I am leaning more towards every moment, I like the following that I pulled from Shawn's (@slhenry) last comment:

XYZ: essential for some, beneficial for everyone

@shawna-slh
Copy link
Contributor

To clarify: I suggest that we use different words from the brackets for some topics, as appropriate -- e.g., captions and text-to-speech are essential; however, I wouldn't say that Large Activation Areas is essential, just important.

I think having minor variety is good - as Shadi (@nitedog) mentions near the top of the thread, partially to avoid being too "boring" or redundant. As long as it is the same structure and cadence, I think it will provide the nice consistency.

@bakkenb
Copy link
Contributor

bakkenb commented Mar 10, 2016

+1 to @slhenry

@James-Green
Copy link

While i think having different words for each is fine, I feel we need to have a very consistent structure and the scripts aren't there yet... I would suggest something short and memorable using one of the following structures:

  • [topic]: [essential, or important, etc.] to some; [handy, or helpful, etc.] to everyone... or
  • [topic]: [essential, or important, etc.] to [disabled user group that benefits]; [handy, or helpful, etc.] to everyone...

@susanatx
Copy link
Contributor

+1 to @slhenry and +1 @James-Green While I was reading through the scripts the "and many more" started to just feel like a shrug to me at the end. We definitely need more punch because we don't want any last impressions to be along the line of "eh, you know, accessible or something."

And I agree with James that a consistent structure - the less wordy the better - is key. Many of the ideas in this thread would work.

@yatil
Copy link
Contributor

yatil commented Mar 10, 2016

Here are some proposals based on @James-Green’s suggestions. More brainstormings, but at least something that we can talk about and see all the catch phrases in one spot, which I found helpful:

  1. Captions: Essential for people with hearing impairments; useful for everyone.
  2. High-Contrast Colors: Crucial for people with vision impairments; useful in for everyone in difficult light environments.
  3. Supporting Voice Recognition: Indespensable for people with physical disabilities; helpful for everyone in certain situations.
  4. Supporting Text to Speech: Essential for people with (some|a wide range of) disabilities; useful for everyone.
  5. Clear Layout and Design: Allows access for people with disabilities; improves the user experience for everyone.
  6. Understandable Notifications and Feedback: Essential for people with disabilities; helpful for everyone.
  7. Large Activation Areas: Needed by people with disabilities; making websites and apps less frustrating to use for everyone.
  8. Customizable Text: Makes websites readable by people with (physical?) disabilities; improves readability for everyone.
  9. Clear and Understandable Content: Crucial to provide access to people with learning and cognitive disabilities; easier to comprehend for everyone.
  10. Keyboard Compatibility: Allows access for people with physical disabilities; useful for everyone.

Note: I think some of them are still a bit long, but that stems mainly from the “people with disabilities” phrase that we need to use. I tried to be quite specific with both, the disability where the topic applies to most and the areas where the topic helps everyone. Sometimes that worked out better, sometimes not. (But who said it would be easy, right?!)

@nitedog
Copy link
Contributor Author

nitedog commented Mar 10, 2016

OK, it seems we are converging towards a common structure that most agree with. Great.

However, I'm struggling with the ending - is the use of "for everyone" or "all" too exaggerated? Are captions really useful for everyone?

@bakkenb
Copy link
Contributor

bakkenb commented Mar 10, 2016

Good question @nitedog. I don't have a critical need for captions, but I use them often for a few different reasons depending upon the circumstance.

Looking at the rest of the scripts, the only one that I have not used to this point is voice recognition. I think that is simply because I have not had a specific reason to experiment with that technology. I do believe that will become widely used in the near future though.

So, to me, these CAN all be really useful to everyone. IMHO I don't feel it is exaggerated.

@sharronrush
Copy link

yes

On Thu, Mar 10, 2016 at 3:21 PM, Shadi Abou-Zahra notifications@github.com
wrote:

OK, it seems we are converging towards a common structure that most agree
with. Great.

However, I'm struggling with the ending - is the use of "for everyone" or
"all" too exaggerated? Are captions really useful for everyone?


Reply to this email directly or view it on GitHub
#109 (comment)
.

Sharron Rush | Executive Director | Knowbility.org | @knowbility
Equal access to technology for people with disabilities

@nitedog
Copy link
Contributor Author

nitedog commented Mar 10, 2016

OK, we now have the following phrases at the end of the videos:

  • Video Captions: essential for some, useful for everyone.
  • Colors with contrast: critical for some, useful for everyone.
  • Voice recognition: essential for some, useful for everyone.
  • Text to speech: essential for some, useful for everyone. (possibly read out by text to speech)
  • Clear layout and design: important for some, beneficial for everyone.
  • Notifications and feedback: important for some, beneficial for everyone.
  • Large activation areas: critical for some, beneficial for everyone.
  • Customizable text: critical for some, beneficial for everyone.
  • Understandable content: important for some, beneficial for everyone.
  • Keyboard compatibility: essential for some, beneficial for everyone.

@nitedog nitedog removed the question label Mar 10, 2016
@yatil
Copy link
Contributor

yatil commented Mar 11, 2016

Just having „for some“ feels too generic for me. – But I’m happy to go with it, if others feel so. At least it is brief and succinct.

@nitedog
Copy link
Contributor Author

nitedog commented Mar 11, 2016

Yeah, I had that reaction too. But most cases it would need a long list and sometimes with more specific differentiation - for example, text to speech is essential for people with some types of visual disabilities and for people with some forms of cognitive and learning disabilities (combining this, like "for people with some types of visual, learning, and cognitive disabilities" is too ambiguous so we would end up with often long and confusing phrases).

@yatil
Copy link
Contributor

yatil commented Mar 11, 2016

Yeah, it gets complicated very quickly and we have the website which can go into slightly more detail.

@nitedog
Copy link
Contributor Author

nitedog commented Mar 13, 2016

Working group resolution to use the consistent format:

  • "(video subject) for an accessible web: essential for some, useful for all"

https://www.w3.org/WAI/EO/wiki/EOWG_Meetings_2016#11_March_2016_Teleconference

@nitedog nitedog removed the important label Mar 30, 2016
@nitedog
Copy link
Contributor Author

nitedog commented Mar 30, 2016

Resolution confirmed per face-to-face resolutions

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants