Opened 5 years ago

Closed 5 years ago

#863 closed defect (fixed)

Goldwave: alerts and message boxes not read

Reported by: briang1 Owned by:
Milestone: 2011.1 Component: Core
Keywords: Cc:
Blocked by: Blocking:


In Goldwave messages inside the alert boxes are not read, though any buttons are. You can read the text in these boxes if you do some object nav, namely
nvda keypad up, then just keypad right till you get to bottom. If this is the case it would be nice to have the text read.

Attached is a log more or less of the above actions on two boxes.

Test it like this.
Load Goldwave (I have 5.56 change the file, say, by inserting a marker, then save as and select mp3. When you try to save this, it will ask if you want to save the markers in a seperate file as markers are not supported. However you can only hear the text using object nav.
again if you have made any change and try to exit goldwave, it will prompt to save the changed files. However the text of the prompt is not read, only the buttons.


Attachments (1)

goldwave alerts no read.log (14.6 KB) - added by briang1 5 years ago.

Download all attachments as: .zip

Change History (4)

Changed 5 years ago by briang1

comment:1 Changed 5 years ago by briang1

About NVDA

NonVisual Desktop Access
version: main-3778


comment:2 Changed 5 years ago by mdcurran

These dialog windows use a class of TMessageForm. Question is though, should we just map TMessageForm to dialog in IAccessible's _staticMap? But we don't force role in the Dialog NVDAObject to dialog, so although tht ext then gets read, it does not announce as dialog. Is this important?
We could hardcode role to dialog in dialog behaviour, but I'm pretty sure we don't do this because we want alerts to say alert. However, then perhapos we need another behaviour class for alerts?

comment:3 Changed 5 years ago by mdcurran

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.