<AWT Dev> <Swing Dev> [12] JDK-7124285: Nothing heard from VoiceOver regarding the status of the progress bar

Philip Race philip.race at oracle.com
Fri Nov 9 04:43:42 UTC 2018

On 11/8/18, 9:10 AM, shashidhara.veerabhadraiah at oracle.com wrote:
>> But your fix also changes the behaviour for the case where no 
>> accessibility is used: progress bar receives keyboard focus even 
>> though it never needs it because it does not support any input.
>> It's just the other side of the coin.
> Very true. The problem is that our software never designed from the 
> accessibility stand point of view and we are trying to use the 
> existing framework for a different purpose(focusability). Hence it 
> leads to such confusions.

Whoa. I don't know what you mean here. Maybe it is very narrow but I 
can't let this pass.
Swing was absolutely designed with accessibility in mind. Probably the 
first and maybe only UI
toolkit to have it designed in from inception. The accessibility team 
were embedded in the
Swing team. There was nothing comparable anywhere else in 1997-8 (20 
years ago!)
So Java + Swing was years ahead of anything else anyone had and it is 
not fundamentally
lacking even today.
Bugs, overlooked things, things that should be updated etc. sure.
But don't go propagating misinformation that A11Y was ignored in the design.


More information about the awt-dev mailing list