- From: Terry Morris <lsnbluff@gmail.com>
- Date: Fri, 30 Nov 2007 16:23:15 -0600
- To: sylvie.duchateau@snv.jussieu.fr
- Cc: "Shawn Henry" <shawn@w3.org>, EOWG <w3c-wai-eo@w3.org>
- Message-ID: <e516f4f50711301423g6f9bc82auf9830732fb074f67@mail.gmail.com>
I'm a newbie to this list so please forgive me if the acronym in my suggestion below has already been discussed and rejected by the group. Suggestion: Since WCAG is a widely recognized acronym, how about something similar, for Mobile Best Practices Content Accessibility Guidelines: MCAG or MWCAG? Terry Terry Morris Associate Professor, Web Development Harper College On Nov 30, 2007 3:13 AM, Sylvie duchateau <sylvie.duchateau@snv.jussieu.fr> wrote: > > Hello Shawn and all, > > I agree with a short title, if possible, and not too complicated acronyms.. > MWBP is difficult for me to remember : I always have to think of the > words that build this acronym to remember each letter of this acronym. > WCAG was difficult at the beginning, but I got used to it. > I like the short simple title : "How Mobile Web and Web accessibility > overlap". > What about an acronym for the words : Mobile Web and Web Accessibility", > cutting one Web would then be : Mobile Web Accessibility, that is > MoWebacc. > The Web being the bridge between Mobile and Accessibility ? > Best > Sylvie > Shawn Henry a écrit : > > > >> 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... > >> > >> > >> > >> > > > > -- Terry Morris Web Developer Foundations: Using XHTML htttp://www.webdevfoundations.net
Received on Saturday, 1 December 2007 14:17:59 UTC