Terms of Service

Section 1

Service Description

RemediADA ("the Service," "we," "us," or "our") is a software platform operated by Remediada Holdings LLC. It checks websites, documents and mobile apps against the Web Content Accessibility Guidelines (WCAG) 2.2 at Level A and Level AA and against EN 301 549, and it writes fixes for what it finds. The website scanner runs axe-core alongside our own detection layers, including keyboard navigation testing and, on paid scans, AI visual analysis. On paid plans we generate source-code fixes and apply them through each platform's own API where the platform allows it (see Section 5). Monitoring subscriptions re-scan on a schedule, issue updated reports and alert you when new violations appear. Add-ons extend a paid audit to documents, app source code, running Android and iPhone apps, and EU deliverables (see Sections 4 and 12).

By accessing or using RemediADA, you agree to these Terms of Service. If you do not agree, do not use the Service.

Section 2

Scope and Limitations of Automated Testing

IMPORTANT: Industry research puts the share of accessibility issues that automated testing can detect at 57.38% (Deque Systems). Our audits are automated, so no report or score from us finds every accessibility barrier.

Automated testing is weakest at judging the meaning of content, the quality of alternative text, the reading order of complex layouts, whether a focus order makes sense, and any barrier that depends on context. The system makes these judgments where it can. A finding it cannot decide is marked for review instead of being reported as passed, and a fix it is not confident in is held or not applied (Section 5). Testing with assistive technologies (screen readers, switch access, magnification software) and with people who have disabilities finds barriers that software cannot. We recommend it before you rely on any score or report for a legal or regulatory purpose, and you are responsible for any further testing your risk profile calls for.

What our coverage figures mean. When we say the Service covers all 55 WCAG 2.2 Level A and AA success criteria, we mean that for each criterion a check exists that can report a failure, and a route exists that sends a detected failure to an automated fix. It does not mean that every failure under a criterion is caught, or that every caught failure is fixed. A criterion marked "passed" in a report means our checks found no failure on the pages and screens they reached. It does not certify that none exists.

Section 3

No Legal Guarantee

OUR SERVICES DO NOT CONSTITUTE LEGAL ADVICE AND DO NOT GUARANTEE PROTECTION FROM LITIGATION OR ENFORCEMENT.

We are not a law firm. Our assessments are technical, not legal. Nothing in a compliance score, audit report, conformance certificate, VPAT, accessibility conformance report or accessibility statement we produce is a legal opinion or an assurance of compliance with the Americans with Disabilities Act (Title II or Title III), Section 508, the European Accessibility Act, any national law that transposes it, or any other accessibility law. If you need legal counsel, consult a lawyer qualified in accessibility law in your jurisdiction.

Section 4

EU Deliverables (EN 301 549 Report and Accessibility Statement)

The EU Accessibility (EAA) Add-On produces an accessibility conformance report organised by the clauses of EN 301 549 (the "ACR") and a draft accessibility statement that follows Annex V of the European Accessibility Act (the "statement"). For these documents:

• Both are generated from our automated checks on the date shown on them, plus the answers you give in the questionnaire. A clause our checks did not reach is marked "Not Evaluated". We explain how each clause is filled on our methodology page.
• Neither document gives your product or service a presumption of conformity with the European Accessibility Act or with any harmonised standard. Neither is legal advice.
• EN 301 549 V3.2.1 remains the legal reference version of EN 301 549 until V4.1.1 is cited in the EU Official Journal. We report against V3.2.1 and label the requirements that the newer edition adds separately.
• You own the statement. You are responsible for the accuracy of your questionnaire answers, for reviewing the statement before you use it, and for publishing it in your own name. The statement describes your product or service, not ours.

Section 5

Remediation Services

Our remediation services generate AI-authored fixes and, where the platform allows it, apply them for you. What we can write depends on the platform, and we tell you which case you are in on every completed job:

• Applied by us. WordPress (REST API and application passwords), Shopify (Admin API; page and product content, not theme files), Webflow (Webflow API), and Squarespace (Products API; product descriptions and product images, not ordinary pages or templates).
• Website repositories on GitHub. We write the fixes to a new branch in your repository and open a pull request. By default we do not merge it: your site changes only when you merge it and publish. If you ask us to turn on automatic merging for your account, we merge each pull request into your default branch as soon as it opens (a squash merge where your repository allows one). If your branch protection requires a review, the merge does not go through and the pull request waits for you.
• App source repositories. For app source code (the App Source Accessibility Add-On) we open a pull request and never merge it. Merging is always your decision.
• Custom-coded sites with no connection. You receive downloadable patches to apply yourself.
• Wix. Wix does not expose the page HTML write access our executor needs, so we do not apply fixes to Wix sites. We generate the changes and you apply them in Wix Studio or Velo, then publish.

Anything outside the "applied by us" case and the automatic GitHub merge above is work you complete, and your live site does not change until you do.

How fixes are approved. On WordPress, Shopify, Webflow and Squarespace, buying remediation and connecting the platform is your instruction to start. The system scores each fix. Fixes it scores at or above its automatic threshold are applied directly. Fixes between its review threshold and its automatic threshold wait in your review queue until you approve them. Fixes below the review threshold are not applied. Before anything is written, the whole batch goes through a visual check, and if the page would look different with the fixes in place, the batch is held and nothing is written. On GitHub every fix goes into the pull request, and we merge it only if you have turned on automatic merging, as described above.

Automatic remediation (Ongoing Protection). If you subscribe to a monitoring plan with auto-remediation, each re-scan queues fixes only for the kinds of issue you have turned on for automatic fixing. Those fixes go through the same thresholds and visual check, and they have the same snapshot, audit trail and rollback protections. You may turn off auto-remediation at any time from your dashboard.

Every applied fix is written to the fix_snapshots audit trail with the original content before our change, the fixed content after it, the resource path that was modified, the timestamp, and a reference to the violation that triggered the fix. This audit trail is available in your dashboard and, on the platforms we write to, supports full or partial rollback for as long as your account is open.

You warrant that you have the authority to authorize the platform access and modifications described above. We modify only resources you have granted us access to, and only within the scope of the remediation you have bought.

Section 6

Rollback Policy

All remediation changes are tracked with before and after snapshots. On the platforms we write to, you may roll back any or all applied fixes from your dashboard at any time with the "Rollback" controls on the affected remediation job. Rollback writes the original content stored in the snapshot back to your platform and marks the snapshot as rolled back in our audit log. If the platform refuses the write, the snapshot is still marked and the stored original content remains available so it can be restored by hand.

A refund or a payment dispute on a purchase other than an add-on reverts applied fixes automatically: every fix we applied for your account, or, for a separate purchase we can link to your account only through that purchase, the fixes that purchase paid for. See our refund policy and Section 18, Chargeback and Dispute Policy.

Rollback can only be automated where we applied the fix in the first place. On Wix, on the Squarespace surfaces we cannot write to, and for changes you applied or merged yourself, there is nothing for us to revert on your behalf. For those, we provide the stored original content so you can restore it.

Section 7

Platform Access and Credentials

To perform remediation we need access to the platforms you want us to modify. All credentials are encrypted at rest using AES-256-GCM with a key derived via scrypt, and are decrypted only on our servers at the moment a job or integration call needs them. You can revoke platform access at any time by disconnecting the integration in your dashboard, which deletes the stored credentials. New jobs cannot use the connection after that; a job already running may finish with the credentials it loaded when it started. You can also revoke our access from the platform's own settings.

GitHub. Our GitHub App asks for read and write access to repository contents and to pull requests on the repositories you choose when you install it. We use it to read the repository, write fixes to a branch, open pull requests and, only where Section 5 says so, merge them. For app source checks we download a snapshot of the repository at one commit and read the source files in it to find issues. You can remove the App or narrow its repositories from your GitHub settings at any time.

We use platform access only for the checks and fixes you have asked for. We never share platform credentials with third parties.

Section 8

Uploaded Documents, App Builds and Source Code

You can upload documents (such as PDF and Office files), Android builds (APK or AAB), iPhone builds (a simulator app in a zip file) and app source code for us to check and, where the product includes it, fix. You keep ownership of everything you upload and of everything in a repository you connect. You grant us a limited, non-exclusive licence to store, copy, open, render, build, install, run and modify that material only to provide the Service to you, including sending parts of it to the sub-processors listed on our sub-processors page. The licence ends when the material is deleted.

You warrant that you have the rights needed to give us that material and to let us process it this way, including any personal data inside it.

How long we keep uploads. An original upload is deleted 90 days after the last check or fix that used it. An upload that never became a check (unfinished or refused) is deleted after 24 hours. An app build sent for a runtime check is deleted when the run ends, whether it passed or failed; if the run stops before it records a result, the build is deleted 90 days after its last check. App source code we download from GitHub is read during the run and not stored; for an iPhone check, a source archive is kept until the run finishes. Retention for everything else is set out in the Privacy Policy, Section 9.

Section 9

Running Your App on Our Devices

For a runtime check (the Android App Accessibility Add-On and the iPhone App Accessibility Add-On), we install your build in an Android emulator or an iPhone simulator on our own hosts, start it, and move through the screens it can reach. When you send iPhone source code, we build your project with Xcode on our host first, and the build runs your project's own build scripts.

• Your app runs with internet access. It may make network calls from our host to your own servers and to any third party it talks to. Private networks and our own services are blocked.
• Use test credentials and non-production data. Do not send a build that is signed in to a real user account, that sends payments, messages or notifications to real people, or that changes production data when it runs.
• We capture a screenshot of each screen we reach. Screenshots can show whatever the app displays, so a test account keeps real user data out of them.
• You are responsible for anything your app does while it runs, including calls it makes to other systems.

Section 10

Scanning Websites

The free scan and audit report features scan publicly accessible pages of a URL you submit. When our crawler looks for additional pages it identifies itself as RemediADA and follows robots.txt disallow and crawl-delay rules (a crawl-delay is honoured up to 10 seconds). The pages themselves are tested in a standard Chrome browser with a standard browser user agent, because some hosts refuse any other. The scanner caps how many pages it visits, and does not attempt to bypass authentication, CAPTCHAs, or access controls. We do not store a full copy of any website; we keep the HTML of failing elements, screenshots, and the other scan data described in our Privacy Policy.

You may only submit URLs that you own, operate, or have permission to audit. Submitting a URL you do not have permission to test is a violation of these Terms.

Section 11

Data Handling and Privacy

Our collection and use of personal information is described in our Privacy Policy, which is incorporated by reference into these Terms. Where we process personal data on your behalf, our Data Processing Agreement applies once it is countersigned.

Customer content (website HTML, screenshots, violation reports, uploads, app builds, source code and source-code snapshots) is processed only to deliver the Service to you. We do not sell or license it. We share it only with the sub-processors listed on our sub-processors page, each for the purpose stated there. For example, page snippets, screenshots, document images with the text around them, and app screenshots are sent to the Anthropic API to analyse them and write fixes. Under Anthropic's commercial terms, Anthropic may not train models on this content.

We keep customer content for the periods in the Privacy Policy, Section 9. When you close your account, erasure starts 30 days later. It waits while a subscription, monitoring enrollment, account suspension or open payment dispute is still on the account, and the Privacy Policy lists the records that stay after it.

Section 12

Payment Terms, Subscriptions and Add-Ons

All payments are processed by Stripe, Inc. By providing payment information you agree to Stripe's Services Agreement. We do not store card numbers; Stripe stores your payment method and gives us a token for future charges.

One-time services (audit reports and remediation) are charged once at purchase. Monitoring subscriptions are billed monthly or annually in advance and renew automatically until cancelled.

Included monitoring. A remediation purchase includes a free monitoring period of 30, 60 or 90 days, depending on the tier. It is not a subscription. When it ends, you are not charged and no subscription starts. A monitoring plan after that is a separate purchase, billed as described above.

Add-ons. The EU Accessibility (EAA) Add-On, the Document Fix Add-On, the App Source Accessibility Add-On, the Android App Accessibility Add-On and the iPhone App Accessibility Add-On are monthly subscriptions. Each renews automatically every month until you cancel it. Each of these works on a paid audit of your website: its checks and documents attach to that audit's report, so you need a paid audit before you can buy it. The EU Accessibility (EAA) Add-On also needs a certificate for that audit, which is issued once a remediation of it is complete, because its documents are built from the certificate. The SEO Growth Add-On and the SEO Pro Add-On are also monthly subscriptions that renew automatically, and the refund and dispute terms for add-ons apply to them too. The price and what each add-on includes are shown on our pricing page before you buy.

You can cancel a subscription or an add-on at any time from the billing portal, which the Manage billing button on /dashboard/billing opens once your account has a billing record. The portal opens for the Stripe customer behind your account's current plan. An add-on billed to an earlier Stripe customer may not appear there; email us to cancel it. You can always cancel by emailing support@remediada.com, and after your account is closed, email is the only way. A cancelled subscription stays active through the end of the current billing period. Closing your account does not cancel a subscription by itself.

If an add-on shares a subscription with another plan and the add-on is cancelled or removed, a renewal invoice Stripe had already drafted can still charge the add-on once. We are alerted automatically when that happens, and we refund that charge.

Quotes we issue expire 48 hours after we issue them, unless the quote shows a different expiry, and the payment page for a quote expires with it. Any discount applied to a quote is capped at a 30% maximum unless Remediada Holdings LLC specifically approves more.

Section 13

Refunds

Refunds are governed by our refund policy, which is part of these Terms. It includes a 30-day money-back guarantee on one-time purchases and explains what a refund does to applied fixes and to add-on access.

Section 14

Email Communications

We send two categories of email: transactional email (scan completion, report ready, receipts, password resets) and marketing email (outreach, product updates, newsletters). Transactional emails are tied to your account or a specific scan and are sent regardless of marketing preferences. Marketing emails comply with the CAN-SPAM Act, include a valid physical mailing address in the footer, identify themselves as commercial messages, and include a one-click unsubscribe link that removes you from all marketing communications within 10 business days.

Section 15

Intellectual Property

The RemediADA software, scanning engine, remediation worker, admin dashboard, and accompanying documentation are the proprietary property of Remediada Holdings LLC and are protected by United States and international copyright and trade-secret law. Your website content, uploads, app builds and source code are yours. Fixes we write to your website, documents or code become part of your content and are owned by you; we keep no rights in those changes beyond the audit trail entries we store. Your accessibility statement is yours (Section 4).

Section 16

Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW:

• OUR TOTAL LIABILITY TO YOU FOR ANY AND ALL CLAIMS ARISING OUT OF OR RELATED TO THE SERVICE IS CAPPED AT THE GREATER OF (A) THE TOTAL FEES YOU PAID TO US IN THE TWELVE (12) MONTHS IMMEDIATELY PRECEDING THE CLAIM, OR (B) ONE HUNDRED DOLLARS (USD $100).
• WE WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, OR PUNITIVE DAMAGES, INCLUDING LOST PROFITS, LOST REVENUE, BUSINESS INTERRUPTION, WEBSITE OR APP DOWNTIME, DATA LOSS, OR THIRD-PARTY CLAIMS (INCLUDING LITIGATION COSTS AND ATTORNEYS' FEES), EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
• WE MAKE NO WARRANTY, EXPRESS OR IMPLIED, THAT THE SERVICE IS FIT FOR ANY PARTICULAR PURPOSE, IS ERROR-FREE, OR WILL SATISFY ANY SPECIFIC LEGAL OR REGULATORY REQUIREMENT. THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE."
• BECAUSE AUTOMATED TESTING DETECTS ONLY A PORTION OF ACCESSIBILITY BARRIERS (SEE SECTION 2), WE EXPRESSLY DISCLAIM ANY REPRESENTATION THAT A PASSING SCORE, A COMPLETED REMEDIATION JOB, AN ACCESSIBILITY CONFORMANCE REPORT OR AN ACCESSIBILITY STATEMENT MAKES YOUR WEBSITE, DOCUMENT OR APP FULLY ACCESSIBLE OR LEGALLY COMPLIANT UNDER THE AMERICANS WITH DISABILITIES ACT (INCLUDING TITLE II AND TITLE III), SECTION 508, THE EUROPEAN ACCESSIBILITY ACT, ANY NATIONAL LAW THAT TRANSPOSES IT, OR ANY OTHER STATUTE OR REGULATION.
• WE ARE NOT LIABLE FOR FINES OR PENALTIES IMPOSED BY ANY AUTHORITY, INCLUDING A MARKET SURVEILLANCE AUTHORITY, OR FOR A DECISION BY AN APP STORE OR PLATFORM TO REJECT, REMOVE OR RESTRICT YOUR APP OR SITE.

Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above limitation may not apply to you in full.

Section 17

Indemnification

You agree to defend, indemnify, and hold Remediada Holdings LLC and its officers, employees, and agents harmless from any third-party claims, damages, liabilities, costs, and fees (including reasonable attorneys' fees) arising out of or related to: (a) your use of the Service; (b) your website content, uploads, app builds and source code; (c) your authority (or lack of authority) to grant us the access required to scan or remediate the websites and repositories you submit; (d) anything your app does while it runs on our devices; (e) the accessibility statement you publish; and (f) any violation of these Terms by you or anyone acting on your behalf.

Section 18

Chargeback and Dispute Policy

Audits, remediation and monitoring. When a payment dispute or chargeback is opened against one of these charges, the system automatically reverts the fixes we applied for your account on WordPress, Shopify, Webflow and Squarespace, using the stored snapshots and the same APIs that applied them, records the reversal in our audit log, and suspends your account's paid service. If the dispute is decided in our favour, neither the fixes nor your access come back on their own; contact us to restore access.

Separate purchases. If the disputed charge is for a separate purchase that we can link to your account only through that purchase (for example, a purchase made with your account's email address without signing in to the account, or a plan subscription your account has since replaced), that purchase is revoked, only the fixes it paid for are reverted, and your account is not suspended.

Add-ons. When a dispute is opened against an add-on charge, access to that add-on is suspended while the dispute is open. Billing for the add-on continues during the suspension. If the dispute is decided in our favour, access is restored. If it is decided in your favour and the charge is returned to you, the add-on is cancelled and its billing stops. If the add-on shares a subscription with another plan, access to the add-on ends and we remove only the add-on from that subscription, without proration; the other plan keeps billing as before. A renewal invoice Stripe had already drafted can still charge the add-on once; we refund that charge. An add-on dispute does not revert any fixes and does not suspend the rest of your account.

You agree that automatic rollback on a chargeback is an appropriate remedy, because our work changes your website's source content. Nothing in this section limits your right to raise a billing dispute with us. Please contact us before starting a chargeback so we can resolve the issue without triggering a rollback.

Section 19

Governing Law

These Terms are governed by the laws of the State of Wyoming, without regard to its conflict-of-laws principles. Any legal action arising out of or related to these Terms or the Service must be brought exclusively in the state or federal courts located in Sheridan County, Wyoming, and you consent to the personal jurisdiction of those courts. If you are a consumer, this does not remove any mandatory protection the law of your country gives you.

Section 20

Changes to Terms

This version of these Terms, including the Refund Policy that forms part of them, applies to accounts opened on or after September 29, 2026, and to accounts opened before that date from October 29, 2026. We may update these Terms from time to time. For material changes we give at least 30 days' notice by email to the address on file and by posting the updated Terms at this URL. For accounts that existed before a change, the change applies when that notice period ends, and your continued use of the Service after it ends means you accept the updated Terms.

Versions in force: Terms effective 2026-09-29; Privacy 2026-09-29; Refund 2026-09-29.

Section 21

Contact

For legal notices, compliance questions, or disputes under these Terms: