Absence of success criterion for deprecated and obsolete features

Name: Treasury Board of Canada Secretariat (Common Look and Feel Office)
Email: clf-nsi@tbs-sct.gc.ca
Affiliation: Government of Canada
Document: W2
Item Number: Guideline 4.1: Maximize compatibility with current and future user agents...
Part of Item: 
Comment Type: general comment
Summary of Issue: Absence of success criterion for deprecated and obsolete features
Comment (Including rationale for any proposed change):
Why is there no success criterion (not even a \"AAA\") that requires deprecated and obsolete features to be avoided? For instance, obsolete features in Java are generally not compatible with the Java Accessibility Bridge which would result in significantly decreased compatibility with screen readers. Same for deprecated features in HTML/XHTML which can also result in decreased accessibility (such as limiting the ability of users to configure a Web page to meet their accessibility needs). 

Proposed Change:
Add a success criterion that covers deprecated and obsolete features.

Received on Monday, 28 January 2008 19:12:42 UTC