lol ok agreed, DropDownChoice is far over the top, but someone let all those methods get through. Perhaps its time to start rolling some up and deprecating others. And getting some examples happening about how best to use the DropDownChoice component.





On 28 Oct 2008, at 15:50, James Carman wrote:

DropDownChoice

On Tue, Oct 28, 2008 at 11:48 AM, Steve Swinsburg
<[EMAIL PROTECTED]> wrote:
What are you referring to when you say DDC? The Dewey Decimal System? Used by pretty much every library around the world making it really easy to find
books? I'd call that accessible.

So my vision for wanting to enforce a bit of accessibility on the web is
narrow(?), but no one wants to move forward with the most simple of
modifications to make it easier to implement accessibility. The most basic
of things to do would be to update the JavaDocs for the API to say:

"NOTE: you should always include an AttributeModifier/Appender (or roll your own implementation) to include the title attribute on every link. here's
some examples, etc"

Or would that be too much bloat as well?


Steve





On 28 Oct 2008, at 15:35, Martijn Dashorst wrote:

There are lots of ways of making accessibility happening, but throwing more arguments to constructors isn't one of 'm. Ever took a short look
at DDC?

Instead of taking this narrow vision, perhaps start a discussion of
how we can make accessibility easy to implement, while not raping our
API?

Martijn

On Tue, Oct 28, 2008 at 4:23 PM, Steve Swinsburg
<[EMAIL PROTECTED]> wrote:

I alluded to this in a feature request for a new constructor of the
ExternalLink component in the hope that it would start the ball rolling
on
getting some accessibility happening in the rest of Wicket, but just
about
everyone that commented said it should not be implemented.

https://issues.apache.org/jira/browse/WICKET-1878

Wont fix?!  Its section 13.1 of the accessibility document!
Yes you can add it manually, but you can do many things manually. If the constructor is there it allows people to automatically take advantage of
it.
If you don't manually add it, you won't get a title on your link.

Come on, lets get some accessibility happening. Then we can tout Wicket
as
being a accessible-by-design as well!

Steve




On 28 Oct 2008, at 15:07, Nino Saturnino Martinez Vazquez Wael wrote:

Of course you should be aware that some components might not be
compliant,
but I think that's mostly in wicketstuff..

Nino Saturnino Martinez Vazquez Wael wrote:

You mean like WAI triple A?

http://www.w3.org/WAI/WCAG1AAA-Conformance

No it won't break it but it wont enforce it either..

miro wrote:

I am new to wicket and want to build web application using wicket, my application should be 508 compliance , so want to know using wicket
for
any
reason can break 508 compliance ?



--
-Wicket for love

Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

---------------------------------------------------------------------
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]


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to