Wysywyg editor buttons should not be tab stops about orchard HOT 7 CLOSED

@heskew commented:

TinyMCE does already have accesskeys for each main section (http://wiki.moxiecode.com/index.php/TinyMCE:Accessibility). Would changing the tabindex on each button to -1 screw anything up as far as accessibility is concerned? Something to try I guess.

from orchard.

@bleroy commented:

Tabindex and accesskey should be independant. I'll ask an accessibility specialist what their take on it is.

from orchard.

@Jetski5822 commented:

You guys will know more than me about accessibility, but a quick google (or should i say bing ) pointed out http://dev.w3.org/html5/spec-author-view/editing.html#the-accesskey-attribute It may not be helpful, but highlights the differents between user interactions on a page for HTML 5.

from orchard.

@heskew commented:

@Jetski5822 - thanks for the link :)

@BertrandLeroy - yep, not saying they're not independent. just pointing out that TinyMCE has taken accessibility into account and has accesskeys for its main sections - also noting that if you want to take the editor buttons out of the tab flow but still have them focusable that might mess things up but I don't know for certain so, yeah, getting a specialist's take would be beneficial :) having an accesskey for each button would be fun but we would need to tackle and document general editor accesskeys early on to prevent conflict with what other modules could introduce.

from orchard.

@bleroy commented:

Tab order is broken in other ways btw.

from orchard.

@Jetski5822 commented:

@Bertrand - With the upgrade to tinymce 4.1.0, you can no longer tab to the tinymce buttons.

Would you now say this issue is closed?

from orchard.

They are no longer tab stops.

from orchard.