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