I'm all for making Wicket more accessible. I don't have much Java
expertise, I'm a front-end developer, so maybe I can help with any html
accessibility questions.
I think standards complient html code is the first step into making
every project accessible, but from what I've seen Wicket is well on it's
way.
The second step is making it more user friendly to disabled users. Here
is where you add tabindex attributes, labeled form elements, table
captions etc.
Let me know if I can help.
--
Sjoerd Lohuis
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500
James Renfro wrote:
Is there already an effort out there to make Wicket more accessible
for people with disabilities? It seems like the framework is
well-suited to this -- for instance, adding ARIA
(http://www.w3.org/TR/aria-roadmap/) attributes to markup tags,
setting tabindex numbers intelligently and transparently for the
developer, etc.
If nobody's working on this, is there any interest in the community
for finding a central place to hold accessible components, or else to
begin modifying the existing base-level components to make them more
accessible?
If you want more background on what I'm talking about, it might be
helpful to take a look at the following (draft) document that the
Fluid project is putting together on the subject:
http://wiki.fluidproject.org/display/fluid/DHTML+Developer+Checklist
Thanks,
James.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
