RadSpell's dialog should have proper tabIndex order to provide keyboard navigation. You can find attached a sample that lets you provide the desired order. When the buttons are disabled the browser should not focus them (i.e., the disabled attribute should prevent this even if tabIndexes are not modified). Related to this improvement request: http://feedback.telerik.com/Project/108/Feedback/Details/126935
Hello, TabIndex order works fine with IE and not working with Chrome and Firefox. With chrome and Firefox, the tab order is behaving like this. On RadSpell dialog is loaded, tabIndex is set to Not in Dictionary Text area, then to Close button and then to iFrame in which the focus is not visible at all. Then tabIndex to browser address bar. Hence tabIndex doesn't event go to Ignore, Ignore All and other buttons. Thanks