ScrollAccess Documentation

Using Webflow? Start with ScrollAccess for Webflow: Setup and User Guide for installation, Designer connection, supported fixes, publishing, verification, and removal.

ScrollAccess is a website accessibility platform for website owners, developers, designers, teams, and agencies. It combines automated accessibility scanning, WCAG-related issue insights, AI-powered guidance, a customizable visitor accessibility toolbar, reports, manual review workflows, and multi-website management.

This guide reflects the current ScrollAccess functionality, including Webflow and generic website connections, per-website toolbar preferences, website translation, managed AI assistance, reporting, agencies, and client access.

Note: ScrollAccess helps identify and manage accessibility work. Automated testing and AI guidance do not guarantee legal compliance and do not replace appropriate manual testing.

ScrollAccess for Webflow: Setup and User Guide

This guide covers the Webflow Designer app, its connection to your ScrollAccess account, and the optional visitor toolbar. Start at the ScrollAccess dashboard. A ScrollAccess account and a Webflow account with access to the website are required. Features and usage limits depend on your ScrollAccess plan.

Workflow: install and authorize → connect the Designer app → scan Designer elements → review → apply a supported change → rescan in Designer → publish separately. Use Undo when needed.

1. Install and authorize Webflow

  1. Open https://scrollaccess.com/dashboard/ and create an account or sign in.
  2. Open Websites and choose Connect Webflow. The connection controls are also available in Settings.
  3. Sign in to Webflow when prompted. Select the website you want to connect and review the requested permissions.
  4. Choose Authorize App. If you cancel or deny authorization, no new connection is completed; return to ScrollAccess to try again.
  5. After returning to ScrollAccess, confirm your selected site is listed and the connection status is connected. Use Sync sites if the list needs refreshing.

Webflow authorization connects site access to your ScrollAccess account. It is separate from the Designer key used to sign in to the extension. Never copy an OAuth callback URL containing temporary authorization parameters as an installation link.

2. Connect the Designer app

  1. In the ScrollAccess dashboard, open Settings → Webflow Designer App and select Generate designer key.
  2. Copy the full key when it is shown. Keep it private. This is a ScrollAccess key, not an AI provider key or a Webflow OAuth token.
  3. Open the authorized site in Webflow Designer, open the Apps panel, and launch ScrollAccess.
  4. Paste the key into Designer API key and select Connect. Confirm the displayed website and connection status before scanning.

The Designer key is kept only in memory while the app instance is open. Reopening or reloading the app requires connecting again. Reuse a valid key you securely retained, or generate a replacement in the dashboard and revoke obsolete keys. Reconnecting the Designer does not require repeating Webflow OAuth unless authorization has been revoked or otherwise needs renewal.

3. Scan the current Designer page

Before your first scan in a connected session, review the disclosure about site identifiers, page URL and limited finding content sent to ScrollAccess, and the configured scan-retention period. You may cancel without sending scan content. Scan content is not sent to an AI provider merely by scanning. The Privacy Policy is linked inside the extension.

  1. Open the authorized page in Designer outside component editing. The app reads supported page elements through the official Designer API; publishing is not required to read these elements.
  2. In ScrollAccess, choose Scan current page and wait for the results.
  3. Review the scan summary. Use the category and severity filters to focus on findings.
  4. Open a finding to review its description, affected element, API-derived element snapshot, WCAG reference, suggested improvement, and related standards guidance.
  5. Where offered, select Show in Designer to locate the matching editable element.

Designer scans inspect a snapshot of supported API-provided elements, including current Designer edits. Checks cover image alt text, heading structure and link/button names. Forms and authentication controls, CMS collections and shared component internals are excluded. Document language and title need manual review. Visual contrast, focus behavior, motion, dynamic content, keyboard interactions, and assistive-technology behavior need rendered-page or manual testing. A scan score is an internal indicator, not accessibility certification.

4. Review and apply supported changes

Supported changes include image alternative text, heading levels, and accessible labels where the finding can be reliably matched to an editable Webflow element. The available controls depend on the finding and element.

  1. Expand Click to fix — review change for a supported finding.
  2. Read the guidance and enter the intended alt text, heading level, or accessible label. Check its meaning in the context of the page.
  3. Select Apply fix in Designer when the control is available. This changes the matching element in Designer; it does not publish your site.
  4. Review the result in Webflow and the fix-verification area before proceeding.

If a unique element cannot be matched, the app displays an explanation or guided manual steps. Edit the element manually in Webflow and run a fresh Designer scan. API findings target the exact Designer element ID; historical findings may require a fresh scan. Saved scans alone do not authorize applying changes: use a fresh scan to establish the current page and element context.

5. Undo a supported change

Use Undo in the fix-verification area while the applied change is available. Up to 50 minimal fix records are held only in memory during the current app session, for at most one hour. They are cleared on Designer disconnect or reload; old browser-stored fix records are removed. Undo attempts to restore the value recorded before the change. If the element or value has since changed and restoration cannot be verified, review the message and correct the element manually in Webflow rather than overwriting unrelated work.

Undo changes the Designer state. If you already published the change, publish again after Undo to update the live page. Keep your own review record and use Webflow's normal editing and backup tools for work beyond the app's available Undo controls.

6. Rescan and publish

  1. Return to ScrollAccess and choose Scan current page again to read the updated Designer elements; publishing is not required for this rescan.
  2. Review the new findings, fix-verification status, and the changed element in Designer.
  3. When satisfied, publish using Webflow's normal publishing controls and inspect the intended change on the live page. Perform manual interaction and assistive-technology testing as appropriate.

Applying a Designer fix does not immediately change a saved scan score. A new Designer scan is needed to update saved results; publishing is a separate step that makes edits visible to visitors. Disappearing findings do not prove complete accessibility or legal compliance.

7. Use AI assistance

Before your first AI request in a connected session, review the disclosure about selected issue context or text sent to ScrollAccess and its configured third-party AI provider, ScrollAccess retention and provider retention differences. Only fields needed for the selected tool are sent. Cancel if you do not want to share this information. Avoid secrets or unnecessary personal information.

AI assistance is included in eligible ScrollAccess plans, subject to the plan's feature and usage limits. Webflow customers do not need their own AI provider account or API key, and do not need access to WordPress administration. The provider connection is managed by ScrollAccess; customers do not receive a separate provider bill for this managed AI feature.

  1. Connect the Designer app and scan the page.
  2. Choose an available finding action such as Explain issue or HTML fix suggestion, or open AI tools and search for a tool.
  3. Supply the requested context. For alt text, describe what the image shows and its purpose; the generator uses your description rather than inspecting image pixels.
  4. Generate the suggestion and review its accuracy, wording, and suitability before using it.

Generated HTML and CSS are suggestions and are not automatically inserted into your site. Where a supported Designer fix is available, review and explicitly apply it, then rescan in Designer and publish separately. If AI is unavailable or a limit is reached, check your plan and usage in Billing or contact ScrollAccess support. Do not enter passwords, private keys, or other sensitive information into AI prompts.

Website translation is a separate optional toolbar feature. Its provider-key requirements and third-party usage charges are explained in Translation API Key; those requirements do not apply to managed AI suggestions.

Security, visitor authorization and restrictive policies

Install the current backend and Designer build, and reapply managed published scripts after a runtime update. Publishing is a separate Webflow action. Versioned runtime files are not modified in place.

Sign-in and password reset: requesting a reset link does not create a session. Reset links are verified before the password can change; after a successful reset, sign in with the new password. Dashboard and authentication pages must be excluded from hosting, CDN and LiteSpeed caches. A cached dashboard shell is not evidence of an authenticated account; protected API requests require a valid session or an authorized Designer key.

Webflow versus other platforms: Webflow toolbar/cookie installation is managed from Websites through the Custom Code API. Copy non-Webflow embed code is a separate setup method for other platforms, not a Webflow fallback. Remove older manual snippets before managed installation to avoid duplicates; uninstall cannot remove manually pasted code.

Translation authorization: default-language and browser-language settings do not authorize sending page content. The first visitor language change asks permission before translation; only an authorized saved preference can be reused. For managed Webflow installations, mark public static containers with the custom attribute data-scrollaccess-translate-public="true". Leave account, form, checkout, personalized and sensitive content unmarked. The runtime also excludes private regions and common sensitive text patterns.

Cookie discovery and consent records: optional discovery starts only after Analytics consent, and reports names/hosts rather than cookie values or full URLs. Discovery expires after 30 days without updates. Consent audit references are created only after a visitor chooses an option; audit history uses the configured 1–365 day retention. Update your privacy notice before enabling either feature. Nonmodal banners do not take initial focus. Where a reload is needed after revocation or changes in another tab, a notice offers a Reload button rather than silently discarding work.

Optional scripts: global DOM insertion interception has been retired. Keep optional markup inert until consent and use reviewed first-party vendor files with the matching SHA integrity value. Configured arbitrary external URLs are rejected. Remove other apps' parser-loaded tags and duplicate integrations before enabling the controlled loader.

CSP and dependencies: the runtimes support nonce-authorized style elements and approved first-party assets. A restrictive policy must authorize the document's nonce or exact style hashes; do not add broad unsafe-inline exceptions. Recompute hashes when runtime/configuration bytes change. Dyslexia CSS and its licensed font are self-hosted. Google's optional mutable gtag loader cannot use stable SRI; enable it only with the required visitor consent, disclosed vendor dependency and specific CSP destinations. Ask your site administrator to test the actual published page with its policy enforced. Allow only the first-party runtime, API, stylesheet and font origin https://scrollaccess.com and any explicitly enabled vendor destinations. A nonce attribute alone does not authorize a style unless the response policy permits the same nonce.

The cookie banner is separate from the visitor accessibility toolbar. On Webflow, install it through the supported Custom Code API, without pasting a new executable embed manually.

  1. In dashboard Websites, choose the connected site's Cookie consent action. Enable the banner, configure its appearance and categories, and save settings.
  2. For an older manual installation, remove only the old ScrollAccess cookie-consent script and its associated Google default snippets from site custom code and page embeds, then publish. Keep the toolbar and unrelated code.
  3. Confirm the legacy cookie snippets are removed or none exist. Choose Apply cookie banner through Webflow. The app registers an immutable HTTPS script with an integrity hash and applies it to the site header. Publish in Webflow, then test the live site.
  4. After changing Google Consent Mode, save, apply again and publish so the header defaults match your settings.
  5. To remove only the cookie banner, choose Remove managed cookie banner, then publish. Toolbar code is preserved.

Dashboard site removal and Disconnect all clean up managed cookie-banner and toolbar code before dropping authorization. Designer Disconnect only ends the Designer session. Webflow uninstall removes app-owned code; publish affected sites to update live pages. Manually pasted code still needs manual removal.

Optional services must not already run through other tags, integrations or tag managers. Remove duplicate tags and use configured consent-aware services. Google denied defaults must run before measurement tags. The banner cannot block requests made before it loads or guarantee legal compliance.

Banner configuration is fetched from ScrollAccess. Optional discovery starts only after Analytics consent and reports observed cookie names and script hosts, without cookie values or full URLs. Discovery expires after 30 days without updates. Consent-history references are created only after a visitor chooses an option. Optional consent history stores choices, timestamps, configuration version and a hashed consent reference for the configured retention period (1–365 days); this module does not record IP addresses or user agents. Update the site's privacy notice before enabling these options. Non-Webflow websites retain the separate embed installation workflow.

8. Add the optional visitor toolbar

The toolbar adds JavaScript and styling to your published website through Webflow's Custom Code API. Its code runs in visitors' browsers to provide accessibility preference controls and optional translation. It is separate from the Designer scanner and does not repair the site's underlying markup.

  1. Connect or reconnect Webflow and approve the Custom Code read/write permissions used to register, apply, inspect and remove toolbar code.
  2. If you used an earlier manual installation, remove the ScrollAccess configuration, scripts and stylesheet references you pasted into site custom code or page embeds. Preserve unrelated scripts and publish this cleanup before continuing.
  3. In ScrollAccess dashboard Websites, choose the connected Webflow site's Install toolbar action.
  4. Confirm older manual snippets have been removed, or that none exist. Select Apply toolbar through Webflow. The app registers an immutable, versioned HTTPS script with an integrity hash and applies it to the site's footer through the Custom Code API. The script includes the toolbar, styling and optional translation functionality; it does not load a changing JavaScript loader.
  5. Publish in Webflow when ready, then test the toolbar on desktop and mobile. Applying or removing the toolbar does not automatically publish other staged site edits.

Configure toolbar preferences in ScrollAccess. Configuration, license eligibility and optional translation use ScrollAccess HTTPS services. A Webflow plan and site role supporting custom code are required. Toolbar availability depends on your active ScrollAccess plan.

9. Remove or disconnect ScrollAccess

  1. Remove the managed toolbar: dashboard Websites → the Webflow site → Install toolbar → Remove managed toolbar. This removes the app's tracked script from staged site custom code while preserving unrelated scripts. Publish in Webflow to remove it from the live site.
  2. Dashboard disconnect or site removal: these actions remove tracked, app-managed toolbar and cookie-banner code before revoking access or deleting the connection. If cleanup fails, retry with valid Webflow authorization; the app does not silently forget a managed installation. Publish the affected site after cleanup.
  3. Disconnect inside Designer: this only ends the Designer connection and clears session data, including fix history. It does not disconnect dashboard OAuth or remove the toolbar.
  4. Uninstall in Webflow: revoke the app using the site's or Workspace's Apps & Integrations controls. Webflow removes app-owned custom code as part of its uninstall lifecycle; publish affected sites for removal to take effect on live pages. A Workspace removal can affect multiple sites.
  5. Legacy manual installations: manually remove old ScrollAccess configuration, JavaScript and stylesheet references from site custom code and page embeds, then publish. Uninstall cannot manage scripts you pasted manually. Preserve unrelated code.
  6. Revoke Designer keys: revoke unused keys in ScrollAccess dashboard Settings.

Disconnecting or uninstalling does not undo content changes you already applied or automatically erase all saved scans and reports. See the Privacy Policy for retention and deletion requests. Reverse content changes separately if needed.

10. Connection troubleshooting

  • No sites on Webflow's authorization screen: check the signed-in Webflow account and its site permissions. Before Marketplace publication, external test users may require Webflow-approved testing access.
  • Authorized site missing in ScrollAccess: confirm you authorized the intended site with the intended ScrollAccess account, then use Sync sites. Reauthorize if Webflow access was revoked.
  • Designer key rejected: paste the full current key, check that it has not been revoked, and confirm the key belongs to the account containing the authorized site.
  • Designer scan unavailable: open the intended authorized site and page in Webflow Designer, leave component editing, and confirm the ScrollAccess Designer connection. Retry the scan and review any displayed API error. Supported unpublished Designer edits can be scanned; publishing is not required. Forms, authentication controls, CMS collections, and shared component internals are outside the supported scan scope.
  • Change not verified: confirm the intended element was updated on the current Designer page, then run a fresh Designer scan. Check the verification message and review the element manually if necessary. Publishing is separate: publish approved edits and inspect the live page to confirm what visitors receive.

Contact support@scrollaccess.com with the site URL, steps, and displayed error. Do not send credentials in support messages.

Getting Started

A typical ScrollAccess setup follows these steps:

  1. Create or sign in to your ScrollAccess account.
  2. Connect a Webflow website through authorization, or add another supported website by URL.
  3. For non-Webflow websites, verify ownership with the supplied meta tag or DNS TXT record.
  4. Run an accessibility scan and review the findings.
  5. Configure the accessibility toolbar for the selected website and install the generated embed code.
  6. Use managed AI assistance when included in your plan; configure a separate translation provider only if you enable website translation.
  7. Use reports, scan comparisons, and manual review to manage ongoing accessibility work.

How ScrollAccess Works

ScrollAccess is designed around an ongoing accessibility workflow rather than a one-time check.

  • Connect & scan: for Webflow, authorize the site and scan supported current-page elements through the Designer API. For other supported platforms, verify your website and scan publicly retrievable HTML. Webflow websites are not scanned through the dashboard URL or sitemap crawler.
  • Understand findings: review issue details, severity, relevant WCAG criteria, and available AI guidance.
  • Make & verify improvements: for Webflow, review and apply supported Designer changes, rescan in Designer, and publish separately. For non-Webflow public-HTML scans, publish your website changes before rescanning.
  • Support visitors: configure and install the visitor-facing accessibility toolbar.
  • Track progress: use scan history, comparisons, reports, and manual review.

Account Setup

Create your ScrollAccess account and sign in to the dashboard. Your account stores website connections, toolbar preferences, report preferences, agency access, and usage entitlements.

In account settings you can manage your profile name, dashboard language, appearance, timezone, and scheduled report preferences where enabled.

Connect Websites

ScrollAccess supports Webflow authorization and a generic website connection flow for other platforms.

  • Webflow: use Connect Webflow to authorize ScrollAccess and import accessible Webflow sites.
  • Other platforms: choose Connect another website, enter the website name and URL, then select the platform.
  • Current platform choices include WordPress, Webflow, Shopify, HTML, Framer, Wix, React, Squarespace, Weebly, Magento, BigCommerce, Drupal, Duda, Joomla, PrestaShop, Custom system, and Other.
Note: Each hostname uses a website/plan slot, including pending websites. The exact hostname must be verified; www and other subdomains may require their own verification. The platform must support custom code for the toolbar embed.

Website Verification

For a non-Webflow website, ScrollAccess provides two ownership verification methods:

  1. Meta tag: place the generated verification meta tag in the homepage <head>, publish the site, then choose Verify meta tag.
  2. DNS TXT: create the displayed TXT record using the full record name and value, allow DNS to propagate, then choose Verify DNS record.

After verification, ScrollAccess can provide the toolbar embed snippet and scanning access when allowed by your active plan and website selection.

Note: Public HTML scanning does not execute page scripts or inspect login-protected content. Dynamic interactions and screen-reader behavior require manual review.

ScrollAccess Dashboard

The dashboard is the central workspace for websites, scans, AI assistance, reports, manual review, billing, agency features, client access, and settings. Use the website selector wherever available to make sure you are working with the intended website.

Accessibility Scanner

Webflow scans read supported elements on the current page through the Designer API, including unpublished Designer edits. Use the Webflow scanning instructions; dashboard URL, full-site crawling, and sitemap scanning are not available for Webflow websites. For non-Webflow websites, automated scans inspect publicly retrievable HTML. Scan results are stored so you can revisit findings and compare changes over time.

  • Review issue categories and counts.
  • Use severity information to prioritize review.
  • Open individual findings for affected element/context and WCAG-related information.
  • For Webflow, rescan the Designer page after editing and publish separately. For non-Webflow HTML scans, publish changes before rescanning. Review whether supported automated findings changed.
Note: A failed page can stop a scan run and partial results may not be saved. Automated scanning cannot detect every accessibility barrier.

Understanding Scan Results

Scan results organize detected accessibility findings so they can be reviewed rather than treated as an automatic compliance decision.

  • Issue description and category
  • Severity/prioritization information
  • Relevant WCAG criterion where available
  • Affected element or selector/context
  • Suggested guidance and available AI actions
  • Issue status and workflow information

Accessibility Issues & WCAG Insights

ScrollAccess maps supported automated findings to relevant WCAG information and can provide additional standards guidance. Use this information to understand why a finding matters and what should be reviewed.

Note: A WCAG reference in a scan result does not mean automated testing has fully evaluated that success criterion. Some criteria require human judgment, interaction testing, assistive technology testing, or content review.

Scan History & Comparisons

Use scan history to revisit earlier runs, review score trends and issue categories, and compare selected scans. Comparisons help show whether automated findings increased, decreased, or changed after website updates.

Use comparisons as progress evidence, not as a substitute for manual accessibility testing.

AI Accessibility Assistant

The AI Assistant helps explain accessibility findings and generate practical suggestions. It does not edit or publish changes to the customer website.

  • Explain an accessibility issue in clearer language.
  • Explain relevant WCAG criteria.
  • Suggest HTML or CSS improvements.
  • Generate accessible button, link, heading, and form-label suggestions.
  • Suggest accessible color replacements.
  • Generate contextual alt-text suggestions for images.
Note: Always review AI output before applying it. AI suggestions can be incomplete or inappropriate for the specific page context.

AI Access for ScrollAccess Customers

AI assistance is included in eligible ScrollAccess plans and is subject to plan usage limits. ScrollAccess manages the provider connection. Webflow customers do not need an AI provider account, provider API key, or WordPress administrator access, and do not receive a separate provider bill for managed AI assistance.

Connect your Designer app, choose an available AI action or tool, provide the requested context, and review the generated suggestion. For step-by-step instructions, see AI assistance in the Webflow guide. Check Billing for your plan's AI allowances or contact support if the service is unavailable.

Website translation has separate provider-key and billing requirements; see Translation API Key.

AI Tools & Alt Text

Available AI surfaces depend on the issue type and your plan. The current AI feature catalog includes alt text generation, WCAG explanation, accessible button and link suggestions, heading and form-label guidance, issue explanations, HTML/CSS fix suggestions, color replacement suggestions, and the general assistant.

Alt text: provide enough page/image context for the suggestion to be useful. Decorative images may require an empty alt attribute rather than descriptive text. Review every generated value before publishing.

Accessibility Toolbar

The ScrollAccess toolbar gives website visitors optional controls for adjusting how content is displayed or experienced. Toolbar configuration can be scoped to an individual connected website.

The toolbar complements accessibility work; it does not repair inaccessible source code or guarantee that a website conforms to WCAG or accessibility laws.

Toolbar Settings per Website

Use the toolbar settings for the selected website to create website-specific preferences instead of relying only on global defaults.

  1. Select the website you want to configure.
  2. Open Settings → Accessibility toolbar.
  3. Choose the Toolbar position: Bottom Right, Bottom Left, Top Right, or Top Left.
  4. Optionally enter a Panel disclaimer.
  5. Choose which Enabled controls should appear in the embedded toolbar.
  6. Choose the toolbar icon where the icon controls are available. Supported icon values include Classic, Blue, Dark, High Contrast, Wheelchair, and Custom; a custom icon URL can be stored for the website.
  7. If Website language translation is enabled, configure the translation provider and key as described later in this guide.
  8. Choose Save embed preferences.
  9. For non-Webflow websites, copy refreshed embed code if required. For Webflow, use the managed toolbar installation workflow. Verify the live website.

Per-website toolbar preferences can store custom status, position, disclaimer, icon/custom icon URL, and enabled controls.

Visitor Accessibility Controls

The current toolbar control catalog includes:

  • Text size (%)
  • Line height
  • Letter spacing
  • Word spacing
  • Contrast presets (light / dark / high)
  • Grayscale
  • Invert colors
  • Highlight links
  • Highlight headings
  • Reading mode
  • Focus mode
  • Reading ruler
  • Reduce motion
  • Large cursor
  • Cursor contrast
  • Dyslexia-friendly font
  • Color blindness simulation
  • Blue light filter
  • Saturation (low / high)
  • Hide images
  • Text magnifier
  • Text, title & background colors
  • Reading mask (spotlight)
  • Highlight on hover
  • Mute HTML5 media
  • Website language translation
Note: Enable only the controls you want to expose for the selected website. Some controls change presentation for the visitor but do not change the underlying website markup.

Install the Toolbar

Webflow: use the Custom Code API installation workflow. The manual embed instructions below apply to non-Webflow platforms.

After a website is connected and eligible for toolbar use, ScrollAccess generates an embed snippet.

  1. Open the selected website toolbar settings or setup panel.
  2. Configure the per-website position, controls, icon, disclaimer, and translation option first.
  3. Choose Copy non-Webflow embed code.
  4. Paste the snippet into the platform’s supported site-wide custom-code location/shared layout.
  5. Publish the website.
  6. For generic websites, use Check installation to confirm the embed is detected.
  7. Open the live website and test the toolbar on desktop and mobile.

For generic websites, ScrollAccess can also replace/rotate the embed key when needed. If the key is replaced, update the installed snippet on the website.

Note: Platform capabilities differ. Shopify checkout, plan-restricted custom-code areas, single-page applications, and dynamically rendered content can require additional testing.

Website Language Translation

Default-language settings and browser-language detection do not grant permission to send page content. The first visitor language change asks for authorization before translation. A saved preference is reused only after authorization. For managed Webflow installations, mark public static containers with data-scrollaccess-translate-public="true". Leave account, form, checkout, personalized and sensitive regions unmarked. See Security and visitor authorization.

Website language translation is an optional toolbar control. It must be enabled in the website’s toolbar control list and requires a configured translation provider API key.

ScrollAccess currently supports Google Cloud Translation, DeepL (Free / Pro), and managed LibreTranslate through libretranslate.com. Available source/target languages depend on the selected provider.

Note: Translation usage is sent to the configured provider and can count toward that provider account’s quota or billing.

Add and Test the Translation API Key

Configure the translation provider in the website toolbar settings:

  1. Open Settings → Accessibility toolbar for the website.
  2. Under Enabled controls, enable Website language translation.
  3. In Translation provider and API key, choose Google Cloud Translation, DeepL (Free / Pro), or LibreTranslate (managed).
  4. Enter the selected provider’s API key. If a key is already configured, leaving the field blank keeps the saved key.
  5. Choose Test connection. Testing sends the word “Hello” for translation and can count toward provider usage; testing does not save the key.
  6. If the test succeeds, choose Save provider and API key.
  7. Save the website embed preferences and test translation on the live toolbar.

The translation key is stored encrypted on the server and is never included in the toolbar embed code. Switching providers requires a key for the new provider. Use Remove API key to clear the saved credential.

  • If the provider rejects the key, check key validity, API permissions, and restrictions.
  • If the API is disabled, enable the translation API in the provider project/account.
  • If quota or billing errors appear, review the provider account’s usage and billing.
  • If a language pair is rejected, choose a pair supported by that provider.

Manual Accessibility Review

Manual review covers accessibility checks that automated scanning cannot reliably determine. ScrollAccess includes a manual review checklist with categories such as keyboard, screen reader, visual & zoom, media, forms, motion, and cognitive accessibility.

  • Keyboard-only operation and focus behavior
  • Screen-reader reading order and accessible names
  • Zoom/reflow and visual review
  • Captions and transcripts
  • Form instructions and error recovery
  • Reduced-motion behavior
  • Plain-language and cognitive review
Note: Manual review should be performed by a person who understands the page’s purpose and interaction patterns.

Reports & Exports

Create accessibility reports from scan data and progress information. Reports can be exported in multiple formats for internal review, stakeholders, or clients.

  • CSV
  • PDF
  • Excel
  • Printable HTML

Reports can include issue summaries, progress information, issue details, and related standards/guidance depending on the report and export format.

Scheduled Report Emails

Where scheduled report email functionality is enabled by the site administrator, users can configure report delivery in account settings.

  1. Enable Email me scheduled accessibility reports.
  2. Choose Weekly or Monthly frequency.
  3. Choose the attachment format: Printable HTML, CSV, or Excel.
  4. Save account settings.
Note: The dashboard indicates when scheduled report emails are disabled by the site administrator.

Agencies & Teams

Agency functionality supports multi-user accessibility work. Available actions depend on the user’s role and permissions.

  • Invite team members and assign roles.
  • Change member roles or remove members when permitted.
  • Create and manage clients.
  • Assign connected websites to clients.
  • Review agency activity when permitted.
  • Configure agency branding such as company name, logo URL, primary color, and powered-by display where available.

Client Portal

Agencies can invite client portal users by account email and associate websites with client records. Portal access is permission-controlled and is intended to give clients access to the accessibility information assigned to them without exposing unrelated agency work.

Note: Only assign websites and information that the client should be permitted to access.

Plans, Billing & Usage

ScrollAccess plans can control website slots and feature/usage entitlements such as scans, AI usage, reports, toolbar access, and agency functionality. The dashboard billing area shows the plans available to the current installation/account.

ScrollAccess offers a 14-day trial. After the trial ends, an active paid subscription is required to scan websites or use the visitor toolbar; these features are unavailable without payment. Managed AI assistance remains subject to the selected plan and usage allowances.

If a website or feature is unavailable, confirm the active subscription, selected website, and remaining entitlement before troubleshooting the feature itself.

Account & Settings

User-facing settings include profile name, dashboard language, appearance/theme, timezone, scheduled report email preferences, Webflow connection controls, toolbar settings, and Designer API keys where the native Webflow Designer extension is used.

Dashboard language and toolbar website translation are separate features: dashboard language changes the ScrollAccess interface, while Website language translation is a visitor toolbar control that uses a translation provider API.

Privacy & Security

ScrollAccess includes security controls for API requests and stores sensitive provider credentials server-side. AI and translation API keys are encrypted before storage and are not included in public embed code.

  • Do not paste private API keys into support tickets or public code.
  • Restrict provider keys in the provider console where appropriate.
  • Rotate a key if you believe it has been exposed.
  • Use only the website embed code generated for the intended connected website.

Accessibility Testing Limitations

Automated scanning is useful for detecting many common issues, but it cannot find every accessibility barrier. For non-Webflow websites, public HTML scanning does not execute page scripts or inspect login-protected content. Webflow Designer scans instead inspect supported API-provided elements; they do not reproduce the rendered page or test dynamic behavior.

Combine automated results with manual keyboard testing, screen-reader testing, zoom/reflow review, content review, media review, and testing of dynamic interactions where appropriate.

Note: ScrollAccess provides accessibility tools, insights, and guidance. It does not provide legal advice, certification, or a guarantee of compliance with WCAG, ADA, EAA, Section 508, AODA, the Accessible Canada Act, or other laws/standards.

Troubleshooting

  • Non-Webflow website will not verify: confirm the exact hostname, publish the meta tag in the homepage head, or verify the full DNS TXT name/value and wait for DNS propagation.
  • Toolbar not detected: confirm the current embed snippet is installed site-wide, published, and allowed by the platform. If you replaced the embed key, replace the old snippet.
  • Translation unavailable: enable Website language translation, save a provider key, test the connection, and check provider API enablement, quota, billing, key restrictions, and language support.
  • AI unavailable: check your plan entitlement and remaining AI usage, retry, and contact ScrollAccess support if managed AI remains unavailable. Customers do not need to configure a provider key.
  • Scan misses dynamic content: non-Webflow public HTML scanning does not execute page scripts. Webflow Designer scanning reads supported API-provided elements and excludes forms, authentication controls, CMS collections, and shared component internals. Use manual review for dynamic interactions, rendered behavior, and assistive-technology testing.
  • Scheduled reports not arriving: confirm report email scheduling is enabled by the administrator and check the selected frequency/format and account email.

Frequently Asked Questions

Does ScrollAccess automatically fix my website?
ScrollAccess does not silently fix or publish your website. For supported findings, you can explicitly apply reviewed changes to matched elements in Webflow Designer, including image alt text, heading levels, and accessible labels. Other findings require manual editing. Rescan in Designer to review updated findings, then publish separately and inspect the live page. Undo is available for supported applied changes.

Can I configure the toolbar differently for each website?
Yes. Per-website preferences can include position, disclaimer, icon/custom icon URL, and enabled controls.

Do I need a separate key for website translation?
Yes. Translation uses the selected Google Cloud Translation, DeepL, or LibreTranslate provider credential. The key is stored encrypted and is not placed in the embed code.

Which AI providers are supported?
ScrollAccess manages the active AI provider. Customers use available AI tools through their ScrollAccess plan rather than configuring provider credentials. Review generated output before use.

Does the scanner guarantee WCAG compliance?
No. Automated testing cannot evaluate every accessibility requirement. Manual testing remains necessary.

Can agencies manage clients?
Yes, subject to plan and role permissions. Agency features include members, clients, website assignments, portal invitations, and branding options.

Support

If you need help with ScrollAccess, contact your ScrollAccess support channel and include enough information to reproduce the problem.

  • Your ScrollAccess account email
  • Website name and exact URL/hostname
  • Website platform
  • The feature you were using
  • Steps to reproduce the issue
  • Screenshot or screen recording
  • Browser and browser version
  • Any displayed error message
Note: Never send your password, AI API key, translation API key, payment credentials, OAuth token, or other private authentication secrets in a support request.

Important Notice

ScrollAccess is an accessibility testing, guidance, visitor-toolbar, reporting, and accessibility-management platform. It does not provide legal advice, legal certification, or a guarantee that a website complies with any accessibility law, regulation, or standard.

Automated results, AI output, toolbar controls, and reports should be combined with appropriate manual accessibility testing and professional review where needed.

Thank you.

Thank you for using ScrollAccess.