First screen of installer inaccessible to screen readers.

[Quin]

Hi there,
When I run the Masm installer, the first screen I get is entirely inaccessible with my screen reader of choice, NVDA. All I hear is "graphic", and have to simulate a left mouse click in the middle of the window to click the next button. Is it possible for this to be looked into/fixed? All the other controls and screens read beautifully, it's just the first one.
Thanks!
BTW, sorry if this is the wrong section, I wasn't entirely sure where to post this

[zedd]

Are you talking about the Masm32 SDK installer? It was not clear to me from your post.

If that is the case the image or graphic is what needs to be clicked upon.

After clicking on that, another small window opens asking what hard drive or partition to install the Masm32 SDK into. It has a listing of all of the partitions on your computer.

You are supposed to select one, then click "OK".

A Message box then pops up, informing that the installer will run a test to determine if the MAsm32 SDK can be successfully installed on your computer. One button there "OK", when clicked another message box for the Disk Write test and another "OK" button. When clicked, another message box for the Disk Read test and another "OK" button. Yet another message box for the the succesful testing of a test executable... click "OK" to continue.

Another message box that Delete operation of the test file succeeded, click "OK".

The final box opens, click "Extract" to proceed.

A very cumbersome process to be sure... especially considering your needs.
Maybe stoo23 can arrange to have a complete Masm32 SDK installation zipped to a zip file and host it for you to download.

Then you would only need to extract the contents where you want to have the Masm32 SDK to be installed.

[Quin]

Yes, the SDK installer.

[zedd]

Yes, the SDK installer.

It is a tedious process. See my modified post above.

[Quin]

Hi,
I think you misunderstood me.
The only part that needs any modification is the first screen you mentioned. The hard drive selection onward works perfectly, it's just that first screen. The graphic needs to be given an accessible role of button, so the screen reader will see it as a tabbable and clickable control.

[stoo23]

The graphic needs to be given an accessible role of button, so the screen reader will see it as a tabbable and clickable control.

Thanks for that. Perhaps some of the members may be able to make that change.
I will bring it to their attention if they do not respond appropriately here.

I have also sent you an email.

[zedd]

Hi,
I think you misunderstood me.
The only part that needs any modification is the first screen you mentioned. The hard drive selection onward works perfectly, it's just that first screen. The graphic needs to be given an accessible role of button, so the screen reader will see it as a tabbable and clickable control.

I am not sure if that can be easily fixed. The author of the Masm32 SDK hutch--' has sadly passed away, and we do not have access to the installer source files.

Perhaps another member might be able to come up with a solution that will work for you.

In the meantime, I have been in contact with stoo23 who might have an alternative solution ...

[NoCforMe]

Hi,
I think you misunderstood me.
The only part that needs any modification is the first screen you mentioned. The hard drive selection onward works perfectly, it's just that first screen. The graphic needs to be given an accessible role of button, so the screen reader will see it as a tabbable and clickable control.

I am not sure if that can be easily fixed. The author of the Masm32 SDK hutch--' has sadly passed away, and we do not have access to the installer source files.

Maybe just ... rewrite the damn thing?

[zedd]

Maybe just ... rewrite the damn thing?

I have neither the authority, time, ambition, or sufficient knowledge to do that so that AV software will not reject it. Sorry Charlie.

I can make an installer, but AV software definitely won't like it. 
Maybe YOU would like to take a crack at it, though. 

[NoCforMe]

Maybe just ... rewrite the damn thing?

I have neither the authority, time, ambition, or sufficient knowledge to do that so that AV software will not reject it. Sorry Charlie.

I didn't mean you personally.
Surely someone here is capable of writing an installer that won't set AV alarms off.

[zedd]

I didn't mean you personally.

It sounded that way, though. My bad.

[sinsi]

Warning - old school hacking ahead

The MASM32 SDK installer is basically 3 parts
 - the main worker
 - the test exe (in the .data section using bin2db)
 - the package as a 7zip SFX (also in the .data section using bin2db)
The one thing that seems to need changing is the main "install" picture, which is a static not a button.

We could change a few things in the main worker and have it install the MASM64 SDK too

[FORTRANS]

Hi,

We could change a few things in the main worker and have it install the MASM64 SDK too

   If so, it should be optionable.  Maybe either one or both?

Regards,

Steve N.

[Quin]

Maybe just ... rewrite the damn thing?

I have neither the authority, time, ambition, or sufficient knowledge to do that so that AV software will not reject it. Sorry Charlie.

I can make an installer, but AV software definitely won't like it. 

The current masm32 installer suffers from this problem too from my experience, when trying to download the installer in firefox it warns me that it contains a virus.
Sad to hear about the creator passing away and us not having access to the source files. Guess it shows that you should always set up doomsday situations for projects 

[shantanu]

Hi,
I think you misunderstood me.
The only part that needs any modification is the first screen you mentioned. The hard drive selection onward works perfectly, it's just that first screen. The graphic needs to be given an accessible role of button, so the screen reader will see it as a tabbable and clickable control.

I am not sure if that can be easily fixed. The author of the Masm32 SDK hutch--' has sadly passed away, and we do not have access to the installer source files.

Maybe just ... rewrite the damn thing?

I second this.
Long time ago, probably a decade or more ago, I had asked Hutch as to why he used the SFX bit wrapped inside the installer, and why not use only the installer script.

I was deep into making installers of things and I even remember doing verification of the drive string, etc.

Anyway, the only reason I am replying is to show support for the idea of using *only* an NSIS script.

Regards,
Shantanu Gadgil