Skip to content
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

[improving] title suggestion #63

Closed
nitedog opened this issue Apr 23, 2016 · 55 comments
Closed

[improving] title suggestion #63

nitedog opened this issue Apr 23, 2016 · 55 comments

Comments

@nitedog
Copy link
Contributor

nitedog commented Apr 23, 2016

From @susanatx in issue #62 :

A more engaging title the makes its purpose clear from the start, e.g "Quick Fixes (or tips) for Improving the Accessibility of Your Website Now," (less words would be better.) The current title is too similar to other resources and doesn't convey this page's purpose well. Let's make it clear these are quick fixes and things that can be done right away.

There was agreement with this suggestion during the EOWG call on 22 April 2016, with some wording brainstorms.

Some of the proposals for a new title based on this initial brainstorm include:

  • Web Accessibility Contingency Plan/Tips
  • Web Accessibility Emergency Plan/Tips
  • Contingency Tips for Improving [the Accessibility of] Your Website
  • Temporary [Accessibility] Fixes for Your Website
  • Adopting Accessibility During a Running Web Project
  • Interim/Provisional Accessibility Repairs for Your Website
  • Interim/Provisional Accessibility Considerations for Your Website
  • Last-Minute Accommodations for Web Accessibility

Please feel free to suggest other titles and reflect on these and other suggested titles.

@sharronrush
Copy link

Interim Web Accessibility Repairs
(with possible subtitle) What to do while developing your long term accessibility plan

@susanatx
Copy link
Contributor

I'm letting these roll around in my head before I can offer any other suggestions. They definitely identify the purpose of the document better but I'm not crazy about the words chosen.

@shawna-slh
Copy link
Contributor

shawna-slh commented Apr 26, 2016

From minutes I liked the approach of [First Steps to tackle Web Accessibility Issues]
It also rings nicely with "Easy Checks - A First Review of Web Accessibility"
/me re-looks at the document, especially the intro & #62 ...
hum, currently it has lots of "Tips"... wonder if any issues around confusion with our other Tips for Getting Started ?

OK, more brainstorms:

  • Web Accessibility Now - Tips for Fixing an Inaccessible Website
  • Tips for Fixing Website Accessibility
  • Quick Fixes - Tips for Getting Going on Web Accessibility

@yatil
Copy link
Contributor

yatil commented Apr 27, 2016

  • How to quick fix the most severe accessibility issues on your website

    …and get on track to implement a sustainable accessibility plan

Edit: Rationale – Using the heading to make clear that this is only a quick fix for severe accessibility issues and the subheading to make clear that the end goal is a sustainable accessibility plan. Other ideas:

  • Quick fixes for the most severe accessibility issues
    …and how to get from there to a sustainable accessibility plan
  • Emergency fixes for the most severe accessibility issues
    …and how to get from there to a sustainable accessibility plan

@yatil
Copy link
Contributor

yatil commented Apr 27, 2016

Another Idea:

  • 911-WEB-ACCESSIBILITY – Web Accessibility Emergency Fixes

    … and how to get from there to a sustainable accessibility plan.

@susanatx
Copy link
Contributor

I really like "quick". "Emergency" sounds too dreadful and panicky. What about "critical" instead of "severe"? A severe problem maybe more than can be done quickly. /me reads minutes
Okay, good points against "quick" although I think the meaning it conveys is still appropriate. What did people not like about "first aid"? Altered suggestions based on some of those above:

Quick fixes for critical accessibility issues
…and how to move towards a sustainable plan (dropped repeated "accessibility" in subtitle.)

Immediate remedies for critical accessibility issues
…and how to move towards a sustainable plan

How to repair some critical accessibility issues right now
…and how to move towards a sustainable plan"

Are we giving them enough in this one-pager to actually a develop a sustainable plan or aren't we rather highlighting those steps and pointing them elsewhere?

@susanatx
Copy link
Contributor

@yatil 9-1-1 isn't the same in every country, no?

Web Accessibility Emergency! Immediate fixes for critical accessibility issues
… and how to get from there to a sustainable accessibility plan.

@yatil
Copy link
Contributor

yatil commented Apr 27, 2016

@susanatx – Yes, it is differently everywhere, but I thought it might be a good starting point. :-)

What about:

Don’t Panic! Immediate fixes for critical accessibility issues
… and how to get from there to a sustainable accessibility plan.

@bakkenb
Copy link

bakkenb commented Apr 27, 2016

I like the various proposed ideas for the main title so I don't want to add more. The ones I prefer are:

  • How to repair some critical accessibility issues right now
  • Immediate fixes for critical accessibility issues
  • Quick Fixes - Tips for Getting Going on Web Accessibility

I also like the subtitle that Eric came up with
…and how to get from there to a sustainable accessibility plan

@nitedog
Copy link
Contributor Author

nitedog commented Apr 28, 2016

Just a reminder that during the call we agreed to move away from terms like "quick" and "immediate", because they are relative - is 2 days/weeks/months quick? (btw, this is also the reason why "quick checks" was changed to "easy checks").

Also, we agreed to clearly communicate that many of these "fixes" are temporary patches but they are often not really ideal or even real fixes. In some cases it may even be too late to rescue accessibility (eg. purchased product the day before launch). Ideally we can reflect this aspect in the title too.

@AndrewArch
Copy link
Contributor

AndrewArch commented Apr 29, 2016

Agree with others - 'emergency' sounds too severe, and for me 'contingency' is too jargony.

  • essential web accessibility fixes/repairs
  • first pass at web accessibility fixes/repairs
  • addressing basic web accessibility
  • getting started with web accessibility repairs

@nitedog
Copy link
Contributor Author

nitedog commented May 3, 2016

Current title is "Tips for Interim Website Accessibility Repairs".

@AndrewArch says:

However, 'interim' doesn't work for me. Also sounds too close to "Tips for
Getting Started with Web Accessibility"
How about something simpler like "getting started with web accessibility
repairs"?

@nitedog
Copy link
Contributor Author

nitedog commented May 3, 2016

How about some of these suggestions:

  • Provisional Website Accessibility Repairs
  • First Aid in Website Accessibility: Temporary Repairs for Urgent Situations

@AndrewArch
Copy link
Contributor

I think "Provisional Website Accessibility Repairs" ist a reasonable title
option

I'm not so keen on "First Aid ..."

On 3 May 2016 at 20:49, Shadi Abou-Zahra notifications@github.com wrote:

How about some of these suggestions:

  • Provisional Website Accessibility Repairs
  • First Aid in Website Accessibility: Temporary Repairs for Urgent
    Situations


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#63 (comment)

Andrew Arch
Canberra, Australia

“Man does not cease to play because he grows old.
Man grows old because he ceases to play.”
George Bernard Shaw

@yatil
Copy link
Contributor

yatil commented May 3, 2016

I think both are OK. However for me – as a non-native speaker – “first aid” is easier to understand. “Provisional” sounds very abstract in comparison. I think we could go without the subtitle, even if we use “first aid”.

@susanatx
Copy link
Contributor

susanatx commented May 3, 2016

+100 to @yatil's comment. Except I'm not ok with "provisional" (Eric seems ok with it either way.)

@nitedog
Copy link
Contributor Author

nitedog commented May 3, 2016

@susanatx, any alternatives to "provisional" that you may be able to suggest? @AndrewArch is not comfortable with "first aid".

@susanatx
Copy link
Contributor

susanatx commented May 3, 2016

Of the ones @AndrewArch suggested above, I think theses are ok:

essential web accessibility fixes/repairs
getting started with web accessibility repairs

The language is more engaging and accessible to all readers. But does this convey our tone as clear as the title with "first aid"?

Thoughts, folks?

@AndrewArch
Copy link
Contributor

alterantive suggestions for 'provisional': interim / short-term / temporary
/ stop-gap / expedient

On 3 May 2016 at 22:45, Shadi Abou-Zahra notifications@github.com wrote:

@susanatx https://github.com/susanatx, any alternatives to
"provisional" that you may be able to suggest? @AndrewArch
https://github.com/AndrewArch is not comfortable with "first aid".


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#63 (comment)

Andrew Arch
Canberra, Australia

“Man does not cease to play because he grows old.
Man grows old because he ceases to play.”
George Bernard Shaw

@dboudreau
Copy link

As a non-native English speaker, words like "provisional" force me to stop, and analyze what it is we mean. So I'm in agreement with Eric. To quote Krug, please don't make me think. Of all the proposal ideas I've read so far, Susan's proposal for "getting started with web accessibility repairs" seems like the easiest and most straightforward, but it does sound like the other "Getting started" resource. I'm not a big fan of "first-aid" either.

I guess what suggestion right now would be something like "First steps to web accessibility repairs".

@nitedog
Copy link
Contributor Author

nitedog commented May 3, 2016

I agree that the similarity with Getting Started Tips is not good. I like your suggestion. Maybe with or without sub-title:

  • First Steps to Website Accessibility Repairs
  • First Steps to Website Accessibility: Temporary Repairs and Measures

Or turn it around to say:

  • First Repairs for Website Accessibility

Thoughts?

@dboudreau
Copy link

The thing I'm wondering is, just how many resources labelled something like "getting started...", "first steps...", "introduction to...", "beginning with..." or any other derivatives are we going to create before we realize that we may need to restructure those documents in a way where there's only a need for a few introductory resources, based on overarching topics. I think the exercise about information architecture with the redesign will help us identify this.

@sharronrush
Copy link

Thanks Denis, just what I was thinking. The "getting Started Tips..." should perhaps be inclusive of all of these quick and easy assets we have been making for the last few years.

+1 to thinking about the architecture of the new site and to incorporating this into that process. Anna Belle has been prepping for the F2F and the redesign workshop and sends this as an IA guide: Information Architecture for the Web and Beyond http://shop.oreilly.com/product/0636920034674.do

@susanatx
Copy link
Contributor

susanatx commented May 3, 2016

More +1 beginning to think about the architecture of the new site. The resources we've been working on recently might end up needing title tweaks. I also would like us to continue reviewing our tone, voice, and overall reading grade level (a US-specific term, I know) as we look to this restructure and reviews of resources.

I don't remember if I put that specific item on the agenda suggestions for the F2F but it warrants at least the beginning of a discussion. I would like more background info from the workgroup as to the original intended audience as well as voice for the site as a whole. Plain language is so important for accessibility so I'm going to keep banging that drum.

@yatil
Copy link
Contributor

yatil commented May 3, 2016

/me thinks we should have that specific discussion in another thread. We can always rename documents after the relaunch.

@sharronrush
Copy link

The more I think about it, Interim seems like the wrong word...how about something like
"Short term accessibility repairs
…and how to move towards a sustainable plan"

@dboudreau
Copy link

I like the idea of "moving towards sustainability" somewhere in that title. 👍

@nitedog
Copy link
Contributor Author

nitedog commented May 4, 2016

Does the document say enough about moving towards sustainability? It's a rather brief section.

@yatil
Copy link
Contributor

yatil commented May 4, 2016

“…start to move towards…”?

@bakkenb
Copy link

bakkenb commented May 4, 2016

I agree with Shadi, right now the document does not have steps/tips to help "move towards sustainability." It strongly states that this is not the best approach for addressing accessibility and that a more comprehensive plan (that includes sustainability) should be implemented as soon as possible after using this resource.

It is Short Term and I like Sharron's suggestion around that. It is a repair and not a plan for implementing accessibility practice in an organization. How about combining Sharron and Andrew's ideas "Tips for Short Term Website Accessibility Repairs."

@AndrewArch
Copy link
Contributor

Brent's combination suggestion - "Tips for Short Term Website Accessibility Repairs" - works for me :)

@dboudreau
Copy link

How about "Tips for Short Term Website Accessibility Wins", then?

@shawna-slh
Copy link
Contributor

shawna-slh commented May 5, 2016

Other brainstorm: "Considerations for Short Term Web Accessibility Fixes"

@sharronrush
Copy link

sharronrush commented May 5, 2016

I do not like Tips, it seems inappropriate. "Considerations" is good but another one of those $50 words that add to the weight of title. Let's lighten it up, here are a few more brainstorms:

  • Access barriers? An approach to fixing them while making your long term plan.
  • Short term accessibility fixes
  • Removing accessibility barriers for the short term
  • short term web accessibility improvements

@yatil
Copy link
Contributor

yatil commented May 5, 2016

I think “tips” should in general be reserved for the Getting Started Tips. I like “Wins”. “Short term web accessibility improvements” sounds good to me.

@bakkenb
Copy link

bakkenb commented May 5, 2016

I like "Short Term Web Accessibility Improvements" as well.

@susanatx
Copy link
Contributor

susanatx commented May 6, 2016

I'm good with "Short Term."

@hkramer
Copy link

hkramer commented Aug 26, 2016

As mentioned at meeting, like "First Steps Toward Web Accessibility"

Also think "Stop gap measures for Web Accessibility" works.

@dboudreau
Copy link

How about "Quick wins for short term web accessibility improvements"?

@hkramer
Copy link

hkramer commented Sep 1, 2016

My - those are a lot of suggestions. I like the Interim, stop-gap, short-term because they because I think it matches the need of the use-case. Someone new to a11y who needs to correct their website quickly.

I'd avoid "tips" or "quick" or "first steps" terminology because it sounds like our other resources.

Or how about: "Get out of town: Quick web accessibility repairs" :-)

@AndrewArch
Copy link
Contributor

yep - we need to convey that this is not the final nor complete solution

I like 'interim' as it conveys that something more/better is coming
'stop-gap' and 'short-term' have similar connotations, but not quite so strongly for me

@clangston3
Copy link

My one concern with comments like short-term or stopgap is that it might deter people from implementing them at all. It would be easy for a PM to see that and think, "we won't address this until we can do it correctly." Maybe I'm overthinking it, and this can be solved through strong introductory text.

What about "Bridging to Accessibility" or something like that?

The researcher in me wants to do some word association, It can't sound like a half measure, even if we know that's what it is.

@Sylduch-Conseil
Copy link

After reading the whole discussion and the mail from Shadi. I don't like interim or provisional. But I found some previous suggestions all right:

  • How to repair some critical accessibility issues right now
  • Immediate fixes for critical accessibility issues

@nitedog
Copy link
Contributor Author

nitedog commented Sep 2, 2016

Thanks for your review @Sylvie42. Can you say more about why you don't like "interim"?

@yatil
Copy link
Contributor

yatil commented Sep 2, 2016

@nitedog Andrew, Sharron were also (mildly) uncomfortable with interim, and it is not my favorite as well. (It does not strike me as a particularly common word to describe this, but then English is not my mother tongue and what do I know :-D)

I think the title needs to be very clear that this is an emergency plan, but I am out of ideas at this point, so I likely go with the group’s decision.

@Sylduch-Conseil
Copy link

@nitedog, I can't explain why. Interim lets me think about a job that is not for ever, that is not well paid and not well reconigsed. I agree with @yatil's comment. It's not my mother tongue and I will support the group's final decision.

@nitedog
Copy link
Contributor Author

nitedog commented Sep 2, 2016

Thanks @yatil and @Sylvie42. @AndrewArch seems to have come around at least twice since (3rd May and 2nd Sep). I asked him offline to provide more thoughts so that we can debate the different options. At this time there is no clear favorite for all, and "interim" seems to be better than "provisional" and "short term" - or is it? :-)

@nitedog
Copy link
Contributor Author

nitedog commented Sep 2, 2016

By the way, "not forever, not well paid, and not well recognized" is not too far off the message that we want to communicate...

@AndrewArch
Copy link
Contributor

AndrewArch commented Sep 2, 2016

Yep, Shadi got it right, it was the combination of words used with Interim
back in may that put me off, but the latest suggestions work well for me.

I think Sylvie 'hit the nail on the head' when she said [Interim lets me
think about a job that is not for ever] which is exactly what I think we
want to convey in the title of this document. This is about some quick
fixes that only go part of the way to repairing the in-accessibility bu
tackling some of the worst issue; they are 'interim' until you can tackle
the full job, or rebuild the site with accessibility in mind from the start.

Andrew

On 2 September 2016 at 20:21, Shadi Abou-Zahra notifications@github.com
wrote:

By the way, "not forever, not well paid, and not well recognized" is not
too far off the message that we want to communicate...


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#63 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGzo78vY6Fv7AVlWHi_oXm5GOyThe7_Wks5ql_iOgaJpZM4IOImv
.

Andrew Arch
Canberra, Australia

“Man does not cease to play because he grows old.
Man grows old because he ceases to play.”
George Bernard Shaw

@dboudreau
Copy link

As a French speaker, I'm siding along with @Sylvie42. That's exactly how "interim" resonates for me, too. It also feels unnecessarily stuffy and complicated. Not a fan, but then again, I'm never really a fan of uncommon words if I can help it. I feel that if we want to address more than intellectual folks or people who come from a more educated background, we should try using more layman terms. It would help to bring our message across. Which is why I liked "quick wins" the most - or maybe "short-term".

But I have no dog in this fight, so I'll go along with whatever the group decides.

@yatil
Copy link
Contributor

yatil commented Sep 2, 2016

Thanks for the clarification, @nitedog and @AndrewArch. In Germany “interim” is usually used for replacement coaches while football ⚽ clubs are searching for the next permanent coach. With that context in mind, it makes sense to call the document “Interim Website Accessibility Improvements”. Still feels slightly weird to me in context.

Playing around with some other ideas:

  • Temporarily fix the most severe accessibility blunders on your website.
  • Accessibility blunders hotfixes
  • Hotfixes for website accessibility

@vuxcaleb
Copy link
Contributor

vuxcaleb commented Sep 2, 2016

I like @nitedog's "First Aid in Website Accessibility: Temporary Repairs for Urgent Situations" because ...

  • It's catchy
  • It's simple
  • It uses universal words
  • The keyword "temporary" drives the point this is not long-term or final

@shawna-slh
Copy link
Contributor

shawna-slh commented Sep 2, 2016

@nitedog
Copy link
Contributor Author

nitedog commented Sep 20, 2016

Resolution on new title taken during EOWG teleconference discussion on 9 Sept 2016 following Survey results on title question: Web Accessibility First Aid: Approaches for Interim Repairs

@nitedog nitedog closed this as completed Sep 20, 2016
nitedog added a commit that referenced this issue Sep 20, 2016
Change title as per EOWG decision in issue #63
@brewerj
Copy link

brewerj commented Dec 13, 2016

"First Aid" sounds medicalized.

This doc might be a candidate for an improved title in the future. Not urgent for now.

Actually, "Approaches for Interim Repairs" sounds much clearer.

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

No branches or pull requests