On 11/11/2018 05:30, shashidhara.veerabhadra...@oracle.com wrote:
This fix works for both windows and mac. Mac may have a short cut to ignore
such things but we still need to solve the problem for windows and for mac(for
TAB key traversal case). TAB key is consumed by java swing for traversal
purpose and hence TAB key traversal is assumed to work for accessibility case
as well and it does work for with this fix. So why deny that?
Hope this answers your question. Accessibility is a new area to explore here
for everyone I think and am also learning along with these fixes. So please let
me know if you have any more questions.
This assumption is wrong, the components should be accessible even
they are have a focus or not, can be focused or not, editable or not,
enabled or not, in all these cases the accessibility tool should
be able to provide this information to the user.
--
Best regards, Sergey.
