> 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.
Attribute modifiers. > 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? I think it is great to have serious support for this in Wicket. What we need though is someone with enough knowledge and preferably the intention to use this on a real project (eat dogfood) to gather the specs of this functionality in a coherent fashion. A good start is to open a feature request for it in JIRA and use that as a base to work on. My hunch is that much of the accessibility support won't be incredibly hard once we know exactly what we want. Cheers, Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
