You have an AudioEye report. Find your flag below and follow the step-by-step guide to fix it.
- Find your flag. Use Ctrl+F (or Cmd+F on Mac) to search this page for the exact wording from your AudioEye report, or scan the guide list below.
-
Locate it on the page. Open the flagged page and add
/?oss=1to the end of the URL (or&oss=1if the URL already contains a?). This highlights the flagged element directly on screen. - Follow the fix guide. Open the matching guide below and work through the steps.
💡Quick answers
-
How do I find the flagged element on the page? Add
/?oss=1to the end of the page URL and press Enter. The AudioEye Accessibility Page Scanner loads and highlights the specific element. Use&oss=1if the URL already has a?in it. -
I fixed the issue but it is still showing in my report. Why? The AudioEye report runs on a rolling 7-day window. Use
/?oss=1on the live page to confirm your fix worked immediately. The main report takes about a week to update. - Does AudioEye check my PDFs? No. AudioEye's monitoring and reporting covers your web pages only. PDFs and other linked documents are never tested and will not appear in your report, but they are still in scope for ADA Title II. See Making accessible PDFs.
-
My flag does not match anything in the list below. What do I do? Email accessibility@finalsite.com with the page URL, the exact flag message, and the
/?oss=1scanner output. We can help identify what it is and how to address it.
In this article
- Find your exact flag message
- Fixes a content editor can make in Composer
- Fixes that may require your web manager
- A note on PDFs and linked documents
Find your exact flag message
Copy the flag name from your AudioEye report and use Ctrl+F to search this page, or match it to a guide using the list below.
- "Image Missing Alternative Text" or "Alt text is a filename" → Alt text
- "Video element missing captions" or "Prerecorded video missing text alternative" → Captions and transcripts
- "Heading levels are skipped" or "Multiple H1 elements detected" or "Page is missing an H1" → Heading structure
- "Deprecated presentational tag detected" → Deprecated HTML tags
- "Form input missing label" or "Link text is not descriptive" → Form labels and link text
- "Element has insufficient color contrast" or "Non-text contrast-ratio on visual boundaries is too low" → Color contrast
Fixes a content editor can make in Composer
These issues are in your page content and can be resolved directly in Finalsite Composer without contacting your web manager.
AudioEye may flag this as: "Image Missing Alternative Text," "Alt text is a filename," or "Image description is not meaningful."
AudioEye flags images that are missing a text description, have a file name as their alt text, or have a description that does not convey what the image shows. Covers inline images, linked images, and images in Resources.
WCAG 1.1.1 Non-text Content · Level A
AudioEye may flag this as: "Video element missing captions," "Video is missing captions," or "Prerecorded video missing text alternative."
AudioEye flags videos that have no captions or have captions turned off by default. Covers hero area videos, Video Elements, YouTube Elements, Vimeo Elements, and Embed Elements. The fix is different for each video type.
WCAG 1.2.2 Captions (Prerecorded) · Level A
AudioEye may flag this as: "Heading levels are skipped," "Multiple H1 elements detected," or "Page is missing an H1 element."
AudioEye flags pages with skipped heading levels, multiple H1 headings, a missing H1, or text that is visually formatted to look like a heading but is not tagged as one.
WCAG 1.3.1 Info and Relationships · Level A
AudioEye may flag this as: "Deprecated presentational tag detected" or "Deprecated HTML element found."
AudioEye flags HTML tags removed from the current web standard, such as <font>, <center>, <b> used for visual styling, and <strike>. These most commonly arrive through content pasted from Microsoft Word or Outlook.
WCAG 4.1.1 Parsing · Level A
AudioEye may flag this as: "Form input missing label," "Link text is not descriptive," or "Link purpose is unclear."
AudioEye flags form fields that are missing a visible label, and links that use generic text like "click here" or "read more" that give no context about where the link leads. Navigation link text changes may require your web manager.
WCAG 1.3.1 Info and Relationships · Level A | WCAG 2.4.4 Link Purpose · Level A
Fixes that may require your web manager
These issues are typically controlled at the theme or site-wide level. A content editor may be able to address some cases, but coordinate with your web manager before making changes that affect the whole site.
AudioEye may flag this as: "Element has insufficient color contrast" or "Non-text contrast-ratio on visual boundaries is too low."
AudioEye flags text, buttons, icons, or form fields that do not have enough contrast to be readable by users with low vision or color differences. Text color inside a Content element can often be changed by an editor. Button colors, form field borders, and site-wide link colors are usually controlled through your site theme and require web manager access.
WCAG 1.4.3 Contrast (Minimum) · Level AA | WCAG 1.4.11 Non-text Contrast · Level AA
A note on PDFs and linked documents
AudioEye does not test PDFs or other linked documents. Their monitoring and reporting covers your web pages only, so no document will ever appear as a flag in your AudioEye report, no matter what condition it is in.
Your PDFs are still in scope for ADA Title II. Because they are not covered by your report, they need to be reviewed separately. See "Making accessible PDFs" for how to audit your document library, decide which files to fix, replace, or remove, and remediate the ones that must stay PDFs.
Still stuck?
If a flag is unclear, persists after your fix, or involves a template element you cannot edit directly, email accessibility@finalsite.com with the page URL and a description of what you have tried. Include the /?oss=1 scanner output to help us trace the issue faster.
Related resources
- 2026 ADA WCAG 2.1 Accessibility at Finalsite: compliance overview, deadlines, and Finalsite's platform commitment
- Accessibility management with AudioEye: how AudioEye works, what it monitors, and how to read your report
- Making accessible PDFs: auditing your document library and remediating PDFs, which AudioEye does not cover
- AudioEye FAQs: common questions from Finalsite clients about AudioEye coverage, the scanner, and report timing
- AudioEye Help Center: AudioEye's own documentation for their dashboard and tools
Comments
Please Sign in to leave a comment if you don't see the comment box below.