RE: Updated Components document, comments on Implementation Cycle

> I think the bullet list order could be different, to follow the cycle
> concept:
> 
> 1 (was 2). When ... content ... developers and users.
> 2 (was 1).  When user agents ... developers.
> 3 (was 4). When developers ... authoring tool.
> 4 (was 3). When authoring tools ... content.

previous order:
- When user agents (including Web browser, media player, assistive
technologies) support an accessibility feature, users are more likely to
demand it and developers are more likely to implement it in their
content.
- When an accessibility feature is implemented in most sites (content),
developers and users are more likely to demand that user agents support
it.
- When authoring tools make a feature easy to implement, developers are
more likely to implement it in their content.
- When developers want to implement an accessibility feature, they are
more likely to demand that their authoring tool make it easy to
implement.

My thinking for this order is that the biggest roadblock to
accessibility feature implementation is UA support. If the UA doesn't
support it, the users aren't going to demand it of the content, the
developers aren't going to do it, and in turn they're not going to
pressure their AT. And even if something is supported by the AT, and
developers do it in their content, it's of no use to the end user if the
UAs don't support it.

I'm hesitant to put "- When an accessibility feature is implemented in
most sites (content), developers and users are more likely to demand
that user agents support it." first because developers just won't
implement acccessibility if it's not supported by UAs (understandably).

I agree with changing it to better reflect the cycle concept. How about:

- When user agents (including Web browser, media player, assistive
technologies) support an accessibility feature, users are more likely to
demand it and developers are more likely to implement it in their
content.
- When developers want to implement an accessibility feature, they are
more likely to demand that their authoring tool make it easy to
implement.
- When authoring tools make a feature easy to implement, developers are
more likely to implement it in their content.
- When an accessibility feature is implemented in most sites (content),
developers and users are more likely to demand that user agents support
it.

Thanks again for your input,

~ Shawn

Received on Monday, 27 September 2004 18:44:09 UTC