Sorry, I mean<br><br>--> <a onclick="drawertool.current_drawer.selectLibrary('{@id}');"<br>--> onkeypress="if (event.keyCode != 9 ) drawertool.current_drawer.selectLibrary('{@id}');"
<br> class="kupu-libsource" title="{title}" style=""><br> <xsl:attribute name="id"><br> <xsl:value-of select="@id"/><br>
</xsl:attribute><br> <xsl:apply-templates select="icon"/><br> <span class="drawer-item-title"><br> <xsl:value-of select="title"/>
<br> </span><br>--> </a><br><br><div><span class="gmail_quote">2007/2/28, Diego Municio <<a href="mailto:dmunicio@gmail.com">dmunicio@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
First, thanks for the reply.<br><br>My problem is that I would like to insert an image in kupu by only using the keyboard (for blind users) but I can't.<br><br>I don't know if this is a desired feature for Kupu or not but I believe that this default behaviour is not
<font size="2"> very "Accessibility Compliant"...<br></font><br>In kupu 1.4, buttons tabindex are rendered as "-1" so buttons are not getting focused with 'tab' key, so if I have understood it would be nice not to have any "tabindex". That's no problem, I could remove them by modifying kupu_wysiwyg_support .
<br><br>Also in librarydrawer, I couldn't access the "Home", "Recent items" icons so I made this change in drawer.xsl<br>(changed the 'div' to 'a' and added onkeypress event)<br><br>
<xsl:template match="library"><br> <div onclick="drawertool.current_drawer.selectLibrary('{@id}');"<br> class="kupu-libsource" title="{title}" style="">
<br> <xsl:attribute name="id"><br> <xsl:value-of select="@id"/><br> </xsl:attribute><br>----> <a onkeypress="if (event.keyCode != 9 )
drawertool.current_drawer.selectLibrary('{@id}');"><br> <xsl:apply-templates select="icon"/><br>----> </a><br> <span class="drawer-item-title">
<br> <xsl:value-of select="title"/><br> </span><br> </div><br> </xsl:template><br><br><br>I could say the same with the "collection|resources" xsl:template in
drawer.xsl. I couldn't select the folders which appear in the center of the drawer... so I added this xsl:attribute:<br><br> <xsl:attribute name="onkeypress"><br> <xsl:choose>
<br> <xsl:when<br> test="local-name()='collection'">if (event.keyCode != 9) drawertool.current_drawer.selectCollection('<xsl:value-of select="@id"/>');</xsl:when>
<br><br> <xsl:otherwise>if (event.keyCode != 9) drawertool.current_drawer.selectItem('<xsl:value-of select="@id"/>')</xsl:otherwise><br> </xsl:choose>
<br> </xsl:attribute><br><br>What do you think about that?<br>Any comments are welcome<br><br><div><span class="gmail_quote">2007/2/28, Duncan Booth <<a href="mailto:duncan.booth@suttoncourtenay.org.uk" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
duncan.booth@suttoncourtenay.org.uk</a>>:</span><div><span class="e" id="q_111086e615d97fd7_1"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
"Diego Municio" <<a href="mailto:dmunicio@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
dmunicio@gmail.com</a>> wrote:<br><br>> I have seen that kupu 1.4 doesn't have tabindex...<br><br>Can you explain why an explicit tabindex would help you? A control which<br>has no explicit tabindex comes next in the order it appears in the html.
<br>A control which uses tabindex/next also comes next in the tabbing order.<br>The only time you should see a change is when the tab index is set to<br>something which isn't tabindex/next, e.g. when it gets set to 30000 for
<br>the search controls in the page header.<br><br>The problem is that unless you know a lot about the tabindex values used<br>for the other controls around you it is almost impossible to come up<br>with suitable values for tabindex.
<br><br>><br>> Well I now that in earlier versions it had a tal:attributes="tabindex<br>> tabindex" statement for each button.<br>> I wonder how can we access tabindex *object* defined in main_template,
<br>> in order to set tal:attributes="tabindex tabindex/next|nothing"<br>> instead. I can access tabindex but I don't know why... Where is this<br>> variable acquisition defined?<br>><br>> I also know that global_defines defines a global tabindex variable but
<br>> with pos=30000.. I couldn't find documentation about<br>><br>> The problem with drawers is maybe harder. As far as I know,<br>> librarydrawer renders its contents with a xslt transform, and in<br>>
drawer.xsl I cannot add tal sentences... such as<br>> tal:atrributes="tabindex tabindex/next".<br><br>Well you could except that it is rendered as a separate template so<br>unless you know a magic number to start from you would only succeed in
<br>making the drawer controls appear somewhere suprising.<br><br>><br>> Has anybody work on this? I need to improve kupu accessibility as much<br>> as possible and I would like to contribute if my knowledge is enough..
<br>><br>If you could start by explaining why the default tabbing isn't a good<br>enough solution and what you would want to achieve by changing it.<br><br><br>_______________________________________________<br>kupu-dev mailing list
<br><a href="mailto:kupu-dev@codespeak.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">kupu-dev@codespeak.net</a><br><a href="http://codespeak.net/mailman/listinfo/kupu-dev" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://codespeak.net/mailman/listinfo/kupu-dev</a><br></blockquote></span></div></div><br>
</blockquote></div><br>