RE: [more] naming for "Methodology"

I like this one best:

Methodology for Evaluating Website Accessibility Conformance  (MEWAC)

If we don't mention WCAG then we don't have to worry about 2.0 or 2.X.  In
the documentation we will have information on WCAG  so I don't think we need
it in the name  - accessibility is better.


Kathy

Phone:  978.443.0798
Cell:  978.760.0682
Fax:  978.560.1251
KathyW@ia11y.com 

  

NOTICE: This communication may contain privileged or other confidential
information. If you are not the intended recipient, please reply to the
sender indicating that fact and delete the copy you received. Thank you.


-----Original Message-----
From: public-wai-evaltf-request@w3.org
[mailto:public-wai-evaltf-request@w3.org] On Behalf Of Shadi Abou-Zahra
Sent: Monday, October 10, 2011 4:01 AM
To: Eval TF
Subject: [more] naming for "Methodology"

Dear group,

It seems that there is some support for:
  - 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

The previous ideas are included below too. Happy brainstorming.

Best,
   Shadi


On 6.10.2011 07:18, Shadi Abou-Zahra wrote:
> Dear group,
>
> As trivial as it may sound it is time for us to think about a name for 
> the Methodology, so that we can start fleshing it out.
>
> Here are some brainstorms to get your creativity flowing:
>
>
> # Favorites:
> - 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)
>
>
> # 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)
>
>
> Best,
> Shadi
>

--
Shadi Abou-Zahra - http://www.w3.org/People/shadi/ Activity Lead, W3C/WAI
International Program Office Evaluation and Repair Tools Working Group (ERT
WG) Research and Development Working Group (RDWG)

Received on Monday, 10 October 2011 12:41:14 UTC