[kupu-dev] Kupu buttons and drawers tabindex

[Duncan Booth]

"Diego Municio" <dmunicio at gmail.com> wrote:

> I have seen that kupu 1.4 doesn't have tabindex...

Can you explain why an explicit tabindex would help you? A control which 
has no explicit tabindex comes next in the order it appears in the html. 
A control which uses tabindex/next also comes next in the tabbing order. 
The only time you should see a change is when the tab index is set to 
something which isn't tabindex/next, e.g. when it gets set to 30000 for 
the search controls in the page header.

The problem is that unless you know a lot about the tabindex values used 
for the other controls around you it is almost impossible to come up 
with suitable values for tabindex.

> 
> Well I now that in earlier versions it had a tal:attributes="tabindex
> tabindex" statement for each button.
> I wonder how can we access tabindex *object* defined in main_template,
> in order to set tal:attributes="tabindex tabindex/next|nothing"
> instead. I can access tabindex but I don't know why... Where is this
> variable acquisition defined?
> 
> I also know that global_defines defines a global tabindex variable but
> with pos=30000.. I couldn't find documentation about
> 
> The problem with drawers is maybe harder. As far as I know,
> librarydrawer renders its contents with a xslt transform, and in
> drawer.xsl I cannot add tal sentences... such as
> tal:atrributes="tabindex tabindex/next".

Well you could except that it is rendered as a separate template so 
unless you know a magic number to start from you would only succeed in 
making the drawer controls appear somewhere suprising.

> 
> Has anybody work on this? I need to improve kupu accessibility as much
> as possible and I would like to contribute if my knowledge is enough..
> 
If you could start by explaining why the default tabbing isn't a good 
enough solution and what you would want to achieve by changing it.