Important note: This Wiki page is edited by participants of the EOWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.


Eval Methodology title brainstorming

From Education & Outreach
Revision as of 00:37, 23 March 2012 by Shawn (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Nav: EOWG wiki main page

latest draft of document currently titled "Website Accessibility Evaluation Methodology for WCAG 2.0 (WCAG-EM)"

New ideas and favorites from below

@@ add yours here ! @@

  • Shadi: ...I stumbled over a previous suggestion that I really like:
    "Website Accessibility Conformance Evaluation Methodology (WACEM)"
    The title is very precise and succinct, and is also apt for having an own version number because it does not have WCAG in the title. Maybe the acronym WACEM (pronounced "wack 'em") is not serious enough but we could play around with alternatices (like stick with WCAG-EM?).

EOWG discussion of 27 Jan

  • WCAG Conformance Methodology - Web Inspection, Sampling, Evaluation = WCAG-WISE
  • WEVAL "we val"
  • WCAG Conformance Methodology - Inspection, Sampling, Evaluation = WCAG-WISE
  • WCAG Conformance - Web Inspection, Sampling, Evaluation = WCAG-WISE
  • RISE = Reporting, Inspection, Sampling, Evaluation
  • Sampling, Applying, Reporting Conformance Evaluation to WCAG - SARCEval, WCAG-RISE
  • WCAG Conformance Methodology for Reporting, Inspection, Sampling, Evaluation WCAG-RISE
  • WCAG Conformance Evaluation Methodology - WCAG-CEM
  • WCAG Conformance Evaluation Methodology for Websites and Web Applications - WCAG-CEM
  • WAI MESA - Metholology for Evaluating Site Accessibility
  • Site evaluation for accessibility methodology SEAM
  • Conformance Sampling, Inspection and technical Evaluation for WCAG2. C-SITE for WCAG2
  • WCAG SIR (sampling, inspection and reporting)

Liam 20 Jan (from e-mail)

Last week I was all up for coming up with an Acronym that resulted in EWOK or NINJA or similar. Now not so sure! But WCAG-EM comes up with lots of references to WCAG and em units, so NOT that.

Thoughts on naming - test all versions to see if they are gogin to be easy to find when Googled. For example, EARL is not - too many other things called EARL. WCAG-EM is similarly not going to be easy - Google associates WCAG-EM with stuff in WCAG mentioning em units. So... something with non-standard spelling like NINJAA or 3-WOK would be better than NINJA or EWOK. In fact, I *really* like 3-WOK. Manages to combine leet-speak with pronouncability (three-wok). And a starwars reference, natch.

[additional to mailing list] Note that EARL was an attempt at an example of a naming decision from years past that has resulted in something that's not terribly findable (although if you Google W3C EARL you get it as top result). My main request would be to avoid WCAG-EM as it will be overwhelmed by references to em units in WCAG. Sadly both Ninjaa and 3-wok are already out there too. Appending or prepending something to WCAG would help (but not 'EM', as noted above).

WCAG-EVAL? {Shawn: WCAG-Eval seems very clear and straightforward (aside from my previously mentioned hesitation with using "WCAG" at all).}

28 Oct Denis says:

Based on our discussions from last friday's meeting in EO and yesterday's meeting at EvalTF, I feel I'm sold to the relevancy of a short catchy name. But finding one is a difficult task...

I also think we need to evacuate "website" from the equation in favor of something else. Still not sure about "web information system" as it is a mouthful, but I do believe it is more accurate than website and covers more broadly.

So, to follow up on the naming ideas that were brought up, I'd like to propose the following for brainstorm... Hack away!

So,

  • Using WISE:
    • Web Information Systems Evaluation
    • Web Inclusion Strategy for Evaluation
  • Using AWARE:
    • Accessible Web Applications Review Examination
    • Applied Web Accessibility Review Examination
  • Using EQUAL:
    • Evaluation for QUalified Accessibility Level
    • External Qualification for Universal Access Label

I know most don't make a lot of sense. I'm hoping they could spark some ideas, so there just meant as a base for discussion. It seems to me that using one of those acronyms would allow us to call this the WISE-, AWARE- or EQUAL-methodology, which would bring a warm, fuzzy feeling to it and would sound kind of cool. Not to mention being much easier to remember and to pronounce than "WAEM" for example.

From 26 Oct e-mail

One particularly interesting idea was potential use of "web information system" or "web-based information system" as opposed to "website". This helps overcome the in clarity that "websites" includes web applications, mobile sites, intranets, and other types of web-based systems. What do people think of the term "web information system" in place of "website"?

This term also lends itself to new sets of title and acronyms. Examples raised include:

  • Web-Based Information System Accessibility Evaluation (WISE)
  • Web-Based Information System Accessibility Conformance Evaluation (WISE)
  • Web-Based Information System Accessibility Conformance Evaluation Methodology (WISACEM)

Other random brainstorm ideas from EOWG included:

  • Website Accessibility Conformance Evaluation Methodology (WACEM)
  • Website Accessibility Review Evaluation (aWARE)
  • Website Accessibility Review (aWARe)
  • Evaluation Quality Accessibility (EQuAl)
  • Accessibility Quality Assurance (AQuA)
  • Quality Accessibility Check (QAC)

earlier brainstorms

The following is from 19 October e-mail thread:

The WCAG 2.0 Evaluation Methodology Task Force (Eval TF) is developing a methodology for evaluating website conformance to WCAG 2.0.

We would like your input on a title and shortname for this Methodology. Currently the TF is considering this title: "Website Accessibility Evaluation Methodology" The direct acronym from this title would be WAEM and the TF also considered WAM or WEM for easier pronunciation. We also considered shortnames that are not specifically bound to the initials of the title, such as SiteAccess or WCAG-check, though none seemed particularly good.

Additional brainstorms:

Website Accessibility Evaluation Methodology

Methodology for Assessing Website Conformity to WCAG 2.0 Some issues and questions raised include:

  • it does not include the word "accessibility" (though it is part of the acronym WCAG, which we would likely expand in the title anyway);
  • should it be "WCAG 2.0" versus "WCAG 2" (to cover all 2.x versions);
  • should we use the term "assessing" versus "evaluation";
  • should we use the term "conformity" versus "conformance";
  • the title does not lend itself to a catchy acronym.

Here are some more ideas to play around with:

  • Methodology for Assessing Website Conformance to WCAG 2
  • Methodology for Evaluating Website Conformity to WCAG 2
  • Methodology for Evaluating Website Accessibility Conformance
  • Methodology for Conformance Evaluation of Websites for Accessibility
  • Conformance Evaluation of Websites for Accessibility
  • Conformance Evaluation of Websites to WCAG 2
  • Sampling, Inspection, and Technical Evaluation [of Websites for WCAG 2.0] (SITE) ... especially when used in combination like "WCAG 2.0 SITE"
  • Methodology for Assessing Website Conformity to WCAG 2.0 (MAC)

Candidate titles (alternative suggestions still welcome): - Methodology for Evaluating Website Accessibility Conformance (MEWAC) - Website Accessibility Evaluation Methodology for WCAG 2.0

Also proposal: Website Evaluation Methodology for WCAG 2.0 (Accessibility is in WCAG we provide the WEM for that)

Open brainstorming for shortname:

  • AccessCheck
  • CheckAccess
  • SiteAccess
  • WCAG*Check
  • AccessSite
  • WCAG*Site
  • SiteCheck
  • CheckSite
  • WAMBAM
  • MCEWA (Methodology for Conformance Evaluation of Websites for Accessibility)
  • CEWA (Conformance Evaluation of Websites for Accessibility)
  • CEW2WCAG2 (Conformance Evaluation of Websites to WCAG 2)
  • UWEM (Unified Web Evaluation Methodology)
  • SITE (no meaning yet)
  • MAWA (Methodology for Assessing Website Accessibility)
  • MDWC (Methodology for Determining Website Compliance)
  • EWAMAC (Evaluation Methodology for Assessing Website Accessibility Conformity)
  • EMAWC (Evaluation Methodology for Assessing Website Conformity)
  • WEM (Website Evaluation Methodology for WCAG 2.0)

Some acronyms are already existing organizations or festivals (including MEWAC).

Alternatives:

  • Conformance Evaluation of Websites for Accessibility (CEWA or Conf)
  • Accessibility Conformance Evaluation of Websites (ACEW)
  • Conformance/Conformity Assessment Procedure (CAP)
  • Conformance/Conformity Assessment Methodology (CAM)
  • Website Accessibility Evaluation (WAE)
  • Website Accessibility Assessment (WAA)
  • Website Accessibility Methodology (WAM)
  • Website Accessibility Assessment Procedure (WAAP)
  • Website Accessibility Assessment Methodology (WAAM)
  • Website Accessibility Evaluation Procedure (WAEP)
  • Website Accessibility Evaluation Methodology (WAEM)
  • Website Accessibility Inspection Procedure (WAIP)
  • Website Accessibility Inspection Methodology (WAIM)

Not serious:

  • Conformance of Websites (CoW, WCAG-CoW, or WAI-CoW)
  • Accessibility Conformance of Websites (A-CoW)
  • Procedure for Accessibility Inspection (PAI like "pay")
  • Procedure for Evaluation of Accessibility (PEA)
  • Procedure for Evaluation of Accessibility Conformance (PEACe)
  • Accessibility Evaluation of Websites (AEW)
  • Harmonized Assessment Methodology (HAM)
  • WCAG 2.0 Harmonized Assessment Methodology (WHAM)
  • Website Conformance Assessment Guidelines (WCAG)

See also Vicki's reply,