W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2001

RE: Modularization

From: Kynn Bartlett <kynn-edapta@idyllmtn.com>
Date: Mon, 20 Aug 2001 15:34:57 -0700
Message-Id: <a0510030db7a7400d74ef@[10.0.1.17]>
To: "Charles F. Munat" <chas@munat.com>, "WAI-GL" <w3c-wai-gl@w3.org>
At 3:16 PM -0700 2001/8/20, Charles F. Munat wrote:
>Damn! Considering how much time I spend with modularized XHTML, why didn't I
>think of this?
>This is an ideal refinement. Modularized accessibility.

Meaning what, though?  What constitutes a module and how are they
used?  In XHTML, modules are primarily intended as a way of being able
to swap in and swap out various bits and pieces, and generally build
your own language within the "XHTML family."

What would be the purpose of accessibility "modules"?  Along what lines
would they be split?  How and when would different "modules" be used?

How would it be any different from "sections" as we have them now?

See, I don't think this is necessarily a terrible idea, but it needs
some expansion and we don't simply solve all our problems by throwing
the m12n buzzword at them.  Modules are broken out in XHTML for very
specific purposes -- so they can be used or removed or replaced
easily -- not simply as a synonym for "section".

Before I buy into this modularized accessibility idea, I need to know
more about what's involved and what you do with it.

--Kynn

-- 
Kynn Bartlett <kynn@reef.com>
Technical Developer Liaison
Reef North America
Accessibility - W3C - Integrator Network
Tel +1 949-567-7006
________________________________________
BUSINESS IS DYNAMIC. TAKE CONTROL.
________________________________________
http://www.reef.com
Received on Monday, 20 August 2001 18:41:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:11 GMT