On 07/06/2019 07:41, Semyon Sadetsky wrote:
Yes, it is implementing this interface and provides some information via this
interface to the external tools, how it is related to the non-focusable
components? it is orthogonal things.
That means you need to keep accessibility in mind when analyzing such component
behavior.
Please stop arguing with me I've already provided enough points that the
suggested fix should be reconsidered.
But your arguments are incomplete, based on your assumption the components such
as Unfocusable Choice, Unfocusable Button, Disabled Button, or even simple
Label are non-Accessible. That's not the case. All of them are accessible via
accessibility API and as a result by the external tools such as JAWS or
VoiceOver. Using this accessibility tools the user can navigate over all
meaningful elements on the Frame despite the components attributes, focus
policy, etc.
--
Best regards, Sergey.
