Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Auto-enable accessible objects in Chrome
The Chrome web browser supports accessible objects in web pages, but this is disabled by default. QM tries to auto-enable it on demand, but with current Chrome version it fails.

You can explicitly enable Chrome accessible objects: run chrome.exe with command line --force-renderer-accessibility
Copy      Help
run "chrome.exe" "--force-renderer-accessibility"

But there is a better way.
The simplest way - create this function and assign this trigger (to read how, click the small ? links below). The trigger enables Chrome accessibility. The function itself is empty and never runs.
Function enable_chrome_acc_t
Trigger $a 2 1 "" "" "" "" "" "" 8     Help - how to add the trigger to the macro
QM must be running when starting Chrome process. If QM is not running all the time, instead use this:
Make exe from this function, and let it run at Windows startup. For example, add a shortcut to it to the Startup folder, which is in the Start menu. Let the exe run all the time. If you want to end its process, use Task Manager.
Function enable_chrome_acc
Copy      Help
;mes 1
opt waitmsg 1; wait -1
UnhookWinEvent hh

#sub Hook_SetWinEventHook
function hHook event hwnd idObject idChild dwEventThread dwmsEventTime

if idObject=1
,IAccessible a; VARIANT v
,AccessibleObjectFromEvent(hwnd idObject idChild &a &v)

;main_function  enable_chrome_acc
;exe_file  $my qm$\enable_chrome_acc.exe
;icon  <default>
;manifest  $qm$\default.exe.manifest
;flags  6
;guid  {35DE25AC-7AD6-4AD8-805A-65B7532D84BC}

Forum Jump:

Users browsing this thread: 1 Guest(s)