When may we say we're done with the ACSS action item?

Al Gilman writes:
 > Reference:
 > 
 > WAI Action items status
 > http://www.w3.org/pub/WWW/WAI/group/actions.html
 > 
 > Q1:  May we say we are done with the ACSS action item?
 > 
 > Q2:  Has Chris or anyone from the Styles area looked over
 > my comments on the ACSS draft itself, and do they feel we have
 > answered their request for an accessibility review of the
 > draft?

I'll leave it for others to answer the two questions above, but comment on the
  rest of the points:

 > 
 > Discussion:
 > 
 > I think I want to claim success on the part about giving feedback
 > to the Styles team, and failure on the part about doing examples,
 > and say it's done.
The examples exist --and more than as examples--
The ACSS implementation in Emacspeak is something I use everyday
on the Wild Wild Web.


 > 
 > I can see benefit to WAI if someone were to do a demonstration
 > project of bimodal documents using ACSS and print- or screen-
Note: there is a tendency within the WAI group to think of ACSS
as a piece of "access technology" --this is not how I think of it--
ACSS is "Aural Cascading Style Sheets" and is an access enabler.
In this sense, print and Braille belong within the realm of general CSS and
  not ACSS

 > alternative styles.
 > 
 > Another valuable experiment would be a third-party restyling
 > demonstration that would take a page with print- or screen-
 > effects and, without author cooperation, analyze them and
 > allocate ACSS effects to the document using the visual styling as
 > a base of departure.
The above is exactly how I use emacspeak and the ACSS implementation --100% of
  the WWW is designed for 
visual interaction and there are *no* pages that use ACSS today-- however
emacspeak does produce well-formatted audio  documents today.

>Note that the original document doesn't
 > need to use CSS to make the latter function doable.  One could
The above as I say is obvious and done.
The reason I wrote the ACSS specification to be independent of visual
styles was with an eye to the future -- ie aural renderings should not be
  bound to the visual rendering
however as evinced by emacspeak, this does not preclude one from
having a personal aural style sheet that maps today's tags to a set of
  well-defined aural properties.

 > key the audio effects to _de facto_ classes based on contexts and
 > visual effects as much as to classes named CLASS=foo.  
 > 
 > I don't volunteer to do either of these.  I would be interested
 > to try to help with the second demo described above, but I don't
 > think I should lead it.  If someone can find volunteers from the
 > industries that originate Web content who are willing to work on
 > either of these demonstrations, the WAI would benefit from the
 > concrete experience.


 > 
 > --
 > Al Gilman

-- 
Best Regards,
--raman

      Adobe Systems                 Tel: 1 (408) 536 3945   (W14-129)
      Advanced Technology Group     Fax: 1 (408) 537 4042 
      (W14 129) 345 Park Avenue     Email: raman@adobe.com 
      San Jose , CA 95110 -2704     Email:  raman@cs.cornell.edu
      http://labrador.corp.adobe.com/~raman/raman.html (Adobe  Internal)
      http://www.cs.cornell.edu/Info/People/raman/raman.html  (Cornell)
-----------------------------------------------------------------------
    Disclaimer: The opinions expressed are my own and in no way should be taken
as representative of my employer, Adobe Systems Inc.
____________________________________________________________

Received on Monday, 14 July 1997 16:22:25 UTC