W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > June 2007

mechanism, or should it be \"programmatically determined\", or both?

From: WCAG 2.0 Comment Form <nobody@w3.org>
Date: Fri, 29 Jun 2007 18:32:15 +0000 (GMT)
To: public-comments-wcag20@w3.org
Message-Id: <20070629183215.BC05E47BA3@mojo.w3.org>


Name: Patrick H. Lauke
Email: redux@splintered.co.uk
Affiliation: 
Document: W2
Item Number: Success Criterion 3.1.4
Part of Item: 
Comment Type: technical
Summary of Issue: mechanism, or should it be \"programmatically determined\", or both?
Comment (Including rationale for any proposed change):
\"A mechanism for finding the expanded form or meaning of abbreviations is available\"



Should it be a mechanism, or a mechanism and/or programmatically determined, or just programmatically determined? Probably the second option (so it could cover both the use of ABBR with relevant TITLE attribute and the possibility of a separate glossary page).

Proposed Change:
\"A mechanism for finding the expanded form or meaning of abbreviations is available, or the expanded form can be programmatically determined.\"
Received on Friday, 29 June 2007 18:32:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:08 UTC