Important note: This Wiki page is edited by participants of the RDWG. 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.


Guideline Specification Languages

From Research and Development Working Group Wiki
Revision as of 12:11, 21 July 2011 by Mpataki (Talk | contribs)

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

[Brief synopsis of 1-2 sentences]

Contacts

Page author(s): Simon Harper

Other contact(s): [if applicable, name of other RDWG participant(s) who have particular interest and/or expertise in this research topic]

Keywords

Guidelines, Evaluation, Conformance, Specification.

Description

Would a Guideline Specification Language enable success criteria to be directly written into a hypertext language specification in a computationally amenable way - such that language validation allowed - where possible - accessibility conformance to be tested at the same time. Would this be possible or/and beneficial? Would a language enable more accurate evaluation - would it remove interpretation from the guidelines and introduce explicit checks which can be relied on to be the same across conformance platforms - and if so would we also include authoring, user agent, and mobile guidelines - one check finds all that are computationally determinable?

Background

[Additional background on the subject matter]

Discussion

  • Do we need a Universal guideline language?
  • Why would it be useful?
  • How would guidelines be specified (what would it look like)?
  • Is it possible to wtite it without knowing the target system (webpage, desktop application, ATM machine)
  • Is it possible - and if yes has it sense - to write such specification for criteria which are not even machine-testable

References

[References to related works and activities]

Back to the list of topics.