Nuno -- thanks -- these links are really helpful.
One thing I've noticed while playing around is that the bulk of these
accessibility changes require introducing tag attributes to the
component tag, for instance, adding role="wai:button" for a tag that
represents a button -- but in some cases the decision as to which role
goes to which tag will need to be made at a high level, based on the
requirements of the app itself. I can see an argument being made that
some of this stuff should be done in html by designers . . . but then
there are cases when it's nice to make the decisions at runtime.
It makes sense to me that Wicket should allow the developer to simplify
that process and abstract these attribute additions out of the html
itself -- for example, by implementing an interface with a single
method, e.g. IRoleContributor.getRole() in Component subclasses -- where
IRoleContributor could extend ITagAttributeContributor or similar. I can
accomplish this in combination with overriding Component.onComponentTag
to verify instanceof these interfaces and use tag.put(name, value) to
insert them.
Not sure if that's the best method or not, but it seems like a great
start here would be a low-level, lightweight support for adding
attributes without having to override onComponentTag. This functionality
may already be there -- I could easily have missed it. Numbering the
tabindex attributes would require something more invasive, I think --
maybe even a modification to Component, WebPage and/or Panel to do the
actual counting of sub-components that choose to present themselves as
'tabable'. Also, some support for using arrow and letter keys to
navigate (without a mouse) would be very helpful, I think. Of course
that's going to require another javascript resource along the lines of
wicket-ajax.js and wicket-event.js -- maybe wicket-accessible.js? I feel
like I might be getting ahead of myself slightly here :-)
What does everybody think?
James
Nino Saturnino Martinez Vazquez Wael wrote:
I think you should be able to use these steps to make sure its ok:
http://www.smartlabsoftware.com/wai-validator.htm
http://www.w3.org/WAI/wcag-curric/sam119-0.htm
http://www.w3.org/WAI/
regards Nino
Sjoerd Lohuis wrote:
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
