I always go for accessibility and each of my links do have a title and I'd be the last one to say that accessibility (and usability) isn't important. But I think the footprint of the components should be kept as small as possible. It isn't hard to extend them anyway. If you only use titled externallinks (like I do) just subclass externallink and add an abstract method to return the title. This way you're forced to come up with a decent title - which in turn improves accessibility/usability. then you're not tempted to use a default constructor ... well just my two cents - if the JIRA goes through, I'll be fine with it too :-)
Michael Steve Swinsburg-2 wrote: > > > Hi all, > > I've just noticed a deficiency in the ExternalLink component that > doesn't allow a 'title' field to be set in its constructor. This is a > basic HTML attribute that all links should have (for accessibility and > expected behaviour). > > Currently this is only achieved by using AttributeAppender and setting > the title attribute onto the link component. I propose a new > construcotr that takes the title attribute as a parameter (or the > ExternalLink set a title by default). > > I have filed a Jira ticket here: > https://issues.apache.org/jira/browse/WICKET-1878 > > > cheers, > Steve > > > > > > > > > > ----- Michael Sparer http://talk-on-tech.blogspot.com -- View this message in context: http://www.nabble.com/no-title-in-ExternalLink-tp20030239p20211164.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
