A browser-based exam cannot guarantee that its questions will never be captured. A website can change what it displays and respond to some keyboard events, but it does not control every operating-system screenshot tool, another application, or a camera pointed at the screen. Treat capture controls as deterrents and test them on the devices your candidates use.
This guide describes the browser exam page in ZYNQO. It does not claim the same behaviour for a separately installed, managed-device app. The checks below are a suggested rehearsal, not published benchmark results.
What the Current Exam Page Does
ZYNQO includes page blur for certain key and focus events, restrictions on copying and selecting exam text, print styles, and a watermark containing a student identifier. The implementation also overrides some screen-sharing and canvas-export methods inside the page. These measures have different scopes. Combining them does not grant a website control over the whole device.
Earlier versions of this guide described automatic clipboard wiping and reliable blocking of external recording tools. That wording overstated the controls. Clipboard wiping is disabled in the current exam page, and page-level method overrides cannot prevent an unrelated application from recording the display.
Keyboard Blur Is a Visible Deterrent
The exam page can blur its content when it receives certain keyboard events. This may obscure a capture if the page receives the event and redraws before the capture occurs. A screenshot started by a hardware button, another application, or an operating-system shortcut may not give the page that opportunity. A successful blur in one rehearsal is not proof that every capture route is blocked.
Check ordinary keyboard tasks as well as screenshot shortcuts. A student using browser zoom or assistive technology may press the same modifier keys. If a control interrupts an approved accommodation, resolve that conflict before the graded exam; do not classify the interruption as misconduct.
Copy Restrictions Do Not Erase Screenshots
Blocking copy or cut events within the exam page discourages ordinary text copying. It does not delete an image already saved to disk, and it does not control clipboard operations in other applications. ZYNQO's current browser exam does not continuously clear the system clipboard.
Even when a website uses the Clipboard API, access depends on browser permissions and security conditions. The Clipboard API documentation explains those restrictions. Do not make an exam policy depend on the assumption that a website can always overwrite a candidate's clipboard.
Screen-Sharing and Canvas Controls Have a Limited Scope
The browser's getDisplayMedia method requests permission to capture a user-selected display surface. Replacing that method inside one page can affect scripts calling that replacement. It does not disable screen sharing initiated in another page, a video-conferencing application, or the operating system.
Similarly, changing a canvas export method affects calls to that method. An ordinary exam question can still consist of text and images outside a canvas. Page automation and browser extensions also have capabilities that a page's canvas wrapper does not govern. These overrides should never be described as general screenshot protection.
Print Styles and Watermarks
Print styles can hide exam content in the browser's normal print preview. That is useful against accidental or casual printing, but it is not a secure document boundary: the content has already been delivered to the device.
A visible watermark can associate a captured view with a session identifier. It does not stop capture, and it may be cropped, obscured, or altered. A watermarked image alone does not prove which person distributed it. An institution should consider the surrounding evidence and give the candidate a chance to respond.
The exam watermark may also contain text asking AI tools not to answer exam questions. Such text is not an access-control mechanism and cannot compel another service to refuse a request. It should not be relied on when deciding whether an assessment is suitable for remote delivery.
Run a Capture-Protection Rehearsal
Create a disposable practice exam with invented questions and a test registration. Record the browser, operating system, device type, session settings, and date. Use the same setup that candidates will use, including approved assistive technology.
- Ordinary copying: attempt to select and copy the dummy question. Record whether it is blocked and whether a written-answer field still supports the required workflow.
- Keyboard and device capture: try the device's normal capture route with permission. Record whether the result is readable, blurred, or watermarked; do not assume one result applies to other devices.
- Print preview: inspect the practice page's preview. Check whether it hides the question and whether the candidate can return to the exam without losing work.
- Focus changes: test an ordinary notification and an approved accessibility shortcut. Note any warning, pause, or recovery step.
- Readability: check small displays, zoom, diagrams, and long answers. A watermark that makes the paper hard to read creates an assessment problem.
Keep observations separate from conclusions. For example, "the laptop shortcut produced a blurred image in this test" is an observation; "screenshots are impossible" is an unsupported conclusion. The exam-readiness worksheet provides a place to record the test and the person responsible for unresolved issues.
Reduce the Consequences of a Leak
Decide in advance how to retire exposed questions, investigate reports, and communicate with affected candidates. Use different question sets where the assessment permits it, and ask for reasoning tied to material taught in the course. These decisions reduce reliance on any single browser control.
If the exam requires stronger device control, evaluate a managed-device or supervised setting and demonstrate its behaviour before committing. The relevant question is whether the chosen environment meets the assessment's needs, including accessibility and incident recovery.
Corrections: this article was revised on 27 September 2026 to clarify the current implementation and remove claims of guaranteed capture blocking. Report a discrepancy through ZYNQO support, including the browser, device, and practice-session steps.