W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > October to December 2007

From Alan: Re: Mnemonic, acronym, name or handle for Mobile Web document

From: Shawn Henry <shawn@w3.org>
Date: Fri, 30 Nov 2007 07:24:46 -0600
Message-ID: <47500F1E.7070706@w3.org>
To: "EOWG (E-mail)" <w3c-wai-eo@w3.org>

>From Alan:

-------- Original Message --------
Subject: Re: Mnemonic, acronym, name or handle for Mobile Web document
Date: Fri, 30 Nov 2007 08:37:47 +0000
From: Alan Chuter <achuter@technosite.es>
To: w3c-wai-eo-request@listhub.w3.org

Hi there Dave and welcome to EO,

I like these ideas, these are new titles and acronyms. Here are my
personal thopughts on them.

COntent Guidelines for MObile Devices (COGMOD) sounds good and it's
pronounceable, although they're not new guidelines.
Accessiblilty and the MObile Web (AMOW) - is OK, it's about design for
all (people and devices).
Accessible Content for Mobile Experiences (ACME) - I like that one a
lot, but perhaps it's a bit too good; sounds like we're creating new
guidelines.

I liked Shawn and Justin's idea: "How Web Accessibility and Mobile Web
Overlap". Introducing a word to express the idea of overlap or meeting
makes it clearer. Other possible words (that are less suitable I
think) are: intersection, join, nexus, common, shared, synergy,
together, "2".

It would be good to include something about guidelines or best
practices, but I can't think of a suitable word to cover both, and not
mentioning them would cause confusion.

I would shorten it even more to simply "Web Accessibility / Mobile Web
Overlap". Possible acronyms could be WAMWap or WAMWO. These are
pronounceable. Removing the redundant "Web" gives "Web Accessibility /
Mobile Overlap" or "Mobile Web Accessibility Overlap"

Overlapping Web Accessibility & Mobile (OWAM)
Web Accessible & Mobile (WAM)
Mobile & Accessible Web (MAW)
Web Mobile & Accessible (WeMA)
Web Overlapping Mobile & Accessible (WOMA)
Web Accessibility / Mobile Overlap (WAMO, WAMWap)
Mobile Web / Accessibility Overlap (MOWA)

My own favourite is Web Accessible & Mobile (WAM).

I'll try to compile all the ideas in the thread so we can discuss them
in today's call.

regards,

Alan


On 29/11/2007, Dave Katten <dkatten@gmail.com> wrote:
> A few ideas (perhaps best for mixing and matching):
> COntent Guidelines for MObile Devices (COGMOD) - which eschews web
> altogether. Could be a dealbreaker.
>  Accessiblilty and the MObile Web (AMOW) - doesn't make it clear that this
> is content accessibility (as opposed to device)
> Accessible Content for Mobile Experiences (ACME) - would be better if we
> could ram a "Web" in there somewhere
>
> As a postscript, please consider this my belated introduction to the list.
> My name is Dave Katten and I work in Web Services as part of IT at Rice
> University. I'm hoping to evangelize our developers into creating more
> accessible webapps, but in the meantime I'm happy to ponder initialisms
> (beats finishing my dissertation). I look forward to being a more productive
> member of EOWG as time goes on and my
> experience increases.
>
> Best,
> Dave Katten
>
>
> On 11/29/07, Shawn Henry <shawn@w3.org> wrote:
> >
> > > If this is going to be a handle from the WAI site, could you just say
> "Mobile Web Overlap"?  Because it's coming from the WAI site, the
> accessibility part is understood.
> >
> > Yes, that works for handle/shortname on WAI site, though think would be
> good to have a single handle/shortname to cover it from both aspects. If a
> Mobile Web person is talking about it do we want them to use the same
> terminology, rather than each of us different?
> >
> > > For a title, how about  - "How Web Accessibility and the Mobile Web
> Overlap"
> >
> > nice. even shorter: "How Web Accessibility and Mobile Web Overlap"
> >
> > p.s. I think OK to keep this brainstorming on EOWG list only. When we have
> more concrete ideas, we should also send them to the MWBP list.
> >
> > >
> > >
> > > ******************
> > > Justin Thorp
> > > US Library of Congress
> > > Web Services - Office of Strategic Initiatives
> > > e - juth@loc.gov
> > > p - 202/707-9541
> > >
> > >>>> Shawn Henry <shawn@w3.org> 11/29/2007 2:45 PM >>>
> > >
> > > It needs something. "Relationship between Mobile Web Best Practices 1.0
> and Web Content Accessibility Guidelines" is too long. fyi, for the agenda
> and such I found myself using: "MWBP-WCAG Relationship" and "MWBP-WCAG
> Overlap"
> > >
> > > Do you hear people saying, "Accessible Rich Internet Applications Suite"
> or "new technologies to make JavaScript, Ajax, and stuff accessible"? No,
> they happily say "ARIA".
> > >
> > > Rather than think of a jargony acronym, think of a short "handle" that
> makes it easy to talk about the concept. That is, it needn't be letters from
> a title, it can be a short word or phrase that is similar to the title.
> e.g,. the "WAI-AGE" project is actually titled: "Web Accessibility
> Initiative: Ageing Education and Harmonisation"
> > >
> > > Note that it should be easy to *say*. ("MWBP" is not easy for me to say,
> and "WCAG" is not for some.)
> > >
> > > Mobile&Accessible... Mobile/Accessibility... MobAcc - MobiAcc - MobWac -
> MobiWac - AccMobi...
> > > Let the brainstorming continue... :)
> > >
> > > ~Shawn
> > >
> > >
> > > Swan, Henny wrote:
> > >> I'm wondering if it needs an acronym as well. I always acronyms with
> > >> standards or best practice guidelines but not with other documents.
> I'm
> > >> finding the use of WAC a little confusing as well as I muddle it with
> > >> Web Access Centre (WAC) which is how my team is referred to and our
> > >> online presence on the RNIB site...but that will just be me!
> > >
> > > justin:
> > >> While acronyms can be helpful, they can also act as a barrier to
> > >> understanding... they become inside baseball jargon. I'm just weary of
> > >> this important concept getting lost in one more acronym that people
> > >> would have to learn and remember.
> > >
> > > -------- Original Message --------
> > > Subject: Mnemonic, acronym, name or handle for Mobile Web document
> > > Resent-Date: Thu, 29 Nov 2007 09:37:12 +0000
> > > Resent-From: w3c-wai-eo@w3.org
> > > Date: Thu, 29 Nov 2007 10:36:54 +0100
> > > From: Alan Chuter <achuter@technosite.es>
> > > To: EOWG < w3c-wai-eo@w3.org>
> > >
> > >
> > > For the creative minds in the group or anyone who has trouble getting
> > > to sleep at night, we need to think up some short way of referring to
> > > the [breathe in] "Relationship between Mobile Web Best Practices 1.0
> > > and Web Content Accessibility Guidelines document".
> > >
> > > Liam suggested for acronyms: "MOBACC" and "MOBWAC (Mobile / Web
> > > Accessibility)"  I thought about "AccMobi" but it sounds like an
> > > existing trade name.
> > >
> > > The keywords are:
> > > Mobile Web Best Practices Web Content Accessibility Guidelines
> > > removing the redundant "Web" word gives
> > > Web Mobile Best Practices Content Accessibility Guidelines
> > >
> > > I think it would be good to keep "Best Practices" and "Guidelines" to
> > > emphasise that it's about those documents and not the concepts in
> > > general.
> > >
> > > Let's brainstorm...
> > >
> > >
> > >
> > >
> >
> > --
> > Shawn Lawton Henry, W3C Web Accessibility Initiative (WAI)
> > about: http://www.w3.org/People/Shawn/
> > phone: +1-617-395-7664
> > e-mail: shawn@w3.org
> >
> >
>
>


-- 
Email: achuter@technosite.es
Blogs
http://www.blogger.com/profile/09119760634682340619



-- 
Shawn Lawton Henry, W3C Web Accessibility Initiative (WAI)
about: http://www.w3.org/People/Shawn/
phone: +1-617-395-7664
e-mail: shawn@w3.org
Received on Friday, 30 November 2007 13:24:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 10:33:46 GMT