Hi All,

PB supports reading Datawindow column AccessibleName via Windows Narrator and NVDA. If you run into problems, it's recommended to do something like this:
1. If you are using PB 2019 R3 Build 2670, please upgrade to PB 2019 R3 Build 2728 or higher first.

2. If you have PB IDE installed locally, please modify the pb.ini file for PB IDE, which is in this location by default: %localappdata%\Appeon\PowerBuilder ##.0\pb.ini, you need to add ACCESSIBILITY=1 in the [Data Window] section of this pb.ini.
[Data Window]
ACCESSIBILITY=1

If you don't have PB IDE installed locally, you need to manually create a pb.ini file in the same directory as yourapp.exe and add the above content.

For more information on ACCESSIBILITY, please refer to: https://docs.appeon.com/pb2022/application_techniques/Creating.html 

3. If you are using Windows Narrator, please check the option "Read and interact with the screen using the mouse" in Narrator Settings.

4. Set the AccessibleName property in DW Column, run the PB application, launch Windows Narrator or NVAD. Then when you move your mouse over DW column, it will read the Column information, including AccessibleName.

Regards,
Ken

Dear friends,

I'm having similar problem using PB 2022 build 1892, impossible to hear column names via Windows Narrator or NVDA (Non Visual Desktop Access).
I've populated accessible tags "accessiblename" and "accessibledescription", put "accessibility=1" in "[datawindow]" chapter of PB.INI, but nothing seems to work.
I've also tried some detailed "verbose"configuration on Narrator (not yet on NVDA), no success on hearing the columns' names.

One question: PB.INI with "accessibility=1" is important in PB folder, or in application executable folder? The entire PB.INI, or only the "accessibility" directive?

Anyone with some additional info?

Thanks in advance!

José Luiz

Hi Frithjof, 

That's weird. Can you please open a ticket at https://www.appeon.com/standardsupport/newbug, so that our support staff can help you out?

Best regards, Julie

Hi Frithjof,

A number of questions for you...

1. When you say R3 do you mean 2017 R3 or 2019 R3 version?

2. Have you properly populated the AccessibleName and Description fields?

3. In PB.INI is accessibility = 1?

4. Are you testing on Windows 10?

5. Are the problems you are seeing the known issues documented in the "Remark and Explanation" column of the VPAT report?

Best regards,
Armeen

Hi Frithjof;

   What Screen Reader software are you using?

Regards ... Chris

Hi,

I don't know the answer to your question. I think there's a demo somewhere on Elevate, but ... just wanted to point out to you that I've seen questions about deactivating the accessibility instead of wanting to use it due to things like "slow behaviour of applications", especially on Citrix.

Just do a search on this forum on "accessibility".

regards.