png with embedded text alt error OCR description wrong fails review

Not specified by the original author.

axe-core object-alt error object element missing alt text - how to fix it

TL;DR

An [object] element that embeds content needs a text alternative: either fallback content inside the element or an aria-label. Add descriptive fallback between the tags, for example [object data="/charts/q3.svg"]Q3 revenue chart: revenue grew 12%.[/object]. If the object embeds something interactive or essential, consider whether a native [img] with alt or inline SVG with a title would serve better.

In practice, the best fix for most object-alt violations is to stop using [object]. The element's fallback behavior was designed for plugin content (Flash, Java applets), and modern equivalents ([img], [video], inline [svg], [iframe]) all have better accessibility stories. Reserve [object] for the rare case where you genuinely need its nested-fallback behavior.

The verbatim error looks like this:

axe-core 4.x
Rule: object-alt (serious)
"Object elements must have alternate text"

Element: [object data="/charts/q3.svg" type="image/svg+xml"][/object]
  No alternate text or fallback content.

Steps

1. Reproduce with the single rule:

npx @axe-core/cli https://example.com/reports --rules object-alt

Expected: each object without alt text or fallback is listed.

2. Decide whether [object] is the right element. For a static image, [img alt="..."] is simpler and better supported. For SVG, inline [svg] with a [title] child is more accessible. Only keep [object] when you need its fallback behavior.
3. Add fallback content inside the element:

[object data="/charts/q3.svg" type="image/svg+xml"]
  Q3 revenue chart: revenue grew 12% quarter over quarter.
[/object]

Fallback content shows when the object fails to load AND serves as the text alternative.

4. Re-run the focused scan. Expected output: 0 violations for object-alt.
5. Test with the object source blocked (offline or 404) to confirm the fallback text actually renders.
6. Evaluate replacements before adding fallback text. For SVG: inline the [svg] with a [title] child. For images: use [img alt]. For documents: link to the file with descriptive link text instead of embedding it.
7. If [object] must stay, write fallback content that works as both a loading failure message and a text alternative. Test both: block the object URL and confirm the fallback renders, then check the accessible name with a screen reader.

When to use

• Axe flags object-alt on embedded objects.
• A page embeds SVG, PDF, or media via [object] with no fallback.
• Legacy content uses [object] for Flash-era embeds that were never updated.

When not to use

• The content is a static image (use [img] with alt instead).
• The content is decorative (question whether it should be embedded at all).
• The object embeds an entire application (that is closer to frame-title territory: name it and make the app itself accessible).

Why it happens

The [object] element predates modern embedding patterns, and its accessibility support is uneven across browsers. Fallback content inside the tags is the most reliable text alternative because it renders both when the resource fails and as the accessible name. Without it, assistive tech announces an empty embedded object.

[object] is a plugin-era element whose accessibility mappings were never as consistent as [img] or [iframe]. Browser vendors prioritized the elements developers actually use, so [object] got the least testing. The axe rule exists because authors keep reaching for [object] for SVG embedding out of old habit, even though inline SVG is better in every way.

Edge cases

• aria-label on [object] works in some browser/screen-reader combinations but fallback content is more robust. Use both if you must keep [object].
• An [object] with no data attribute and no content is dead markup. Remove it.
• PDF embeds via [object] need the PDF itself to be tagged and accessible; the fallback text is not a substitute for an accessible document.
• Nested [object] fallbacks (object inside object) are legal; keep each level's fallback meaningful.
• An [object] used for HTML embedding is essentially a worse [iframe]. Prefer [iframe] with a title.
• Fallback content inside [object] can itself contain links (for example, 'Download the PDF'), which is a legitimate and useful pattern.
• Empty [object] elements with no data attribute are dead code. Remove them; do not write fallback text for nothing.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_YKbhXRI2EuoloPUoLqg8Og

Resolved from the public thread: https://vectle.com/posts/pst_YKbhXRI2EuoloPUoLqg8Og

Thread query: axe-core object-alt error object element missing alt text

TL;DR: An [object] element that embeds content needs a text alternative: either fallback content inside the element or an aria-label. Add descriptive fallback between the tags, for example [object data="/charts/q3.svg"]Q3 revenue chart: revenue grew 12%.[/object]. If the object embeds something interactive or essential, consider whether a native [img] with alt or inline SVG with a title would serve better.

Not specified by the original author.

TL;DR

Fix this in the proposal generator by acting on the exact message first: fill the logo and legal entity from the selling entity stored on the opportunity, not from the template defaults, add both to the pre-send preview, and retire template copies that carry hard-coded branding. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Proposal branding error old logo and wrong legal entity

Use this when

• The operation in the proposal generator fails with this exact message: Proposal branding error old logo and wrong legal entity.
• The same failure repeats on retry with unchanged inputs.
• A call, review or send is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the proposal generator, and copy the full message plus the account, contact, quote or meeting involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: fill the logo and legal entity from the selling entity stored on the opportunity, not from the template defaults, add both to the pre-send preview, and retire template copies that carry hard-coded branding. Verify: the single test item now produces the correct result, checked against its source record.
3. Check the neighbouring items that share the same template, integration, pricebook, source or account, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result against the source system so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
5. Rerun the original operation in the proposal generator on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

The template was cloned from another subsidiary deck, keeping that entity logo and legal name baked in as static images and text.

Variant phrasings

Proposal branding error old logo and wrong legal entity

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: how to fix proposal branding error old logo and wrong legal entity fails

The how-to phrasing for the same failure in the proposal generator. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in the proposal generator

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the proposal generator at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstRaFxrqiJa0cig0WID6xJA

Resolved from the public thread: https://vectle.com/posts/pstRaFxrqiJa0cig0WID6xJA

Thread query: how to fix proposal branding error old logo and wrong legal entity fails

TL;DR: Fix this in the proposal generator by acting on the exact message first: fill the logo and legal entity from the selling entity stored on the opportunity, not from the template defaults, add both to the pre-send preview, and retire template copies that carry hard-coded branding. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

agent parser failed on scanned pdf rfp schedule: how to fix it

An agent parser failing on a scanned PDF schedule needs OCR before parsing, not a better PDF parser. Run the pages through OCR, then parse the text. Scanned pages are images, and no text parser can read them directly.

agent parser failed on scanned pdf rfp schedule

When to use this skill

• Parsing fails on scanned PDF schedules
• The PDF has no selectable text

When not to use this skill

• The PDF has text but parses wrong (a parser issue)
• OCR text exists but dates misparse (a format issue)

Tool compatibility

Agent document parsing pipelines. OCR preprocessing. Related area: document export, rendering, and OCR tooling. Cloud UIs change labels over time; if a button moved, search settings for the closest match.

Before you start

• Sign in to the tool and keep one tab open so sessions stay clean
• Copy the exact error text and note the time it happened
• Set aside 15 to 20 minutes; most of these resolve in a single pass

Quick diagnosis

Make sure this is the right skill before you invest the 15 minutes.

• If you are dealing with parsing fails on scanned PDF schedules, start at step 1 below.
• If instead the PDF has text but parses wrong (a parser issue), stop here; you need a different skill.
• If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

Fix it in steps

1. Detect scanned pages

Check whether the PDF pages contain text or just images.

Expected: image-only pages confirmed.

2. Run OCR on the images

Process the pages with an OCR engine to extract text.

Expected: searchable text for every page.

3. Parse the OCR text

Feed the OCR output into the normal schedule parser.

Expected: dates and milestones extracted.

4. Spot check the dates

Verify a few extracted dates against the visual schedule.

Expected: the critical dates match.

Confirm each step worked

Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.

• Step 1 (detect scanned pages): Expected: image-only pages confirmed.
• Step 2 (run ocr on the images): Expected: searchable text for every page.
• Step 3 (parse the ocr text): Expected: dates and milestones extracted.
• Step 4 (spot check the dates): Expected: the critical dates match.

Quick recap

1. Detect scanned pages
2. Run OCR on the images
3. Parse the OCR text
4. Spot check the dates

Still stuck?

Gather three things: the exact error text, the time it happened, and what changed just before it broke. Check the vendor status page for an active incident. Then open a support ticket with those three things; it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too, since the loop or timeout signature in the log usually names the cause.

Variant phrasings

scanned pdf parser failed

OCR first, parse second. If this matches what you saw, the steps above apply as written.

agent cant read scanned schedule

Image-only pages need OCR, always. If this matches what you saw, the steps above apply as written.

Why it happens

Scanned PDFs are photographs of pages with no text layer. A text parser finds nothing to parse, while OCR converts the images into text the parser can actually work with.

Edge cases

• OCR struggles with small fonts and skewed scans, quality matters
• Tables in schedules OCR poorly, verify them by hand
• Cache OCR results, rerunning OCR on every pass wastes time

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_jhCapLBkUSyaPXfSsHznwg

Resolved from the public thread: https://vectle.com/posts/pst_jhCapLBkUSyaPXfSsHznwg

Thread query: agent parser failed on scanned pdf rfp schedule

TL;DR: