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

Re: Please Read (was RE: Survey on Media Accessibility Requirements)

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Tue, 1 Jun 2010 08:35:13 -0500
Message-ID: <AANLkTinpZKykqA7s47B-JCgRxK1dr3bxNMuVpldQFSGs@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Cc: Janina Sajka <janina@rednote.net>, Charles McCathieNevile <chaals@opera.com>
Hello everyone,

The definition of wishlist:

<q cite=<http://www.merriam-webster.com/dictionary/wishlist">
Main Entry: wish list
Function: noun
Date: 1970
: a list of desired but often realistically unobtainable items <a wish
list of useful changes>

Some requirements may not be not be technically achievable on all
devices for all users at this time but it is still useful to identify
needs in the requirements document as Janina pointed out.

As Chaals mentioned it might be good to prioritize. "Ranking" is one
of the desirable of the characteristics for a requirement
specification. Others characteristics are "complete", "consistent",
"correct", "modifiable", "traceable", "unambiguous", and "verifiable"
[1] [2]. Ranking requirements is essential for scope management.

In fact it might be helpful to prioritize requirements in multiple
dimensions. Typical schemes for prioritization of requirements include
importance to user groups, stability, risk, technical difficulty,
cost, etcetera.

Janina, you mentioned that in many instances the requirements in the
current doc are close to governmental requirements. That would also be
useful to document for the "traceable" characteristic of a good
requirements document. Requirements are not written in isolation.
Traceability provides a mechanism for finding and referring to the
origin of the requirement.

Best Regards,

[1] DOD MIL-STD-490A, Specification Practices, June 4, 1985.
[2] IEEE Std 830-1993, Recommended Practice for Software Requirements
Specifications, December 2, 1993.
Laura L. Carlson
Received on Tuesday, 1 June 2010 13:35:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:40 UTC