W3C home > Mailing lists > Public > public-html@w3.org > October 2010

Re: Adopting the media accessibility requirements

From: Karl Dubost <karl@la-grange.net>
Date: Thu, 28 Oct 2010 08:26:54 -0400
Cc: HTML WG <public-html@w3.org>
Message-Id: <AAF58312-98A0-40DF-AA43-0D9124E7611B@la-grange.net>
To: Maciej Stachowiak <mjs@apple.com>

In this [email][3] about [Media Accessibility Requirements][1], it is said:

	It is the extent of this challenge that compelled 
	us to approach the problem using the classical 
	technology development model--starting with user 
	requirements gathering.

The word requirements might lead to misunderstanding as we have already seen in [Henri's email][2] (Henry is making good points). It has to be clear that 

	"user requirements" differs from "implementation requirements"

The [Media Accessibility Requirements][1] says:

* "requirements of an accessibility user"
* "needs of sensory impaired users"
* "*not* a collection of baseline user agent or authoring tool requirements"
* "*not* all user agents (nor all authoring tools) will support "
* "collection of user requirements"
* "This document is our inventory"

I guess from the introduction it is clear that the document is more about collecting some needs and the way they have been implemented in current softwares (even if imperfect). Unfortunately the rest of the document has a language which turns into a very implementation requirements more than user stories. 

User stories are usually more useful for implementers because they help to devise right strategies for implementations or come up with solutions which are not necessary the ones which we are used to. It also removes the frustration of domain expertise and help the two parties to focus on the issues to solve more than the way to solve it. 

Then the [email][3] continues with:

	We are to the point where we need to begin engaging 
	the wider HTML 5 community in understanding the 
	ramifications of these requirements, and in 
	collaborating on appropriate solutions.

Would it be possible to add at the start of the Media Accessibility Requirements a sentence giving the status of the document along:

	This document is a draft. The intent of the current 
	inventory is to give materials for defining implementation
	requirements for Media Accessibility for HTML5. This 
	document is not an implementation requirements document 
	for HTML5. 

I guess it would be useful for Henri and others to repeat under which forms they would prefer to get the Media Accessibility Ideas under the form of a generic template. 

[1]: http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Requirements
[2]: http://www.w3.org/mid/1432845596.205607.1288255134250.JavaMail.root@cm-mail03.mozilla.org
[3]: http://lists.w3.org/Archives/Public/public-html/2010Aug/0327.html

Karl Dubost
Montréal, QC, Canada
Received on Thursday, 28 October 2010 12:27:17 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:06 UTC