User Verification - Change of Context - Action Type (Desktop)

Modified on Fri, 4 Sep at 6:53 PM

Product

CommonLook PDF Desktop Version


Feature

Verification (User Verification statuses/checkpoints)


Document Element

Actions — specifically the document's Open Action, but the same logic applies to actions on Bookmarks, links, and JavaScript 


Issue

You receive a User Verification status during a verification in which CommonLook flags a checkpoint that references an "action" attached to something in the document, most commonly the document's Open Action, with a trigger type such as "Go To (a) Destination." The Description warns that this action "does not initiate a change of context," which can read as an alarming, technical warning even though in the vast majority of cases there's nothing actually wrong. 


Symptom 

During verification, a checkpoint appears with a Description mentioning an action (e.g., "Open Action") and a trigger like "Go To Destination," along with wording about not causing a "change of context." The item is unreviewed/needs a status, and its technical phrasing makes it look like a serious problem.


Screenshot of the status dialog box.  The Description indicates that there's a Go To Destination action attached to the Open Action event of the document.


Causes

PDFs support "actions" in several places. Bookmarks use actions so that clicking one navigates to a page. Links and buttons can carry actions too. A document can also have an Open Action — something that fires the moment the file is opened, such as jumping to a specific page or setting a particular zoom/view level. JavaScript embedded in a document can trigger actions as well.

This checkpoint exists to confirm that none of these actions create an unexpected "change of context" for the person reading the document — for example, automatically jumping to a random page, silently reordering how content is presented, or otherwise doing something disorienting the moment the file is opened. That would be a genuine accessibility barrier. However, the checkpoint fires any time an Open Action (or similar action) is present at all, regardless of what it actually does — so most of the time it's just flagging something benign, like a default page/zoom setting, not an actual problem.


Affected Users

Screen reader users and users with cognitive or attention-related disabilities are the primary group at risk if an action did cause a real, unexpected change of context — an unannounced jump or reorder can be disorienting or cause someone to lose their place. Low vision users could also be affected if a magnification change happened unexpectedly. In the typical case described here, no one is actually affected, since nothing unexpected is occurring. 


Accessibility Guidelines


Resolution Steps

  1. Open (or re-open) the document and pay attention to what happens the moment it loads.
  2. Confirm nothing unexpected occurs — e.g., the document does not jump to an unrelated page (such as page 65), does not reorder pages, and does not change the meaning or presentation of the content.
  3. If the only thing that happens is something ordinary, like the page displaying at "Fit Page" or a set zoom/magnification level, that's expected and not a problem.
  4. If the document contains JavaScript and a similar checkpoint appears for it, apply the same test: does running it produce anything unexpected or disorienting?
  5. If nothing "weird" happens in either case, no remediation is needed.


Verification

Change the checkpoint's Status to Passed, since the Open Action (or JavaScript action) is not initiating an unexpected change of context. Re-run verification to confirm the item now shows as Passed and no other related checkpoint is affected. 



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article