How to use the Webpage Broken Image Checker.
A broken-image check concerns loading, not whether the picture is appropriate. Record the failing source and distinguish a blocked request from a missing file.
Make the workflow fit your task.
Inspect the selected page after its expected loading state, recording image source, alternative text and available load information. Separate failed loads from lazy images that have not been requested. Recheck relevant images after scrolling or expanding their section.
- What you provide
- Current page image elements.
- What you get
- Images failing to load with source URLs and alt text.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Inspected image: src /images/banner.png, alt Summer workshop, complete=true, naturalWidth=0. No network status supplied.
Completed example
Image: /images/banner.png Alternative text: Summer workshop Observed state: loading completed with naturalWidth 0. Finding: failed image load under the supplied state. Unresolved cause: missing file, blocking or another request failure; inspect network evidence before choosing a fix.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Does naturalWidth equal to zero always mean the file is missing?
It can also occur before loading or after a blocked or failed request. Combine it with completion state and available request evidence.
Why does an image work when opened directly but fail on the page?
Referrer restrictions, authentication, policy or responsive source selection may differ. Inspect the failing request and selected source before changing the URL.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑