Finalsite + AudioEye: Use the AudioEye Accessibility Page Scanner on your Finalsite CMS

Misty Flowers

May 20, 2026 21:55

This article covers how to activate the AudioEye accessibility page scanner within your Finalsite CMS, including how to locate flagged elements on a page and what the scanner interface shows.

💡Quick answers

How do I open the page scanner? Add ?oss=1 to the end of any page URL from the AudioEye report (or &oss=1 if the URL already contains a ?), then press Enter.
Does anything need to be installed? No. The scanner activates through the URL parameter alone. No browser extension or software is required.
The scanner loaded but nothing is highlighted. What now? Check that the correct parameter was used. Use ?oss=1 for a clean URL and &oss=1 only when the URL already contains a ?.
Does the scanner affect site visitors? No. The scanner is a view-only tool and does not modify the site or affect visitor experience.

What the page scanner is

When AudioEye flags an accessibility issue, the report identifies the page URL and the type of element involved. The AudioEye accessibility page scanner takes that a step further by loading directly on the page and highlighting the specific element that was flagged, making it straightforward for a web team to find and address.

⚠️ Important Note

No software or browser extension is needed. The scanner is activated by a single URL parameter appended to the address of the page being inspected. Learn more in the next steps!

Activate the page scanner

Step 1: Find the flagged page URL in the AudioEye report. Each flag in the dashboard includes the full URL of the page where the issue was detected. Copy that URL.
Step 2: Paste the URL into the browser address bar, then add the scanner parameter to the end:
- If the URL has no existing parameters (no ? in it), add: ?oss=1
- If the URL already has parameters (a ? already appears in it), add: &oss=1
Step 3: Press Enter. The page reloads with the scanner active and flagged elements highlighted.

Review these URL examples

Standard page with no existing parameters: https://www.yoursite.com/about?oss=1
Page with an existing parameter: https://www.yoursite.com/news?category=events&oss=1

Pro tip

To check whether a URL already has a ?, look at the full address in the browser bar. Everything after the first ? is a parameter. If a ? is already present, use &oss=1. If not, use ?oss=1.

See what the scanner shows

Once the scanner loads, it overlays the page with accessibility information. Here is what the scanner looks like in use:

What you see	What it does
Highlighted elements	The specific flagged element is marked directly on the page so the exact location is immediately visible.
Issue details	A summary of what was detected and the WCAG criterion that applies.
Navigation controls	Controls to move between multiple flags on the same page when more than one issue is present.

Nothing highlighted after the scanner loads? Double-check the parameter used. Use ?oss=1 for a clean URL and &oss=1 only when the URL already contains a ?. Also confirm the URL matches exactly what appears in the AudioEye report.

Share the scanner with the team

Send the scanner URL directly. The full URL with ?oss=1 appended can be shared with a developer or designer so they can load the scanner and see the highlighted element in context.
Open multiple pages at once. Each scanner URL is independent, so several can be opened in separate tabs to compare issues across pages.
Work from the report URL. Always copy the exact URL from the AudioEye report rather than navigating to the page manually. The report URL points to the specific page AudioEye scanned.
Use it as many times as needed. The scanner does not modify the site or affect visitors, so it is safe to load repeatedly.

Next steps: Fix the flagged issue

Once the flagged element is visible on screen, follow the step-by-step fix guide for that issue type. Select the relevant guide from the AudioEye report landing page.

If a flag is unclear, persists after a fix, or involves a template element that cannot be edited directly, email accessibility@finalsite.com with the page URL and a description of what has been tried. Include the ?oss=1 scanner output to help trace the issue faster.
If a flag appears in the AudioEye report but the scanner does not highlight anything on the page, see AudioEye's article on understanding discrepancies between platform reporting and the accessibility scanner for common reasons this occurs.