Accessibility widgets improve user experience and demonstrate inclusivity, but they can’t replace full accessibility compliance. This guide explains global accessibility laws and clarifies how accessibility widgets fit into a compliance strategy.

Jump to

How AccessYes Helps with Accessibility Compliance

Understanding the Accessibility Landscape

Digital accessibility requirements are defined by a combination of legal obligations and technical standards. Laws establish who must provide accessible digital experiences, while technical guidelines define how accessibility should be implemented and evaluated.

For most organisations, accessibility compliance is guided by two core frameworks:

• The Americans with Disabilities Act (ADA) and comparable national laws
• The Web Content Accessibility Guidelines (WCAG)

Understanding how these frameworks align helps organisations manage legal risk and plan effective accessibility improvements.

Americans with Disabilities Act

In the United States, the Americans with Disabilities Act (ADA) requires businesses that offer goods or services to the public to provide equal access to people with disabilities.

Although the ADA does not explicitly mention websites or mobile applications, courts now consistently interpret digital properties as places of public accommodation. As a result, websites and apps are expected to meet the same accessibility expectations as physical locations.

The ADA itself does not prescribe technical standards. In practice, courts and regulatory bodies rely on WCAG 2.1 Level AA to assess whether a website meets accessibility requirements. Organisations that fail to align with this standard face increased legal exposure.

Key compliance implications

• Websites and mobile apps fall within the scope of ADA enforcement.
• Accessibility is measured against WCAG 2.1 Level AA, even though the statute does not reference it.
• Compliance requires ongoing maintenance as content and functionality change.

Web Content Accessibility Guidelines

The Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium (W3C), serve as the global standard for digital accessibility. These guidelines make web content accessible for people with various disabilities, including visual, auditory, cognitive and motor impairments.

WCAG is built around four key principles, known by the acronym POUR:

• Perceivable – Information and user interface components must be presented in ways all users can perceive, such as providing text alternatives for images.
• Operable – Websites must work with multiple input methods, including keyboards and assistive devices, not just a mouse.
• Understandable – Content and operation must be clear, consistent and predictable to reduce user confusion.
• Robust – Content should be compatible with current and future technologies, including screen readers and other assistive software.

WCAG also defines three levels of compliance:

• Level A – Basic accessibility addresses the most urgent issues.
• Level AA – The standard most organisations aim for and the level required by most laws.
• Level AAA – The highest level of accessibility, ideal for specialised use cases and rarely mandated by law.

Most global regulations, including those in the U.S., Canada, the U.K. and the European Union, specifically reference WCAG 2.1 Level AA as the baseline requirement. By following WCAG, organisations can not only improve usability for all users and align with recognised compliance standards.

Applying Accessibility Standards in Practice

Meeting accessibility obligations typically involves:

• Aligning website structure and content with WCAG 2.1 Level AA
• Conducting regular accessibility audits and testing with assistive technologies
• Addressing both code-level and user-experience barriers

Accessibility widgets can support these efforts by improving usability and reducing certain user-facing barriers. However, they should be used alongside accessible development practices and ongoing compliance activities.

Accessibility Laws Worldwide

Accessibility laws worldwide build on the WCAG framework. While each country or region has its own legal framework, WCAG serves as the technical standard most frequently referenced when determining compliance.

United States

• Key Laws: ADA Title III and Section 508 of the Rehabilitation Act
• Requirement: Websites must align with WCAG 2.0 Level AA to reduce legal risk.
• Impact: Private businesses and federal agencies face lawsuits or penalties for inaccessible digital services.

European Union

• Key Laws: EU Web Accessibility Directive (2016) and the European Accessibility Act (2025)
• Requirement: Public-sector websites and mobile apps must meet WCAG 2.1 Level AA.
  From 2025, private-sector services, including e-commerce, banking and telecommunications, will also fall under the new act.

United Kingdom

• Key Laws: Equality Act 2010 and Public Sector Bodies Accessibility Regulations (2018)
• Requirement: Public-sector websites and mobile apps must comply with WCAG 2.1 Level AA.
  Private-sector services are expected to provide reasonable accessibility under the Equality Act.

Canada

• Key Laws: Accessible Canada Act (2019) and Accessibility for Ontarians with Disabilities Act (AODA, 2005)
• Requirement: Federally regulated organisations and Ontario-based entities must meet WCAG 2.0 Level AA.

Other Notable Regulations

• Australia: Disability Discrimination Act (1992) interpreted to require WCAG compliance.
• India: The Rights of Persons with Disabilities Act (2016) mandates WCAG 2.0 compliance for public and private websites.
• Israel: Equal Rights Regulations (2013) require WCAG 2.0 Level AA for all websites.

Role of Accessibility Widgets in Compliance

Accessibility widgets help make websites more user-friendly for people with disabilities. However, it’s essential to understand their strengths and limitations.

What Accessibility Widgets Can Do

Accessibility widgets provide immediate user-facing improvements without requiring major changes to a website’s code. They often include features such as:

• Text resizing
• Colour contrast adjustment
• Dyslexia-friendly fonts

These features make content easier to read for users with visual or cognitive disabilities.

Many widgets also enhance support for assistive technology. They enhance keyboard navigation and integrate ARIA roles, enabling screen readers to accurately interpret website elements.

Widgets install quickly, provide immediate improvements while you work on long-term fixes, and signal to users and regulators that you’re taking accessibility seriously.

How AccessYes Helps with Accessibility Compliance

Meeting accessibility requirements involves both structural accessibility (how developers build a site) and usability support (how users interact with it). Accessibility widgets address the usability layer by helping reduce common user-facing barriers, while organisations continue working toward full compliance through accessible design and development practices.

Accessibility Widget Capabilities

These tools offer immediate, user-controlled adjustments that improve how people with disabilities interact with a website. In particular, accessibility widgets are effective at resolving common usability challenges without requiring major changes to existing code.

Typical benefits include:

• Allowing users to resize text, adjust spacing and modify colour contrast
• Improving keyboard navigation for users who cannot rely on a mouse
• Enhancing screen reader interpretation through supplemental ARIA attributes
• Providing consistent accessibility support across desktop and mobile devices
• Deploying quickly with minimal technical effort

These features help reduce friction for users and demonstrate an organisation’s commitment to accessibility.

Scope and Limitations of Accessibility Widgets

Accessibility widgets are not a replacement for full accessibility compliance. They do not resolve issues in the underlying structure of a website and cannot:

• Replace semantic HTML or proper document structure
• Automatically make forms, navigation, or custom components accessible
• Guarantee compliance with ADA, WCAG or other accessibility regulations
• Eliminate the need for accessibility audits, remediation and manual testing

True accessibility compliance requires accessible design, clean and semantic code and ongoing evaluation as content and functionality evolve.

How AccessYes Supports Accessibility Compliance

AccessYes is designed to support accessibility efforts by providing immediate, WCAG-aligned usability enhancements while organisations address long-term compliance requirements.

The AccessYes Accessibility Widget:

• Bridges short-term usability gaps for users with disabilities
• Supports keyboard and screen reader interaction
• Helps organisations demonstrate active accessibility efforts
• Reduces risk by addressing common accessibility barriers early

AccessYes works best when used alongside accessible development practices, regular audits and continuous improvement, not as a standalone compliance solution.

Key Benefits

• WCAG-aligned adjustments: Users can resize text, adjust spacing, and change colour contrast without altering your design.
• Keyboard navigation: Enables smooth site movement using Tab and Arrow keys.
• Screen reader support: Adds ARIA roles and attributes to improve interpretation by assistive tools.
• Mobile-friendly design: Enhancements work seamlessly across all screen sizes.
• Quick deployment: Integrates with minimal code changes for fast implementation.
• Compliance support: Shows your commitment to inclusion and helps lower legal exposure.
• Ongoing updates: Regular improvements keep the widget aligned with evolving accessibility standards.

Widgets, ADA and WCAG: The Connection

In recent years, ADA lawsuits related to websites have increased significantly and courts have consistently pointed to WCAG 2.1 Level AA as the standard for compliance. This means that although the ADA itself does not specify technical standards, businesses are expected to ensure their websites comply with WCAG requirements to avoid lawsuits.

Accessibility widgets can play a helpful role in this process. By adding features like text resizing, high-contrast modes or improved keyboard navigation, widgets support ADA readiness by reducing barriers for users. They also show that an organisation is making an effort to improve accessibility.

However, they don’t fix issues in the underlying code. True ADA and WCAG compliance requires making structural improvements, such as creating accessible HTML and ARIA (Accessible Rich Internet Applications) roles, adding proper alternative text for images, labelling form fields clearly and ensuring compatibility with assistive technologies.

Equally important, compliance is not a one-off task. Businesses need to conduct regular accessibility audits and test their websites with screen readers and other assistive tools to ensure accessibility is maintained as content and design evolve.

Best Practices for Accessibility Compliance

Achieving accessibility means going beyond widgets. It’s about designing inclusivity into the foundation of your website. A widget can provide helpful tools for users, but it should always be combined with accessible design and development practices.

Practical Steps

• Run accessibility audits using tools such as WAVE, axe or Google Lighthouse to detect missing alt text, low contrast or ARIA errors.” Automated testing is not enough on its own, but it’s a great way to quickly catch common problems.
• Write accessible content:
  • Add alt text to images so screen readers can describe them.
  • Provide captions and transcripts for videos.
  • Use clear heading levels (H1, H2, H3) to give content a clear and logical structure.
• Test manually with screen readers and keyboard navigation as automation alone can miss critical usability issues.
• Stay current: Accessibility is constantly evolving. Keep track of WCAG updates and regional law changes.

Quick Accessibility Checklist

Conclusion

Accessibility compliance rests on two complementary pillars. Legal frameworks, such as the ADA and the UK Equality Act, set requirements for making digital services accessible, while the WCAG provide the technical standards to implement these requirements in practice. Together, they form the foundation for inclusive digital experiences.

Accessibility widgets offer immediate tools for adjusting text and contrast while showing users you value inclusion. But they’re only part of the solution.

True compliance requires addressing the underlying website structure through accessible coding, thoughtful design, and ongoing testing with assistive technologies. By integrating the AccessYes Accessibility Widget alongside these practices, your organisation can reduce legal risk, align with WCAG standards and create a digital presence that genuinely welcomes all users.

The post Accessibility Compliance Guide appeared first on CookieYes.

The Reports page provides insights into how visitors interact with the cookie consent banner on your website. Use this dashboard to track total consents, user preferences and pageview usage based on your current plan. These insights help you monitor consent trends and stay compliant with data privacy regulations.

How to Access Consent Trends and Pageviews Reports?

1. Log in to your CookieYes dashboard.
2. From the top navigation bar, go to More > Reports.
   
   
3. Reports are displayed based on the default date range (Last 7 days). To change it, open the date-range dropdown and pick a different range (for example: Last 30 days, This month, or All time).

Report Overview Sections

The Reports Overview includes two sections: Consent Trends and Pageviews. Together, they show how users interact with your cookie banner and how your website’s traffic performs.

• The Consent Trends section focuses on how visitors respond to your cookie consent banner, helping you understand user preferences and engagement.
• The Pageviews section tracks your website’s total traffic and monitors how much of it counts toward your monthly plan usage.

By default, reports display data for the last 7 days, but you can adjust the date range using the dropdown filter (for example: Last 30 days, This month or All time). Changing the date range updates both sections instantly, allowing you to analyse patterns and compare performance over time.

Consent Trends

The Consent Trends section provides a visual summary of how visitors respond to your cookie consent banner. It highlights user privacy and consent preferences, enabling you to evaluate banner performance and make compliance decisions. This section displays a donut chart with the total number of consent interactions for the selected date range. Each segment in the chart represents a type of user response:

By reviewing Accepted, Rejected, and Partially Accepted responses, you can see how visitors engage with your banner.

• A high number of Accepted responses often indicates user trust and clarity in your messaging.
• A high number of Rejected responses may suggest that the banner feels unclear, intrusive or lacks sufficient information.
• Partially Accepted responses show that visitors are selectively choosing categories, reflecting increased awareness and control over their privacy.

These insights help you assess how effectively your banner communicates consent choices. You can use the data to support compliance with regulations like GDPR and CCPA, refine banner design and messaging and improve user engagement. Analysing consent trends ultimately builds trust by giving users transparency and control over their data.

Pageviews

The Pageviews section provides an overview of the total number of pages viewed on your website within the selected date range. It includes all recorded pageviews tracked by CookieYes during that period, helping you understand your website’s traffic patterns and banner visibility. This count includes both pageviews within your current subscription plan and any additional traffic that exceeds your plan’s monthly limit.

In the example shown above, a total of 240,000 pageviews were recorded between November 29, 2024 and October 30, 2025. These pageviews are captured each time a visitor loads a page containing the CookieYes script. The line graph below visualises how traffic fluctuates over time, showing periods of low activity and occasional spikes on specific dates.

When your traffic exceeds the monthly plan limit, the additional pageviews are reflected in the summary card above the chart. The Extra pageviews used value helps you track usage beyond your plan allowance, while the graph itself shows overall traffic trends for the selected period.

Regularly monitoring this section helps you anticipate extra pageview charges, manage your website’s traffic usage and decide when to upgrade your plan.

Conclusion

The Reports page helps you monitor both cookie consent activity and website traffic in one place. By reviewing Consent Trends, you can gauge how effectively your banner communicates privacy choices to users. The Pageviews report, on the other hand, helps you track traffic usage against your plan limits and manage additional costs proactively. Regularly reviewing these reports ensures your website remains compliant, transparent and optimised for user trust.

The post Consent Trends and Pageviews Reports appeared first on CookieYes.

1. In the CookieYes Dashboard, navigate to the Profile icon in the top-right corner and click Billing & Invoices from the drop-down.
   
   
   
2. On the Billing & Invoices page, go to the Billing Details panel on the right and scroll to the Extra usage section. Toggle Enable Extra Pageviews to the On position.
   
   
3. A confirmation window will appear with the pricing and usage details. Click Enable Extra Pageviews to proceed.
   
   

Once enabled, additional usage charges will be automatically added to your monthly invoice.

The post How to Enable Extra Pageviews in CookieYes? appeared first on CookieYes.

For every successful conversion, you will receive a 30% commission, which recurs each year for three years as long as the referred user remains subscribed. You will also continue to earn a 30% commission on any upgrades or downgrades to that subscription for three years.

Eligibility & Requirements

Joining the CookieYes Affiliate Program is quick and easy for anyone with a relevant platform and an engaged audience. Submit your application, and our affiliate team will review and approve it. Once approved, you’ll receive your unique referral link and access to the affiliate dashboard. Learn more about the eligibility criteria in the section below.

Who Can Join

To be eligible for the CookieYes Affiliate Program, you must have a verified media platform with a relevant audience that aligns with our product and industry. We accept applications from affiliates who actively promote content in related niches and maintain a meaningful following. Once approved, you’ll receive your unique referral link and access to the affiliate dashboard.

Wondering if you’re a good fit?

Commission Structure

The CookieYes Affiliate Program offers a straightforward, high-reward commission model for every successful referral.

What You Earn

• Earn 30% commission on every successful conversion generated via your unique referral link.

There are no tiers, minimum targets, or caps. You earn 30% for every qualifying transaction, regardless of volume.

What counts as an approved conversion

Once a referred user signs up using your unique referral link, we track the referral in your affiliate dashboard. We’ll schedule your 30% commission payout once:

• The user signs up using your referral link and upgrades to a CookieYes Premium plan (Basic, Pro, or Ultimate) during or after the 14-day trial.
• The payment gateway and the CookieYes team have successfully processed and verified the subscription payment.
• The user doesn’t request a refund within 15 days of payment, clearing the refund window.

We mark the referral as approved once we successfully process the subscription payment. If the user later requests a refund, we adjust the corresponding commission amount from your future payouts in accordance with our policy.

Payout Schedule

CookieYes follows a transparent payout process to ensure timely commission payments for all affiliate partners.

Once your referred user meets the eligibility conditions, we’ll approve your 30% commission visible in your affiliate dashboard.

Payout Timing: All confirmed commissions are processed on the 15th of the following month, provided your total approved commission balance has reached the minimum payout threshold of $100 / £100 / €100. If the balance is below the minimum threshold, the amount will roll over to the next month.

Payout Method: You can select from available payout methods, such as PayPal or Bank Transfer, in your affiliate profile. Ensure your payout details are up to date to avoid any delays.

In the unlikely event that a user requests a refund after we process your payout, we adjust your future payouts accordingly, following our standard policy.

How The Process Works

This section explains each stage of the CookieYes Affiliate Program in detail. We will guide you from signing up to earning your commission, ensuring clarity, transparency, and ease throughout your referral journey.

Affiliate Program Workflow

Join the CookieYes Affiliate Program

Join the CookieYes Affiliate Program

Your journey as a CookieYes Affiliate Partner begins by signing up for our affiliate program. To sign up, follow the steps given below:

Sign up for your account

1. Visit the CookieYes Affiliate Signup form by clicking here.
2. Provide your basic information, including your name, email address, and password for future logins and hit the Sign up now button to submit your Affiliate Partner request.
3. This will sign you into the Affiliate Partner portal.
4. Click Start to explore your CookieYes Affiliate Portal.

Complete your profile

1. Fill in your contact details, language, address, company information, and marketing channel domains and choose your payout method (PayPal or Bank Transfer)
2. Click Finish to save your profile information.

Make sure to complete every field in the form, as incomplete applications will be rejected.

Your profile is now under review. You will receive an email notification confirming this.

Meanwhile, you can now access the Affiliate Portal to explore available features and settings. For a breakdown of its key features, click here.

Please ensure all fields are completed accurately, as incomplete applications will be rejected. Also, double-check that the account details you provide are correct, since all your commissions will be processed to this account.

Share Your Unique Referral Link

Share Your Unique Referral Link

Once your profile is verified, you will receive an email confirming your approval as a CookieYes Affiliate Partner. The email contains your unique referral link for the affiliate program.

You can now share this unique referral link on your marketing platforms and even with potential clients (Firms that you think would require a cookie consent solution). You can also create a short link by following these steps:

1. Navigate to your CookieYes Affiliate Program portal Dashboard by clicking here.
2. Click the Copy option to copy your unique referral link.
3. Enable “Create short link” to generate a clean, shareable URL optimised for social media and easier to distribute.

Pro Tip: To maximise reach, distribute your affiliate link via social media, email campaigns, or blog content. The more visibility your link gets, the more chances you have to earn. Every successful sign-up brings you a 30% commission — no questions asked! For additional tips or personalised guidance, feel free to email us at affiliate@cookieyes.com

User Onboarding & Trial Activation

User Onboarding & Trial Activation (Done by the Referee)

When a user clicks on your unique referral link, they land on the CookieYes website, where they can sign up and activate a 14-day free trial of any of the CookieYes premium plans – Basic, Pro, or Ultimate.

We track and record this in your Affiliate Dashboard, so you can monitor the user’s activity in real time. We confirm your commission only after the user upgrades to a paid subscription following their 14-day free trial.

Note: The CookieYes Affiliate Program includes a 30-day referral window. Tracking begins from the user’s first click on your affiliate link and remains valid for 30 days. For successful referral attribution, the user must complete the sign-up within this period using the same device and browser from which the initial click was made.

Subscription to CookieYes premium plan

Subscription to CookieYes premium plan (Done by the Referee)

After signing up using your referral link, the referred user upgrades to one of the CookieYes premium plans (Basic, Pro, or Ultimate) at any time during or after their 14-day free trial.

Once we successfully process the payment, we will mark your 30% commission as approved, and it will appear in your affiliate dashboard.

Conversion & Payout

Conversion & Payout (Done by CookieYes)

If your total approved commission balance reaches the minimum payout threshold (USD 100 / GBP 100 / EUR 100), the payout will be processed on the 15th of the following month. After processing, we credit the payout to your account by the end of that month at the latest.

If a user cancels their subscription during the refund period, we adjust the corresponding commission amount from your future payouts in line with our policy.

Note: See the payout schedule section above for exact dates, methods, and refund adjustment rules!

Affiliate Dashboard & Reporting

Dashboard

You can view your daily conversions and click performance, including comparisons to the previous day and total commission in real-time within your CookieYes Affiliate Program Dashboard. The dashboard gives you a clear overview of your referral activity and earnings.

Reporting

The Reporting section provides a visual breakdown of your affiliate performance. You can view graphical representations of clicks, conversions, and commission amounts, filterable by date for deeper insights. This section also includes extra details such as the source of each payout and audience-related metrics. For further analysis or record-keeping, you can download or export these reports as CSV files with a single click.

To learn more about the various sections of the CookieYes Affiliate Portal and their functionalities, click here.

Conclusion

The CookieYes Affiliate Program is a great way to earn consistent rewards by referring CookieYes to users who could truly benefit from a powerful and scalable cookie consent solution. With a clear process, real-time tracking, and reliable payouts, you have everything you need to grow your earnings.

Earn with the CookieYes Affiliate Program today. Share your affiliate link, monitor your performance through the dashboard, and receive rewards for every successful referral. It’s that simple.

You can reach us at affiliate@cookieyes.com for any queries.

The post CookieYes Affiliate Program (Tapfiliate) appeared first on CookieYes.

To begin with, Sign up on CookieYes and try it for free.

Steps to Generate a Cookie Policy

Step 1: Access the Cookie Policy Generator

From the top navigation menu, click on More and select Cookie Policy Generator from the dropdown menu.

Step 2: Language settings

Select the Primary Language

Choose your preferred primary language for the cookie policy by clicking one of the available options. The selected language will be highlighted with a checkmark.

Enable Multiple Languages (Optional)

Toggle on the Generate policy in multiple languages option. Once enabled, additional language options will appear. Select one or more additional languages from the list.

Save and Continue

After selecting your language preferences, click Save draft if you want to save your progress and return later or click Next to proceed to the next step: About cookies.

Step 3: About Cookies

In this step, you can define the introductory section of your Cookie Policy by explaining what cookies are and why your website uses them.

Heading

Use the Heading field to specify a clear title for this section. You may keep the default text or customise it to match your website’s style and tone.

Add or Edit the Description

In the Description field, provide a clear explanation of cookies and their purpose. The default text covers what cookies are, why your website uses them and how they benefit users (such as improving functionality, security and performance). Edit or expand the text to ensure it matches your website’s practices.

Preview the Cookie Policy

Click Preview cookie policy (bottom left of the screen) to review how your content will appear to users. Use this option to confirm clarity, formatting and tone before proceeding.

Continue

Click Next to move to Use of cookies.

Step 4: Use of Cookies

In this step, you’ll describe how your website uses cookies and explain their purpose to your users.

Heading

In the Heading field, enter a clear and user-friendly title. You can either use the default heading as is or modify it to match your site’s tone and audience.

Description

Use the Description field to explain in detail how your website uses cookies. The default text includes information on the use of first-party cookies (primarily for website functionality) and the role of third-party cookies (such as analysing site performance, tracking user interactions, enhancing security and providing relevant ads). You may update the description as needed to ensure accuracy for your website’s practices.

Save and Continue

When you’re ready, click Next to proceed to the next step, Types of Cookies.

Step 5: Types of Cookies

Heading

In the Heading field, you can keep the default title “Types of cookies we use” or edit it to better reflect your website’s tone and your audience’s expectations.

Review the cookie list

The cookie list shown here is based on your last website scan. To refresh the list, click Scan again. You’ll be redirected to the Cookie Manager, where you need to click Scan now to run a new scan.

Check cookie categories and details
The list organises cookies into categories such as:

1. Necessary – cookies required for basic site functionality and security.
2. Functional – cookies enabling features like content sharing or feedback collection.
3. Analytics – cookies for tracking and analysing visitor interactions.
4. Performance – cookies for monitoring site performance and improving user experience.
5. Advertisement – cookies are used to deliver relevant ads.

Each entry includes details about the cookie’s name, duration and purpose. Confirm that the descriptions are clear and accurate.

Proceed

After reviewing the cookie list, click Next to proceed to Cookie Preferences.

Step 6: Cookie Preferences

Heading

Use the Heading field to title this section. The default text is “Manage cookie preferences”, but you can update it to align with your site’s tone or user expectations.

Revisit consent widget code

This section includes a pre-generated HTML snippet that enables users to reopen the consent banner after initial interaction.

Description

The Description box explains how users can manage their cookie settings. It also includes helpful links to official browser support pages for managing or deleting cookies. You can customise this description to include additional browser types, site-specific instructions or translations, depending on your audience.

Set the effective date

This is the Effective Date of your cookie policy. By default, it shows the current date, but you may change it if needed. This date indicates when your cookie policy comes into effect.

Finalise or Save your policy

Click Generate cookie policy to complete the process and publish the cookie policy, or click Save draft if you want to continue editing later without publishing.

Step 7: Generate and Add the Cookie Policy to Your Website

Review the generated Cookie Policy Preview in your selected language(s). When you’re ready, click Add policy to site in the top-right corner.

Add the Policy to Your Site

After clicking Add policy to site, a modal window will appear prompting you to choose a method to embed the policy.

You have two options:

Option 1: Code Snippet

Automatically keeps your cookie policy updated whenever changes are made in the CookieYes platform.

Steps:

1. Choose the preferred language.
2. Click Copy code to copy the JavaScript snippet provided.
3. Paste the code into the required section of your website’s HTML.

Option 2: HTML Format

Use this option if you prefer to manually update the website every time you modify the cookie policy.

Steps:

1. Select the language.
2. Click the Copy code to copy the generated HTML code.
3. Paste it into the desired location on your site.

Conclusion

You’ve successfully generated, published your cookie policy and added it to your website. With these steps, your visitors can easily understand how cookies are used on your site, and you can meet important privacy compliance requirements such as GDPR, CCPA and other data protection laws.

By embedding the policy directly into your site, you ensure it’s easily accessible and kept up to date, especially if you choose the recommended Code Snippet method. This not only strengthens legal compliance but also builds user trust by providing transparency about your data practices.

The post How to Generate a Cookie Policy in CookieYes appeared first on CookieYes.

This page lists all static IP addresses used by CookieYesbot to perform compliance scans on websites connected to our platform. We recommend allowlisting these IPs in your firewall, bot management system, or CDN (e.g., Cloudflare) to prevent unintended blocking of our scans.

Scanning IPs

The following IP addresses are used for scans triggered by users:

• 34.248.84.9
• 34.255.233.191
• 54.220.97.228
• 52.16.192.187
• 3.248.28.214
• 54.77.122.154
• 63.32.8.12
• 52.209.242.108
• 54.229.175.38
• 46.51.164.219

How to Use This List

• Firewall/Access Control: Add the relevant IPs to your allowlist to ensure uninterrupted scanning.
• Cloudflare Customers: Create a rule to allow requests from these IPs under Security → WAF → Tools.
• Bot Detection Systems: Configure exceptions using our User-Agent substring:

CookieYesbot

Contact

If you have questions about CookieYesbot’s IP addresses or encounter issues, contact our support team:

Email: support@cookieyes.com
Website: https://www.cookieyes.com

Frequently Asked Questions

Q1: Why do I need to whitelist these IPs?
If your firewall or CDN blocks CookieYesbot’s requests, our scanner will not be able to verify your banner setup or compliance settings. Whitelisting prevents false positives.

Q2: Will the IP addresses ever change?
While we try to keep IPs static, changes may occur for operational or security reasons.

Q3: Can I whitelist by User-Agent instead of IP?
Yes. Most bot management tools allow whitelisting by User-Agent. The match pattern is CookieYesbot. However, IP allowlisting is generally more reliable.

Q4: Does CookieYesbot access private or login-protected pages?
No. By default, scans are limited to public pages. If you require scanning behind authentication, it must be explicitly configured by you in the CookieYes dashboard.

Q5: What happens if I don’t whitelist?
The scanner may be blocked or challenged, leading to incomplete or inaccurate scan reports. This can affect compliance verification results.

The post CookieYesbot Scanner IP Addresses appeared first on CookieYes.

CookieYesbot is the official scanning bot used by CookieYes to verify the implementation and behavior of cookie consent banners, privacy notices, and compliance configurations across websites that use our platform.

This bot helps ensure that websites meet requirements under data protection laws such as the GDPR, CCPA, ePrivacy Directive, and other global privacy frameworks.

What CookieYesbot Does

CookieYesbot performs automated scans on publicly accessible web pages to:

• Detect and validate cookie consent banner implementations
• Identify region-specific banner behavior and consent flows
• Verify whether the correct banner is active and properly displayed
• Audit script configurations and policy link placements
• Provide diagnostic insights to CookieYes users for compliance optimization
  

CookieYesbot does not index content, scrape data, or perform deep or intrusive crawling. Scans are limited to the scope of consent management verification.

Bot Category

Category: Security
CookieYesbot is classified as a Security and Compliance scanner that assists websites in maintaining up-to-date and legally compliant consent mechanisms.

User Agent

All requests made by CookieYesbot use the following user agent string:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko; CookieYesbot/1.0; +http://www.cookieyes.com/documentation/cookieyesbot) Chrome/131.0.6778.0 Safari/537.36

We recommend whitelisting this user agent in your firewall or bot management systems if you are a CookieYes customer or partner, to ensure uninterrupted scan performance.

Security and Compliance

CookieYesbot is designed to operate within strict security and ethical guidelines:

• No personal data is collected or stored
• All requests are lightweight and limited in frequency
• The bot is used solely for the purpose of consent compliance and diagnostic scanning
• Scanning occurs only upon account connection, user-triggered requests, or scheduled audits for active CookieYes users

Access Control

CookieYesbot does not scan authentication-required pages or private environments by default. Scans are restricted to publicly available content unless a customer has explicitly requested or authorized a scan behind authentication (e.g., through session token or whitelisted access).

Contact and Support

If you have questions, encounter an issue with CookieYesbot, or would like to verify a scan, please reach out to our support team:

Email: support@cookieyes.com
Website: https://www.cookieyes.com

The post CookieYesbot Technical Documentation appeared first on CookieYes.

The AccessYes Accessibility Widget is a no-code accessibility solution designed to work across various platforms and CMSs, offering user-facing accessibility controls to help meet global compliance standards. It enables organisations to provide user-facing accessibility controls such as keyboard navigation, contrast modes and text resizing, supporting compliance with global accessibility standards like WCAG 2.1, the Americans with Disabilities Act (ADA) and the European Accessibility Act (EAA). This guide explains how to customise the AccessYes Accessibility Widget using its JavaScript embed. You can configure its position, accessibility statement link and enable or disable modules directly within the configuration object before the widget loads.

This document assumes you’re embedding the widget via JavaScript using the standard snippet provided by AccessYes.

Core Configuration Structure

The AccessYes Accessibility Widget can be customised using a JavaScript configuration object called _cyA11yConfig. The configuration object controls the widget’s behaviour, placement and enabled features. Below is the core structure with commonly used options:

window._cyA11yConfig = {
  iconId: "default", 
  position: {
    mobile: "bottom-right", 
    desktop: "bottom-right" 
  },
  modules: {
    statement: {
      enabled: true,                 
      url: "https://yoursite.com"   
    }
  }
};

Configuration Parameters

This section provides an in-depth breakdown of each configuration property available in the _cyA11yConfig object. These settings give you granular control over the widget’s interface, positioning and feature modules.

Use this reference to better understand what each key controls, the values it accepts and how each setting influences the widget’s behavior.

Property	Type	Default	Description
iconId	string	“default”	Controls the widget’s icon appearance.
position.mobile	string	“bottom-right”	Choose a position that doesn’t clash with other UI elements.
position.desktop	string	“bottom-right”	—
modules.statement.enabled	boolean	true	Show/hide the Accessibility Statement link.
modules.statement.url	string	—	Required if enabled: true.

Widget Icon

Defines the style or theme of the Accessibility Widget icon, allowing you to align its appearance with your brand or accessibility focus.

iconId: "default"

Accepted Values:

• "default": Standard default icon style.
• "accessibility": Universal accessibility icon.
• "wheel": Wheelchair symbol, representing mobility accessibility.
• "assist": Assistive tech-themed icon.

Use Case: Choose an icon that complements your site’s accessibility messaging. For example, use "wheel" to highlight mobility support or "assist" for general assistive functionality.

Position

Specifies where the Accessibility Widget appears on both mobile and desktop views to ensure optimal visibility and avoid UI conflicts.

position: {
  mobile: "bottom-right",
  desktop: "bottom-right"
}

Accepted Values:

• "bottom-right"
• "bottom-left"
• "top-right"
• "top-left"

Use Case: Adjust the widget’s position to prevent overlap with other interactive elements (like chat widgets) or to support layout direction (e.g., use "bottom-left" for RTL languages).

Accessibility Statement

This module displays a link to your website’s Accessibility Statement inside the widget menu, helping demonstrate transparency and support for accessibility compliance.

statement

modules: {
  statement: {
    enabled: true,
    url: "https://example.com/accessibility-statement"
  }
}

Parameters:

• enabled: Enables or disables the Accessibility Statement link in the widget.
• url: Full URL to your published Accessibility Statement page.

Accepted Values:

• enabled: true or false
• url: A valid, publicly accessible URL (required only if enabled is true)

Use Case:

Use this module to provide users with direct access to your Accessibility Statement. This builds trust and aligns with accessibility standards such as WCAG and the EAA.

If you do not want to display the Accessibility Statement link, set ‘enabled’ to false. You may also leave the url field empty or remove it entirely.

Here’s what the configuration should look like:

modules: {
  statement: {
    enabled: false,
    url: "" // Optional when disabled
  }
}

Configuration Example

Below is an example of how to define the _cyA11yConfig object to customise the AccessYes Accessibility Widget. This configuration controls the icon type, widget placement across devices and accessibility statement linking:

window._cyA11yConfig = {
  iconId: "assist",
  position: {
    mobile: "bottom-left",
    desktop: "bottom-right"
  },
  modules: {
    statement: {
      enabled: true,
      url: "https://example.com/accessibility-statement"
    }
  }
};

The image below illustrates a website with a fully configured accessibility setup. The AccessYes widget is displayed at the bottom-right corner, using the assist icon style, while an additional blue accessibility icon appears at the bottom-left, demonstrating the mobile-specific layout. This configuration highlights the flexibility in widget positioning across various devices and demonstrates how multiple icons can coexist for improved accessibility.

Best Practices

• Always declare the _cyA11yConfig object before loading the widget script.
• Validate that all URLs are correct and publicly accessible.
• Keep your Accessibility Statement up to date and ensure the link (url) points to the latest version.

Conclusion

The AccessYes Accessibility Widget offers flexible configuration options that let you tailor its behaviour and appearance to your website’s accessibility goals and user experience needs. By customising the _cyA11yConfig object before the script loads, you can:

• Align the widget’s icon with your brand or accessibility message
• Position it strategically across devices to prevent UI overlap
• Link to your Accessibility Statement to reinforce transparency and compliance

For best results, always declare the configuration before loading the widget script, and keep your settings updated to reflect any changes in your site’s structure and accessibility policies.

This documentation provides a reference foundation for getting started, but the widget may evolve over time, so check for new options or modules as they become available in future updates.

The post Customising the AccessYes Accessibility Widget via JavaScript appeared first on CookieYes.

Ensure that Microsoft Clarity is installed on your Wix site, either via the Wix App Market or by manually adding the Clarity tracking code and that your site is connected to a Clarity project.

Follow the steps below to enable Microsoft Clarity in CookieYes:

1. From your Wix dashboard, go to Apps > CookieYes GDPR Cookie Banner.
2. Navigate to More > Advanced Settings > Microsoft consent mode & Clarity API integration.
3. Enable the Microsoft Clarity Consent API integration option.

Once enabled, CookieYes will automatically handle user consent signals for Clarity. Clarity will only start recording a session if the user has given consent to the use of tracking cookies, ensuring compliance with user privacy preferences.

The post Does CookieYes integrate with the Microsoft Clarity Consent API on Wix and how do I set it up? appeared first on CookieYes.

• Google Tag Manager (GTM) integration
• Custom script implementation

Both methods ensure that the UET tag only fires after users give consent to advertisement cookies, helping you stay compliant with privacy laws such as the GDPR.

Steps to enable it via the CookieYes app on Wix:

To enable Microsoft UET Consent Mode via the CookieYes app on your Wix site:

1. From your Wix dashboard, go to Apps > CookieYes GDPR Cookie Banner.
2. Navigate to More > Advanced Settings > Microsoft consent mode & Clarity API integration.
3. Enable the toggle for Support Microsoft UET Consent Mode.

For detailed instructions, refer to our help guide on setting up Microsoft UET Consent Mode.

The post Does CookieYes support Microsoft UET Consent Mode on Wix? appeared first on CookieYes.