Accessbility complaint on Radspell screen (i.e., tab is not working on Radspell screen)?

[Burepalli V S Rao]

Hi,
I noticed that after opening the Radspell screen if we press the tab then it is not going to the controls present in the screen instead it is going to the address bar.now my question is , Is there any way to provide the tabindex to the controls present in the Radspell screen or at least focus to the first control? I know it's bit of a silly question, but a bug has been filed about it and I have to investigate.

Thank you!!
Burepalli V S Rao.

[Rumen]

Hi BVS Rao,

The standalone RadSpell control does not offer section 508 compliance. I logged your feature request in our PITS system with ID 3133. If more people request this feature we will raise its priority level.

I also updated your Telerik points in your account for your help on enhancing RadSpell.

Currently, my suggestion is to use the inline spellchecker of RadEditor which is section 508 compliant. You can move between the misspelled words using TAB, to choose suggestions using the top and bottom arrow keys and press Enter.

Kind regards,
Rumen
the Telerik team

[Priyanka]

Hello, I have the same issue and I am using Q12014 ASP.NET AJAX RadSpell.
Do you think it is fixed if so, can you please send me the code?.

Thanks

[Marin Bratanov]

Hello,

RadSpell has focus when the dialog is opened in later versions so things should be OK.

Could you try with this simple markup, invoke the spellcheck and see whether tabbing gets you out of the dialog?

<asp:TextBox ID="Textbox1" runat="server" Text="miztake" />
<telerik:RadSpell runat="server" ID="RadSpell1" ControlToCheck="Textbox1" />

You can also use the browser's console and, when the dialog is opened, see what document.activeElement is. It should be the iframe (because it has its own document object and the parent page would not know the exact details). You can run this command to get in the iframe object in the dialog and see the exact element: $find("RadSpell1_dialogOpenerSpellCheckDialog").get_contentFrame().contentWindow.document.activeElement
where RadSpell1 should be the ClientID of the spell control.


Regards,

Marin Bratanov
Telerik

 

 

[Priyanka]

Tab Order is not correct. First focus is on Suggestions ListBox and then to 'Undo' (Disabled), Close and then Browsers addressbar, then Ignore, IgnoreAll etc.
Is there any way we can change the Order from Suggestions to Ignore, IgnoreAll, Add Custom, Change, ChangeAll and then to Close button.
Also when Undo button is disabled we dont' need the focus applied on this button when tabbing.

We are using Q12014 version of ASP.NET AJAX controls.

Thanks

[Marin Bratanov]

Hi Priyanka,

I am attaching here an example that will let you set the tab indexes as desired and focus the main button as desired. You can extend this to match your needs (e..g, add a function to check the last tab index and, if needed, apply it to the undo button). Or, you can simply add a tabIndex to it, too.

You can track these improvements in the following feedback portal pages:

• http://feedback.telerik.com/Project/108/Feedback/Details/126937-add-tabindex-attributes-to-the-radspell-dialog-elements
• http://feedback.telerik.com/Project/108/Feedback/Details/126935-improve-radspells-dialog-should-focus-the-ignore-button-by-default

I hope this helps.


Regards,

Marin Bratanov
Telerik

 

 

[Priyanka]

Thank you for your responce. It works as expected for tab order. Only issue was with "Undo" button when disabled, still the focus in on. Is there any way we can by pass focus on Undo Button when disabled?.

[Marin Bratanov]

Hi,

The buttons have, by default, tabIndex=-1, thus the browser should skip them. What I can suggest is adding a couple of lines to the script I showed that will:

• set the tabIndex of the dialogControl_Undo button to -1
• set the disabled attribute of the dialogControl_Undo button to "disabled" (note that I cannot guarantee this will not cause it to remain disabled even when it should not)
• set the tabIndex of its parent anchor to -1 just in case.

If this does not help, then it would seem your browser goes through all elements on the page regardless of their state.


Regards,

Marin Bratanov
Telerik