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.


Evaluation tool guidance

From Education & Outreach
Jump to: navigation, search

Title

from Shadi's 2 April e-mail:

ERT WG discussed this further today [4] and proposes this new title:

- "Developer Guide to Features of Web Accessibility Evaluation Tools"

We would appreciate EOWG's perspective on this new title. Also, we are not sure if it is better to use the term "Developer Guide" (commonly used term) or rather "Developers' Guide" (grammatically better?). Also if it is "Developer Guide _on_" versus "_to_ ...".

As to a short-name handle for the document, we propose "WAET Guide". Not sure how this is pronounced but probably something like "wayet". Apparently this is already a listed abbreviation according to [5].

  • I quite like the idea of subliminally improving developers' grammar, though I think "Hitchhiker's Guide" has more promise in that regard. In any event, I vote for Developer's Guide {Anna Belle}
  • In matters of grammar, I found that I nearly always agree with AnnaBelle. +1 to Developer's Guide and WAET Guide as the acronym. Also prefer "to" vs "on"{Sharron, 2 April}
  • +1 of Annabelle's grammar suggestion and of her taste in fine literature. I also prefer "to" to "on" & I like WAET as the acronym because if you say it correctly, you will sound like you're from Texas.{Jan, 3 April}
  • +1 Anna Belle's suggestion "Developer's Guide etc."{Vicki, 3 April}
  • +1 to "Developer's Guide ..." and prefer _to_ rather than _on_. JAWS does make WAET sound like a drawled "what".{Bim, 04-April-2014}
  • If I understood the discussion of last teleconference correctly, some suggested to write a long title and a short subheading, and others to wfrite a short title and a longer subheading as description. I would be in favour of the second alternative. But if all of you like this new title, it is ok for me, and I have no opinion on the grammar issue and on versus to. {Sylvie, 04-April-2014}}
  • +1 to Annabelle's suggestion {Liam, 4 April}
  • Good suggestion for title. On grammar, I reckon it should be [Developers' Guide to ...] as it is for many developers. Happy with abbreviation. {Andrew 04-April-2014}
    • Or "Developers's Guide", if we follow the recommendations of the W3C style guide... {Liam 04-April-2014}
  • comment {name}

previous

Brainstorms on title, subtitle, and shortname from EOWG 28 March telecon

  • Web Accessibility Tool Development Guide {Shawn}
  • Developers' Guide to Web Accessibility Evaluation Tool Features {Bim}
  • Guidance for Developers to Web Accessibility Evaluation Tool Features {Jan}
  • Web Accessibility Evaluation Tools Features Description {Jan, Shawn}
  • Web Accessibility evaluation tool features / a guide for tool developers {Andrew}
  • Web Accessibility Evaluation Tools Features Description for Tool Vendors (but don't like it) {Shawn}
  • Guidance for Tool Developers on Features of Web Accessibility Evaluation Tools {Shawn}
  • Tool Creators Guide to Features of Web Accessibility Evaluation Tools {Sharron}
  • Tool Developers Guide to Web Accessibility Evaluation Tools Features {Shawn}
  • Guide for Developers to Features of Web Accessibility Evaluation Tools {Jan}

General

  • summary — comment {name}

Archived Notes

template for done:

  • [done] summary — comment {name}