Skip to content
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.

title #10

Closed
shawna-slh opened this issue May 5, 2016 · 33 comments
Closed

title #10

shawna-slh opened this issue May 5, 2016 · 33 comments

Comments

@shawna-slh
Copy link
Contributor

shawna-slh commented May 5, 2016

brainstorming on subtitle

Accessibility, Usability, and Inclusion:

  • Working Together on a Web for All
  • Cooperating for a Web for All
  • Synergies for a Web for All
  • Synergestic Aspects of a Web for All
  • Related Aspects of a Web for All
  • Combined Aspects of a Web for All
    ...
@yatil
Copy link
Contributor

yatil commented Nov 19, 2016

For context: The currently proposed title is

“Accessibility, Usability, and Inclusion: Related Aspects of a Web for All”.

Above are other brainstorms.

@yatil
Copy link
Contributor

yatil commented Nov 19, 2016

I think the “Related Aspects of a Web for All” works well as a subtitle. +1 for keeping it that way.

@susanatx
Copy link

+1

@shawna-slh
Copy link
Contributor Author

"Related Aspects of a Web for All” is fine and I have no objections to it, however something like

Working Together on a Web for All

Is much more active and friendly and encouraging -- which I really like. :-)

@nitedog
Copy link
Contributor

nitedog commented Nov 30, 2016

Devil's advocate: encouraging to do what? This document does not really propose any specific actions or provide any "do's" - working together on what? We previously had mismatch between the expectations raised by the title and the actual content, so I want to be cautious of that.

@yatil
Copy link
Contributor

yatil commented Nov 30, 2016

I think it is a more reference-type of document, and the current subtitle underlines that. I am happy to defer to the editor.

@sharronrush
Copy link

Agree with Eric, this document does not really provide guidance for "working together," +1 to the current subtitle.

@shawna-slh
Copy link
Contributor Author

Just to make sure what I said previously wasn't lost:

"Related Aspects of a Web for All” is fine and I have no objections to it

@bakkenb
Copy link

bakkenb commented Dec 1, 2016

[medium]

Not sure a I like the "Web for All" portion.

"Accessibility, Usability, and Inclusion: Understanding these terms and how they relate"
"Accessibility, Usability, and Inclusion: Why you should know the difference"
"Accessibility, Usability, and Inclusion: Not interchangeable, understand the difference"

@shawna-slh
Copy link
Contributor Author

shawna-slh commented Dec 2, 2016

Data point: Some activities that focus on accessibility have started using "Web for All".

This may be a reason for including "Web for All" in the title -- and also for getting in the search results for "Web for All".

At the same time, I think Brent's approach may be useful in better communicating the purpose of the document. More brainstorms:

  • Accessibility, Usability, and Inclusion: Understand the Differences Related to a Web for All
  • Accessibility, Usability, and Inclusion: Understand the Differences in a Web for All
  • Accessibility, Usability, and Inclusion: Understand the Differences and Relationships in a Web for All
  • Accessibility, Usability, and Inclusion: A Comparison of Related Aspects of a Web for All
  • Accessibility, Usability, and Inclusion: Understand the Differences and Relationship
    ...

Yeah, these are longer, but since it's just sub-title, I think that's OK.

@nitedog
Copy link
Contributor

nitedog commented Dec 2, 2016

From Howard:

I think the sub-title is okay but it's a little awkward. I think I would try to simplify or clarify it.
Some suggestions:

  • Commonalities, Differences and Application
  • Translating these approaches to practice
  • Commonalities and Differences

@shawna-slh
Copy link
Contributor Author

shawna-slh commented Dec 2, 2016

/me notes Howard's and Brent's approaches are similar - to explain the purpose more

@yatil
Copy link
Contributor

yatil commented Dec 2, 2016

All are good for me.

@yatil
Copy link
Contributor

yatil commented Dec 2, 2016

Another idea for a title for editor’s discretion:

How Accessibility, Usability, and Inclusion are related

@shawna-slh
Copy link
Contributor Author

Title discussion in 2 Dec telecon

@shawna-slh
Copy link
Contributor Author

I'm still fine with:

Accessibility, Usability, and Inclusion: Related Aspects of a Web for All

and I still slightly/mildly favor including the buzz-phrase "Web for All"

I think this is the most succinct and descriptive title, and I'd be OK with it:

How Accessibility, Usability, and Inclusion are Related

However I note in the minutes at last one -1 for starting with "How". Another brainstorm:

Understanding How Accessibility, Usability, and Inclusion are Related

But I don't like that -- it's seems a bit to preachy or something. :(

@nitedog
Copy link
Contributor

nitedog commented Dec 7, 2016

How about "web for everyone" (playing on TimBL's "this is for everyone" tweet):

  • Accessibility, Usability, and Inclusions: Related Aspects of a Web for Everyone
  • Accessibility, Usability, and Inclusions: Aspects of a Web for Everyone
  • Accessibility, Usability, and Inclusions in a Web for Everyone
  • Accessibility, Usability, and Inclusions: A Web for Everyone
  • A Web for Everyone: Accessibility, Usability, and Inclusions

@sharronrush
Copy link

sharronrush commented Dec 7, 2016 via email

@nitedog
Copy link
Contributor

nitedog commented Dec 7, 2016

Yes, sorry. I don't know how the "s" got in there. Typo!

@bakkenb
Copy link

bakkenb commented Dec 7, 2016

To me, I see this resource as more of an article rather than our usual "how to," or "you need to do this" type resources. That said, I see two ways to go here. Option 1 - Name the article with a descriptive name so that people will know what the article is going to be about before they start reading it, kind of like success criteria 2.4.9 :). Option 2 - Name the article with a creative, catchy name so that people are intrigued to start reading it to find out what it is about. Both of these options are used all the time in naming articles. I am fine with either option that the group likes best.

Based on the latest input on this discussion, these would be my choices for either Option we feel is best.

  • Option 1 (descriptive) - "Accessibility, Usability, and Inclusion: Understanding these terms and how they relate"
  • Option 2 (creative) - "Accessibility, Usability, and Inclusion: A Web for Everyone"

@yatil
Copy link
Contributor

yatil commented Dec 7, 2016

@bakkenb, I think those are two great options, in principle and in practice.

For this document, I’d go with option 2 (creative) – but in general I think we could use this as general guidelines for naming resources. Do you mind if I put this on a wiki page?

@bakkenb
Copy link

bakkenb commented Dec 7, 2016

Feel free to do so @yatil

@James-Green
Copy link

I vote for option 2.

@susanatx
Copy link

susanatx commented Dec 8, 2016

+1 for #2

@AndrewArch
Copy link
Contributor

"Accessibility, Usability, and Inclusion: Related Aspects of a Web for All" still works for me, but @bakkenb's suggestion of "Accessibility, Usability, and Inclusion: A Web for Everyone" is more succinct and still captures the idea that there are overlaps.

@hkramer
Copy link
Contributor

hkramer commented Dec 8, 2016

I probably would have leaned towards option 1 but I'm warming up to 2. If that's the consensus I'm on board. Eric's comment that it was more creative swayed me and I think 2 does have more poetry.

@yatil
Copy link
Contributor

yatil commented Dec 8, 2016

@hkramer – Actually that was @bakkenb’s comment. Can’t take credit for everything ;-)

@lakeen
Copy link

lakeen commented Dec 8, 2016

+1 for option 2

@shawna-slh
Copy link
Contributor Author

I think it's good/important to keep the "related" idea in the title -- It's telling people what this document does. I don't think "Accessibility, Usability, and Inclusion: A Web for Everyone" communicates it clearly enough.

I think it's better to have a longer more descriptive title, than a short _un_clear title.

So I'd prefer "Accessibility, Usability, and Inclusion: Related Aspects of a Web for Everyone"

(I also suspect there are aspects of "a web for everyone" that are not covered in "inclusion" — if so, then the shorter title is inaccurate by leaving things out.)

I'd like folks to think about these points... and then if the group decides they want the shortened version, I won't object. :-)

@nitedog
Copy link
Contributor

nitedog commented Dec 8, 2016

Which aspects of "a web for everyone" is not covered in "inclusion"?

@susanatx
Copy link

susanatx commented Dec 8, 2016

Where did my reply to @slhenry go? argh... I originally was thinking short, sweet, and catchy but now I'm leaning towards your point. I had thought of that as well and then decided, no, it's too long. But the catchy title doesn't really describe the purpose of the article - which is to show how the three relate as well as differ. I retract my +1.

Although I'm not sold on "Web for Everyone" being necessary (or adding much to) the title, I'm okay with "Accessibility, Usability, and Inclusion: Related Aspects of a Web for Everyone." If it helps with searching and cohesion with other concepts then it works for me. But having "Related" or similar is important.

@AndrewArch
Copy link
Contributor

if "relationship" is important, and I appreciate that it is, what about "Accessibility, Usability, and Inclusion:
Related Aspects"? as a shorter title? Do we really need the "for a Web for Everyone"?

@nitedog
Copy link
Contributor

nitedog commented Dec 9, 2016

EOWG decided to call it "Accessibility, Usability, and Inclusion" (that is, sub-title is dropped) Minutes of 9 December 2016

@nitedog nitedog closed this as completed Dec 9, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants