Re: A little back to basics (Re: Users should have (Re: Fresh start? Re: Minimal Browser Capabilities))

Hi,

While transformations can be useful in various situations as an approach
towards accessibility, I'm thinking we need to be careful to
differentiate between which transformations are desirable and which can
be readily achieved by the web page developers including testing, etc.

I've been kind of exploring some ideas not to dissimilar to what
you are suggesting about abstracts as a way to quickly size ulp
a web page when browsing by voice or on a small screen.  A format
that I keep coming back to that could appear at the beginning of appropriate
web pages would be something like:

    TITLE

    INTRODUCTION / SUMMARY

    INDEX OF SECTIONS ON PAGE

Scott


> I wasn't thinking I suggested something totally new. Just tried to 
> verbalize what we do in another way. For instance, I think that adding alt 
> text for the images of a Web page is one way to make in transformable to 
> text and from that it can be transformed to audio with the help of proper 
> devices. If the page has enough equivalent information we can do it. When 
> the end result from the transformation is usable for users with different 
> disabilities the page is accessible. The transformation itself can be done 
> in many several ways e.g. with one user agent or by using specialized user 
> agents or with some filters etc.
> 
> I do agree that there is a need to think of what are the most needed 
> transformations and if  some additional equivalents would be beneficial 
> e.g. different length abstracts of the text may would be beneficial to be 
> able to quickly glance a page while browsing with voice or show the page on 
> a small screen.
> 
> Marja

Received on Monday, 31 December 2001 22:28:28 UTC