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 ?
--
View this message in context:
http://www.nabble.com/wicket-and-508-compilance-tp20208921p20208921.html
Sent
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
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?
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
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
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
On Tue, Oct 28, 2008 at 4:48 PM, Steve Swinsburg
[EMAIL PROTECTED] wrote:
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
For the Javadoc? (please stop being so vague!)
No worries, I'll do this up and submit it into a general accessibility
Javadoc improvement Jira ticket.
Steve
On 28 Oct 2008, at 15:57, Martijn Dashorst wrote:
On Tue, Oct 28, 2008 at 4:48 PM, Steve Swinsburg
[EMAIL PROTECTED] wrote:
So
I don't think Martijn is intentionally being vague. DDC is a common
abbreviation for DropDownChoice among folks within the Wicket
community. As for the request for a patch, that's the best way to
get your code suggestions merged into the codebase, providing a patch.
Please make sure you
Well the last post was unclear about which patch he was referring to
(Javadoc or codebase).
From the previous discussions, it's clear that a patch for a new
constructor won't be considered. I will, however, get some information
to extend the Javadocs and submit that.
Javadco improvement
both 1899 and 982 are pretty friggin vague :)
how often are link titles dynamic? i am thinking not very often at
all, so why add another imodel slot to make the component event bigger
for a small percantage of usecases.
in most cases a wicket:id=external-link title=
i also dont want to have another constructor with that title parameter
But if there are a certain amount of components that could use something for
accessibility then i am more for just a method
setTitle(IModel model)
or something like that
johan
On Tue, Oct 28, 2008 at 5:15 PM, Steve
I don't understand why you keep insisting that a title attribute should
always be included in an anchor. In most cases the text within the
anchor tag is enough information for what the purpose of the link is,
certainly if you think a minute about that text. In such cases a title
attribute will
13 matches
Mail list logo
