thepaciellogroup / aviewer Goto Github PK

Windows protected your PC
Windows SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk.

App: aViewer2.0.exe
Publisher:† Unknown publisher

tested on http://thepaciellogroup.github.io/AT-browser-tests/test-files/a-href.html
no focus ring is displayed and no information is displayed when the link has focus.

When trying to run aviewer on Windows 7 x64. The only thing that appears on screen is the aviewer taskbar icon.

Thank you for making a product helping me be a better webdeveloper!

But, at least for me, it's not that obvious how to use the Aviewer. Could you please add a little guide/howto, to help us get started?

Kind Regards
/Bjarni

When I tab to an interactive element, it seems the AccParent sometimes populates with what I would think should be the AccName. The AccName is not in the list on the right side top by default. The user has to open the settings and select it. I'd suggest that is the most important value to get from the tool and so should be there by default.

UI automation information is not being displayed when inspecting web content on windows 10

Such a picky issue - but is easier to find that way

Following the recent change in version numbering (which is a great start), I was wondering if we could have a further tweak...

Currently, the 32bit and 64bit versions have subtly different file version numbers (2.0.1.85 and 2.0.1.69) and the same product version (2.0.1.0). I've changed the InnoSetup file to grab the latter for the installer (so the combined installer becomes aViewer2.0.1.0.exe). However, this can be a little confusing (see #29).

Is it possible to drop the last part of the product version, so it's just "2.0.1"? (or well, for the next release, "2.0.2")?

Can you put some documentation in the readme.md file on how to compile AViewer and a description of what each file does?

So if someone wanted to help or extend AViwer they would know where to start and how the code is organized.

It seems the settings window has incorrect/missing title - see screenshots below on a fresh install

When walking the accessibility tree pane, the information in the accessibility properties window does not automatically update based on the currently selected node.

Using aViewer 32bit on Windows 10 64bit (because the 64bit version of aViewer is broken). Problem is evident with both Jaws and NVDA running. aViewer is set to display "all objects" in the accessibility tree pane.

Start using GitHub releases to distribute this.

works fine in IE 11 not in firefox or chrome

the latest build of 64 bit version does not show IA2

On Windows 7, after I uninstalled my prior versions of aViewer and installed the new 2.0.1.0 version of aViewer when I open aViewer it shows a different version number (2.0.1.69) in the title bar of the window. See screenshot below.

Just a placeholder issue, as Windows 10 final isn't out yet...but worth flagging up that in one of the recent Insider Preview builds (10162) aViewer does not seem to work at all - the application starts, I can register the .dll, but nothing is displayed. In certain situations, I can get the yellow "focus only" rectangle to appear, but even this is inconsistent.

Would be useful to have a keyboard shortcut for moving directly to each of the three panes (acc tree, acc properties and code view) within the UI. At present there is a lot of tabbing involved.

the latest developer branch exe has some issues:
it does not always update the msaa etc info when walking the acc tree pane.
it does not always report correctly the element being watched via the cursor.

Accessibility view is running and set to follow focus.
Open https://namecheap.com and click Sign In
Click the name input box - correctly shows state
Click the password box - correct shows state as protected
Click the name input box again
Click on another window
Click the password input box - incorrect object identified.

Hi, how can I find AccCTRLs unit or how can I import AccCTRLs's dll or ocx?

Have tried current release version and dev versions, the left side treeviw does not display and the HTML/ARIA info does not display in the right list view. Occurs on very page viewed.

I have installed aViewer on Win7.

When opened, it sometimes displays a little bit on info, but it seems extremely laggy, and it crashes usually after focusing some random elements in Firefox.

Do I misunderstand something here?

I am using a Windows 7 SP1 64-bit laptop.

The Tree View pane can be collapsed but then it cannot be expanded. I found that this issue with the TreeView pane getting "stuck" collapsed happens if I manually use the mouse to click on the "Collapse (or Expand) Button for TreeView" [<< button] as well as if I use the View > Collapse > TreeView menu option.

1. Once I close the left TreeView pane (by clicking on the button or using the menu option) I can't get it to open again unless I close aViewer and reopen it and manually drag the pane open with my mouse.
2. When I reopen aViewer then the TreeView pane is still visibly collapsed. The only way I can open it again is by manually using the mouse to drag the cursor to the right of the expand/collapse button. You cannot currently use the View > Collapse > Tree View menu option to toggle the pane back to an expanded state.
3. I currently cannot collapse/expand the panes using the keyboard to activate the buttons that control the panes. When I tab to the << button and activate it with the spacebar then aViewer becomes non-responsive. NOTE: I am able to repeatedly expand/collapse the two other panes (TreeList and CodeEdit) without a problem using either the mouse or the menu options but not by activating the buttons using the keyboard.

Trying the latest release on a Win7 virtual machine, and can confirm that it seems to hang/crash quite regularly (while under Win10 I'm not seeing these sorts of behaviors).

@jun325 wondering if you have a Win7 machine (either real or virtual) available to test? May be related to the IAccessible2.dll (particularly the 64bit one)?

Environment:
New Windows 10 computer with fresh install of everything

Steps:
Launch Firefox or Chrome
Launch AViewer
Inspect a text field

What happens:

• IA2 properties not displayed, even though they are selected in settings
• If you click Register IA2 DLL in settings, a strange dialog comes up (Japanese characters?). If you click OK about 20 times it goes away, but after that AViewer is locked up

Not a bug, but more of an annoyance: when using aViewer and NVDA together, whenever the treeview panel gets updated, NVDA announces that change (often getting in the way of announcing what you're actually navigating, e.g. the content on a webpage).

See video https://youtu.be/MgYO2hieirY

aViewer becomes non-responsive if I open the Settings window and attempt to change any settings (see screenshot below):

The Windows dialog that appears has the following information about the error:

Description:
A problem caused this program to stop interacting with Windows.

Problem signature:
Problem Event Name: AppHangB1
Application Name: aViewer.exe
Application Version: 2.0.1.69
Application Timestamp: 58de0cda
Hang Signature: bcc2
Hang Type: 0
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Hang Signature 1: bcc21320a354a490c52571a6d3952e86
Additional Hang Signature 2: 237a
Additional Hang Signature 3: 237acb176da410d9ef3397fa1ef5313a
Additional Hang Signature 4: bcc2
Additional Hang Signature 5: bcc21320a354a490c52571a6d3952e86
Additional Hang Signature 6: 237a
Additional Hang Signature 7: 237acb176da410d9ef3397fa1ef5313a

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\WINDOWS\system32\en-US\erofflps.txt

Similar to ThePacielloGroup/CCA-Win#2, create a proper InnoSetup installer for aViewer

I have the 2015-05-20 version of WAT installed in IE 11 on my Windows 7 SP1 64-bit laptop. When I run aViewer from WAT no content displays in the accessibility tree (TreeView) pane of aViewer. The TreeList and CodeEdit panes work fine. My colleagues are having the same problem.

I saw some other posts stating others experienced problems with Windows 7 64-bit and aViewer. Are there any possible solutions/workarounds yet?

The following blurb and link points to a webpage that no longer exists and redirects to a generic and unhelp page on the TPGi website:

For further information, see The Paciello Group's aViewer resource page.

There are some situations where it would be handy to be able to get the unique ID property from IAccessible2. For instance when cross referencing with other ATs.

For consistency with the TPG brand (and to make it slightly more visually appealing), started work on a new icon in a separate branch https://github.com/ThePacielloGroup/aviewer/tree/new-app-icon

Work is not complete here, as I believe the following still need to be resolved:

• convert all png files into a multi-image ico
• recompile the 32bit and 64bit exe files to use the new icon

https://msdn.microsoft.com/en-us/library/windows/desktop/hh437309%28v=vs.85%29.aspx

see also related mapping bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=29032#c0