[improving] title suggestion #63
Comments
|
Interim Web Accessibility Repairs |
|
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. |
|
From minutes I liked the approach of [First Steps to tackle Web Accessibility Issues] OK, more brainstorms:
|
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:
|
|
Another Idea:
|
|
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 Quick fixes for critical accessibility issues Immediate remedies for critical accessibility issues How to repair some critical accessibility issues right now 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? |
|
@yatil 9-1-1 isn't the same in every country, no? Web Accessibility Emergency! Immediate fixes for critical accessibility issues |
|
@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 |
|
I like the various proposed ideas for the main title so I don't want to add more. The ones I prefer are:
I also like the subtitle that Eric came up with |
|
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. |
|
Agree with others - 'emergency' sounds too severe, and for me 'contingency' is too jargony.
|
|
Current title is "Tips for Interim Website Accessibility Repairs". @AndrewArch says:
|
|
How about some of these suggestions:
|
|
I think "Provisional Website Accessibility Repairs" ist a reasonable title I'm not so keen on "First Aid ..." On 3 May 2016 at 20:49, Shadi Abou-Zahra notifications@github.com wrote:
Andrew Arch “Man does not cease to play because he grows old. |
|
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”. |
|
+100 to @yatil's comment. Except I'm not ok with "provisional" (Eric seems ok with it either way.) |
|
@susanatx, any alternatives to "provisional" that you may be able to suggest? @AndrewArch is not comfortable with "first aid". |
|
Of the ones @AndrewArch suggested above, I think theses are ok: essential web accessibility fixes/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? |
|
alterantive suggestions for 'provisional': interim / short-term / temporary On 3 May 2016 at 22:45, Shadi Abou-Zahra notifications@github.com wrote:
Andrew Arch “Man does not cease to play because he grows old. |
|
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". |
|
I agree that the similarity with Getting Started Tips is not good. I like your suggestion. Maybe with or without sub-title:
Or turn it around to say:
Thoughts? |
|
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. |
|
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 |
|
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. |
|
/me thinks we should have that specific discussion in another thread. We can always rename documents after the relaunch. |
|
The more I think about it, Interim seems like the wrong word...how about something like |
|
I like the idea of "moving towards sustainability" somewhere in that title. 👍 |
|
Does the document say enough about moving towards sustainability? It's a rather brief section. |
|
“…start to move towards…”? |
|
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." |
|
Brent's combination suggestion - "Tips for Short Term Website Accessibility Repairs" - works for me :) |
|
How about "Tips for Short Term Website Accessibility Wins", then? |
|
Other brainstorm: "Considerations for Short Term Web Accessibility Fixes" |
|
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:
|
|
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. |
|
I like "Short Term Web Accessibility Improvements" as well. |
|
I'm good with "Short Term." |
|
As mentioned at meeting, like "First Steps Toward Web Accessibility" Also think "Stop gap measures for Web Accessibility" works. |
|
How about "Quick wins for short term web accessibility improvements"? |
|
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" :-) |
|
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 |
|
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. |
|
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:
|
|
Thanks for your review @Sylvie42. Can you say more about why you don't like "interim"? |
|
@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. |
|
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? :-) |
|
By the way, "not forever, not well paid, and not well recognized" is not too far off the message that we want to communicate... |
|
Yep, Shadi got it right, it was the combination of words used with Interim I think Sylvie 'hit the nail on the head' when she said [Interim lets me Andrew On 2 September 2016 at 20:21, Shadi Abou-Zahra notifications@github.com
Andrew Arch “Man does not cease to play because he grows old. |
|
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. |
|
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:
|
|
I like @nitedog's "First Aid in Website Accessibility: Temporary Repairs for Urgent Situations" because ...
|
|
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 |
Change title as per EOWG decision in issue #63
|
"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. |
From @susanatx in issue #62 :
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:
Please feel free to suggest other titles and reflect on these and other suggested titles.
The text was updated successfully, but these errors were encountered: