Re: FW: Questions and proposed approaches for Baseline Specifics

  
> 1) What do we mean by a technology.  Do we mean a particular specification
> or a general type?

I'm wondering whether the current definition of "technology" in the WCAG2.0 
Glossary [1] is sufficient to answer Question 1 previous.  I found a 
definition of "technology" (from [2]) as "electronic or digital products or 
systems considered as a group").  Although this definition is overly general, 
does it have aspects we might want to consider in a possible revision of our 
definition of "technology" (for example, the "grouping" concept, which seems 
to me to be absent in the WCAG2.0 definition, which lists items in singular 
terms, that is, "markup language, programming language, style sheet, data 
format, or API")?

> 
> 2) What if there is an extension of a technology that someone developed.  Is
> it included?  What about modules that extend a technology?  If they are
> supported by User agents including AT - shouldn't they be part of baseline?
> Are they?

The QA Framework: Specification Guidelines (extensibility section [3] gives 
some discussion of extensibility, with links to other discussions on 
extensibility and versioning.  Perhaps some of this information might be 
useful in consideration of an answer 
to Question 2 previous? 
 
> 
> 3) What if there are features of a technology that are NOT supported by AT.
> And if using them would make a page (or that part of the page) inaccessible?
> Can they be used WITHOUT providing an accessible alternative?

What is a definition of a "feature"?  How granular do we want to be?
For example, CSS2.1 [4] defines a feature as "a section or subsection of a 
specification". 

Thanks and best wishes
Tim Boland NIST 


[1]: http://www.w3.org/TR/WCAG20/appendixA.html
[2]: http://www.webopedia.com/TERM/t/technology.html
[3]: http://www.w3.org/TR/qaframe-spec/#extensions
[4]: http://www.w3.org/TR/CSS21/
 

Received on Thursday, 7 September 2006 12:12:02 UTC