RE: Multiple versions of a page

Hi,

I think that the grouping I started describing would benefit screen
reader users.  Users who have older browser technology, slower
connections or PDA's could also benefit.  Another group who might
benefit is the web page developers.  The reason why I mention web site
developers is that they might be able to reduce the amount of effort
needed to determine the accessibility of web pages.  For example, the
web site developer could go through various cycles of determining how
web pages "linearize" and fixing problems identified.  Or they could
just create web pages which don't use tables and that reduces amount of
linearization checking that needs to be done.

I may not sure who loses with this grouping if another version of the
web page is developed.  Maybe part of the question is identifying what
is lost and how critical that loss is to functionality.

I think the extension to "unusable" is pretty good.  Maybe, we are
discussing a range from "best" to "sufficient" to "barely usable" to
"unusable".

Scott

>Yes, I think if we can define some obvious groupings, and explain who is the
>group that requires this obvious grouping, then we will be further along the
>track. I saw your grouping, but I think it needs to say "who benefits", and
>how there are two groups, one of whom benefits from this, and one of whom
>loses something by having this kind of grouping.
>
>The question of the difference between best and sufficient is an interesting
>one. It should be extended in my opinion - what are the differnces between
>getting a best version, getting a sufficient version, and getting an unusable
>version? How can we descriobe ways of getting the best experience possible
>for everyone, while making sure that at no stage we lead to people having an
>unusable experience?
>
>cheers
>
>Chaals

Received on Sunday, 24 March 2002 00:27:31 UTC