You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Barry Books <tr...@gmail.com> on 2014/06/12 14:31:04 UTC
Section 508 Compliance
I need to make a Tapestry 5.4 site 508 compliant. I've looked thru the
requirements and what HTML is generated now and I don't see anything that
looks to difficult but I'd like to get Tapestry to do most/all the work.
My plan is to write mixins to handle thinks like access keys. For example
<t:pagelink page="search"/>
Would look in the message catalog for
search-title=Do Search
search-text=Search
search-accesskey=s
and create
<t:pagelink page="search" accesskey="s" title="Do Search"><span
class="accesskey">S</span>earch<t:pagelink>
I'm also going to create a visitor to patch up things like grid link sort
titles.
Has anyone else built a 508 Tapestry site? If so any suggestions
Lastly some things might be better (like grid sort link titles) if they
were included in the base code. Would someone be willing to accept patches
and if so should they be enabled all the time or should 508 be a feature
you need to turn on?
Thanks
Barry
Re: Section 508 Compliance
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Fri, 13 Jun 2014 10:41:45 -0300, Barry Books <tr...@gmail.com> wrote:
> Personally I think mixins combined with workers are one of Tapestry
> hidden gems.
Agreed 200%. :)
> In my case I need a title on every pagelink . With a mixin applied to
> pagelink by a worker I can easily lookup a title in the message catalog
> and add it. Maybe 30 minutes of coding and it's automatically applied to
> every page link on the site (and in any libraries used).
> Contrast that with creating a new component. First pagelink only seems
> trivial because it works really well. Secondly I have to refactor the
> entire project. Lastly I can't do anything about links in a library.
I couldn't have said it better myself. ;)
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Section 508 Compliance
Posted by Barry Books <tr...@gmail.com>.
Personally I think mixins combined with workers are one of Tapestry hidden
gems. In my case I need a title on every pagelink . With a mixin applied to
pagelink by a worker I can easily lookup a title in the message catalog and
add it. Maybe 30 minutes of coding and it's automatically applied to every
page link on the site (and in any libraries used).
Contrast that with creating a new component. First pagelink only seems
trivial because it works really well. Secondly I have to refactor the
entire project. Lastly I can't do anything about links in a library.
On Fri, Jun 13, 2014 at 8:22 AM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Thu, 12 Jun 2014 18:45:21 -0300, Lance Java <la...@googlemail.com>
> wrote:
>
> Mixins are always a bit harder since you're usually manipulating the dom
>> after the default impl.
>> For something a trivial as pagelink, I'd argue that starting from scratch
>> would be easier.
>>
>
> In this case, I agree. But, as a more general solution, I'd go for a
> mixin. By the way, there's a sadly very much overlooked open source
> library, tapestry-xpath, that helps a lot in Tapestry DOM rewriting.
>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Section 508 Compliance
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Thu, 12 Jun 2014 18:45:21 -0300, Lance Java <la...@googlemail.com>
wrote:
> Mixins are always a bit harder since you're usually manipulating the dom
> after the default impl.
> For something a trivial as pagelink, I'd argue that starting from scratch
> would be easier.
In this case, I agree. But, as a more general solution, I'd go for a
mixin. By the way, there's a sadly very much overlooked open source
library, tapestry-xpath, that helps a lot in Tapestry DOM rewriting.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Section 508 Compliance
Posted by Lance Java <la...@googlemail.com>.
Mixins are always a bit harder since you're usually manipulating the dom
after the default impl.
For something a trivial as pagelink, I'd argue that starting from scratch
would be easier.
On 12 Jun 2014 16:02, "Thiago H de Paula Figueiredo" <th...@gmail.com>
wrote:
> On Thu, 12 Jun 2014 10:41:10 -0300, Lance Java <la...@googlemail.com>
> wrote:
>
> Sounds like this issue would help you here
>> https://issues.apache.org/jira/browse/TAP5-1611
>>
>
> In Barry's case, I think creating a ComponentCclassTransformerWorker to
> apply a mixin to all PageLink, ActionLink and EventLink instances is the
> way to go. No need to copy or subclass the link components.
>
> That doesn't I won't implement TAP5-1611. That's part of my to-do list in
> the Month of Tapestry campaign.
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Section 508 Compliance
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Thu, 12 Jun 2014 10:41:10 -0300, Lance Java <la...@googlemail.com>
wrote:
> Sounds like this issue would help you here
> https://issues.apache.org/jira/browse/TAP5-1611
In Barry's case, I think creating a ComponentCclassTransformerWorker to
apply a mixin to all PageLink, ActionLink and EventLink instances is the
way to go. No need to copy or subclass the link components.
That doesn't I won't implement TAP5-1611. That's part of my to-do list in
the Month of Tapestry campaign.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Section 508 Compliance
Posted by Lance Java <la...@googlemail.com>.
Sounds like this issue would help you here
https://issues.apache.org/jira/browse/TAP5-1611
BTW I had no idea what section 508 was. A link / description might help.
On 12 Jun 2014 13:31, "Barry Books" <tr...@gmail.com> wrote:
> I need to make a Tapestry 5.4 site 508 compliant. I've looked thru the
> requirements and what HTML is generated now and I don't see anything that
> looks to difficult but I'd like to get Tapestry to do most/all the work.
>
> My plan is to write mixins to handle thinks like access keys. For example
>
> <t:pagelink page="search"/>
>
> Would look in the message catalog for
>
> search-title=Do Search
> search-text=Search
> search-accesskey=s
>
> and create
>
> <t:pagelink page="search" accesskey="s" title="Do Search"><span
> class="accesskey">S</span>earch<t:pagelink>
>
> I'm also going to create a visitor to patch up things like grid link sort
> titles.
>
> Has anyone else built a 508 Tapestry site? If so any suggestions
>
> Lastly some things might be better (like grid sort link titles) if they
> were included in the base code. Would someone be willing to accept patches
> and if so should they be enabled all the time or should 508 be a feature
> you need to turn on?
>
> Thanks
> Barry
>
Re: Section 508 Compliance
Posted by Barry Books <tr...@gmail.com>.
Thanks,
Those links are very helpful. I had not seen the Kawwa components before.
On Thu, Jun 12, 2014 at 11:51 PM, Basile Chandesris <ba...@free.fr> wrote:
> It seems that Kawwa Components tries to support W3C/WAI (Web Accessibility
> Initiative):
>
> https://kawwa.atosworldline.com/accessibility
> https://kawwa.atosworldline.com/componentapproach
> https://kawwa.atosworldline.com/components
>
> --
> http://www.jimthatcher.com/sidebyside.htm
> http://www.jimthatcher.com/webcourse1.htm
>
> Le 12/06/14 14:31, Barry Books a écrit :
>
> I need to make a Tapestry 5.4 site 508 compliant. I've looked thru the
>> requirements and what HTML is generated now and I don't see anything that
>> looks to difficult but I'd like to get Tapestry to do most/all the work.
>>
>> My plan is to write mixins to handle thinks like access keys. For example
>>
>> <t:pagelink page="search"/>
>>
>> Would look in the message catalog for
>>
>> search-title=Do Search
>> search-text=Search
>> search-accesskey=s
>>
>> and create
>>
>> <t:pagelink page="search" accesskey="s" title="Do Search"><span
>> class="accesskey">S</span>earch<t:pagelink>
>>
>> I'm also going to create a visitor to patch up things like grid link sort
>> titles.
>>
>> Has anyone else built a 508 Tapestry site? If so any suggestions
>>
>> Lastly some things might be better (like grid sort link titles) if they
>> were included in the base code. Would someone be willing to accept patches
>> and if so should they be enabled all the time or should 508 be a feature
>> you need to turn on?
>>
>> Thanks
>> Barry
>>
>>
>
Re: Section 508 Compliance
Posted by Basile Chandesris <ba...@free.fr>.
It seems that Kawwa Components tries to support W3C/WAI (Web
Accessibility Initiative):
https://kawwa.atosworldline.com/accessibility
https://kawwa.atosworldline.com/componentapproach
https://kawwa.atosworldline.com/components
--
http://www.jimthatcher.com/sidebyside.htm
http://www.jimthatcher.com/webcourse1.htm
Le 12/06/14 14:31, Barry Books a écrit :
> I need to make a Tapestry 5.4 site 508 compliant. I've looked thru the
> requirements and what HTML is generated now and I don't see anything that
> looks to difficult but I'd like to get Tapestry to do most/all the work.
>
> My plan is to write mixins to handle thinks like access keys. For example
>
> <t:pagelink page="search"/>
>
> Would look in the message catalog for
>
> search-title=Do Search
> search-text=Search
> search-accesskey=s
>
> and create
>
> <t:pagelink page="search" accesskey="s" title="Do Search"><span
> class="accesskey">S</span>earch<t:pagelink>
>
> I'm also going to create a visitor to patch up things like grid link sort
> titles.
>
> Has anyone else built a 508 Tapestry site? If so any suggestions
>
> Lastly some things might be better (like grid sort link titles) if they
> were included in the base code. Would someone be willing to accept patches
> and if so should they be enabled all the time or should 508 be a feature
> you need to turn on?
>
> Thanks
> Barry
>
Re: Section 508 Compliance
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Thu, 12 Jun 2014 09:31:04 -0300, Barry Books <tr...@gmail.com> wrote:
> Lastly some things might be better (like grid sort link titles) if they
> were included in the base code. Would someone be willing to accept
> patches
Of course! :)
> and if so should they be enabled all the time or should 508 be a feature
> you need to turn on?
We can have a symbol for enabling it with a default value of true. But, of
course, we can discuss what the better default should be.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org