Editorial Board
—
12 June 2026
Google just added agentic browsing to Lighthouse — here's what it means for accessibility
AI agents are no longer a future scenario. They're browsing, comparing, booking, and purchasing right now — on behalf of real people
Introduction
This Privacy Notice aims to clearly and transparently explain which personal data we collect when you visit our website, why we collect it, how we use it, and what Your rights are.
We process your personal data in accordance with Regulation (EU) 2016/679 (GDPR) and applicable national data protection laws. We are committed to ensuring that all processing activities are carried out in accordance with the principles of lawfulness, fairness, transparency, data minimization, integrity, and confidentiality.
Specifically, in this notice you will find information about:
-
which data we collect about you and for what purposes;
-
the legal bases on which we process such data;
-
who we may share your data with;
-
how long we retain your data;
-
your rights and how to exercise them.
While we sometimes need Your data for example, to respond to your requests or improve our website), we do so with respect, care and only when truly necessary.
Our Privacy Promises
-
We deeply value your privacy, and for this reason, we guarantee that:
-
We treat your data as if it were our own.
-
We use your data only for the purposes outlined in this notice.
-
We retain your data only for as long as strictly necessary.
-
We do not share your data with third parties without a valid legal basis or your explicit consent.
1. Who Processes Your Personal Data
The Data Controller — that is, the entity that determines the purposes and means of the processing of Your personal data — is AccessiWay S.a.S., with registered office at 7 Rue du Général Henrion Bertier, 92200 Neuilly-sur-Sein registered with the Nanterre Trade and Companies Register under number 914 022 595.
AccessiWay is part of the team.blue group and, in certain cases, acts as joint controller together with team.blue NV, with registered office at Skaldenstraat 121, 9042 Ghent, Belgium. In this context, Your personal data may be shared within the group for statistical, administrative, operational, and service improvement purposes.
AccessiWay and team.blue have defined their respective roles and responsibilities under a joint controllership agreement pursuant to Article 26 of the GDPR, ensuring full compliance with data protection regulations.
For more information regarding joint controllership or to exercise Your rights, you may contact AccessiWay via email at the following email addresses:
📧 legal.fr@accessiway.com or info@accessiway.com.
2. Who This Privacy Notice Applies To
This notice applies to:
-
users who browse the website www.accessiway.com,
-
individuals who contact us through the form available on the website or via email;
-
users who interact with tools we have implemented (e.g. widgets, cookies);
-
individuals who, through the website or other channels, access external platforms or third-party entities through which they may submit a job application (e.g. recruiting portals or employment agencies).
-
In such cases, the privacy notices of the third parties involved — independent from AccessiWay — also apply.
3. What Data We Process
To manage your interaction with our website, we may process the following categories of personal data:
-
Identification and contact details such as name, surname, company, job title, email address, and phone number.
-
These data may be partially processed through our customer relationship management (CRM) system.
-
Data relating to your interaction with our services such as information collected via the website or through Hubspot, such as communication history, preferences, requests, and commercial or technical notes.
-
Technical data such as IP address, device type, operating system, browser, access times, and other data automatically recorded by our systems or servers.
-
Browsing data and preferences such as collected via cookies or similar technologies, in accordance with the choices expressed through the cookie consent banner.
-
Application data such as personal information included in your CV or other documents submitted through third-party platforms (e.g. professional experience, education, contact details).
-
These data are processed by AccessiWay only after being transmitted by the third party, which remains autonomous in the initial processing.
4. Purposes and Legal Basis of Processing
We process Your personal data in compliance with Regulation (EU) 2016/679 (GDPR) and applicable national data protection laws. Your data may be processed for the following purposes:
-
Technical operation of the website
We process technical data, using technical cookies and similar tools, to allow You to access the site, view it correctly, and ensure it functions properly (e.g. browsing, content loading, storing preferences).
📌Legal basis: this processing is necessary to provide a service requested by the user, pursuant to Article 6(1)(b) of the GDPR. Your consent is not required for these cookies.
-
Handling contact or support requests
When you send us a request — via the contact form or by email — we process your data to respond and provide the information requested.
📌 Legal basis: this processing is necessary to take steps at your request prior to entering into a contract, pursuant to Article 6(1)(b) of the GDPR.
-
Compliance with legal obligations
In certain cases, we may need to process your data to comply with legal obligations, such as tax, accounting, or IT security requirements.
📌 Legal basis: this processing is based on compliance with a legal obligation, pursuant to Article 6(1)(c) of the GDPR.
-
Statistical analysis and website improvement
We use analytical tools (e.g. analytical cookies) to collect aggregated data in order to understand how the website is used and to improve its content and functionality.
📌 Legal basis: we process this data only with your freely given and specific consent, pursuant to Article 6(1)(a) of the GDPR.
-
Marketing and Profiling
If you authorize us to do so, we may use your data to send you promotional communications or provide personalized content (e.g. through profiling cookies).
📌 Legal basis: this processing is carried out only with your explicit consent, pursuant to Article 6(1)(a) of the GDPR. You may withdraw your consent at any time without affecting the lawfulness of processing based on consent before its withdrawal.
-
Management of job applications through third parties
We may receive job applications via third-party platforms (e.g. job portals) or through recruitment agencies. In such cases, we process the submitted data to assess your suitability for the proposed role.
📌 Legal basis: this processing is necessary to take steps at your request prior to entering into a contract, pursuant to Article 6(1)(b) of the GDPR.
Note: the privacy policies of the third-party platforms or agencies involved also apply, independently of AccessiWay.
5. Cookies and Tracking Tools
This website uses a cookie management system provided by iubenda, which allows you to:
-
view a full and transparent list of the cookies in use;
-
modify or withdraw your consent at any time;
-
access the complete Cookie Policy, integrated in the cookie widget.
You can manage your preferences by clicking on the cookie widget icon located at the bottom left corner of every page on the site.
Technical cookies are necessary and therefore enabled by default. Other non-essential cookies (analytical, profiling) are only enabled with your consent.
For more information, please refer to the full Cookie Policy accessible from the cookie widget.
6. Use of accessWidget
This website integrates accessWidget, an automated accessibility tool developed by accessiBe Ltd. and distributed by AccessiWay. The widget allows users to personalize their browsing experience based on their needs.
When the user activates the widget, their IP address is technically transmitted, but:
-
it is not stored, tracked, or associated with identifiable individuals;
-
it is anonymized via a proxy located in the European Union;
-
it is not used for profiling or marketing purposes.
📌 Legal basis: provision of a service requested by the user (Article 6(1)(b) of the GDPR).
7. Data Security
We adopt appropriate technical and organizational measures to ensure the security, integrity, and confidentiality of the personal data we process. These measures are designed to prevent unauthorized access, loss, disclosure, or alteration of your data. In particular, we implement:
-
secure connections via HTTPS (SSL/TLS);
-
authentication systems and access control;
-
access limitation and internal access tracking mechanisms;
-
regular audits and verification procedures;
-
continuous updates to systems and security measures according to the level of risk.
8. Data Retention
Your personal data is stored only for the time strictly necessary to achieve the purposes for which it was collected. Specifically:
-
Contact data: up to 10 years if relevant for contractual or legal purposes;
-
Technical and browsing data: according to what is outlined in the Cookie Policy;
-
Marketing data: until consent is withdrawn.
9. Your Rights (Data Subject Rights)
As a data subject, you may exercise the rights provided under Articles 15–22 of the GDPR at any time. In particular, you have the right to:
-
Obtain confirmation as to whether or not your personal data is being processed and access such data (right of access);
-
Request the rectification of inaccurate personal data or the completion of incomplete data (right to rectification);
-
Request the erasure of your data, if the conditions set out in the GDPR are met (right to erasure);
-
Obtain restriction of processing where applicable (right to restriction);
-
Object to the processing of your data, in whole or in part, under certain circumstances (right to object);
-
Receive your data in a structured, commonly used, and machine-readable format, and, where technically feasible, have it transmitted directly to another controller (right to data portability);
-
Withdraw your consent at any time, without affecting the lawfulness of processing based on consent before its withdrawal.
📧 You can exercise Your rights at any time by contacting us at: legal.fr@accessiway.com.
🔗 If you are located in France and believe that the processing of your personal data violates applicable law, you have the right to lodge a complaint with the French Data Protection Authority (Commission Nationale de l’Informatique et des Libertés – CNIL) via the website: www.cnil.fr.
*If you have difficulty accessing our form, please feel free to contact us. Send an e-mail to info@accessiway.com
AI agents are no longer a future scenario. They're browsing, comparing, booking, and purchasing right now — on behalf of real people. And Google has just made something explicit: starting with Lighthouse 13.3 (released May 2026), its open-source auditing tool now includes a brand-new experimental category called Agentic Browsing.
This isn't just a technical update for developers to note and move on. It's a signal about the direction of the web — and for teams already doing serious digital accessibility work, it's also a reminder that they're further ahead than they might think.
What is the Lighthouse agentic browsing category?
Lighthouse already measures four things: performance, Web Content Accessibility Guidelines (WCAG) compliance, SEO, and best practices. The Agentic Browsing category adds a fifth lens — one that asks a simple but pointed question: can an AI agent actually use your site?
Unlike the familiar 0–100 score in the Performance or Accessibility categories, the Agentic Browsing category doesn't produce a weighted number. Instead, it returns a fractional pass/fail ratio across its checks, pass or fail status on specific technical requirements, and informational counts that give a quick snapshot of overall readiness.
Google is explicit that the standards here are still forming. The category is marked as experimental, which means there's no ranking signal attached — yet. What it represents today is a clear statement of direction, and a playbook worth understanding before it becomes standard.
The four checks — what they test and what they mean
1. The accessibility tree — the check that connects to your existing work
This is the most mature of the four checks and the one most directly tied to accessibility practice your team may already have underway.
AI agents don't see a page the way a person does. They navigate using the accessibility tree — the structured, semantic representation of a page's content and interactive elements that browsers generate from your HTML. Google's own documentation describes this as agents' "primary data model."
If that sounds familiar, it's because it's the same tree that screen readers rely on. A button with no accessible name is invisible to someone using a screen reader, and equally invisible to an AI agent trying to complete a task. The same is true for unlabeled form fields, improperly nested ARIA (Accessible Rich Internet Applications) roles, and broken focus management.
Lighthouse filters a specific subset of WCAG checks that are critical for machine interaction: every interactive element must have a programmatic name, roles and parent-child relationships must be valid, and content must not be hidden from the accessibility tree while remaining interactive.
The takeaway: if your team has been investing in semantic HTML and proper ARIA labeling to serve people with disabilities, that work directly translates to agentic readiness. It's the same journey, seen from a new angle.
2. Layout stability (CLS) — why shifting pages break agent tasks
Cumulative Layout Shift (CLS) has been a Core Web Vital since 2020, measuring how much page content moves while it's loading. It now surfaces in the Agentic Browsing category for a specific reason: shifting layouts aren't just disorienting for people — they're a functional hazard for agents.
When an AI agent identifies a button and the page shifts before it can interact, the agent either triggers the wrong action or fails entirely. For agents completing tasks on someone's behalf — bookings, form submissions, purchases — that's not a minor inconvenience. It's a task failure.
Common culprits are images without set dimensions, fonts that load after the page renders, and content injected above the fold by third-party scripts. The Lighthouse Performance audit and Google Search Console's Core Web Vitals report both surface these issues. If your team hasn't addressed CLS yet, this is a good moment.
3. llms.txt — a new convention worth knowing
Alongside robots.txt (for search crawlers) and sitemap.xml (for indexing), there's now a third convention to understand: llms.txt. Placed at the root of your domain — for example, https://yourdomain.com/llms.txt — this plain Markdown file gives large language models (LLMs) and AI agents a concise, structured summary of your site's purpose and key content.
Lighthouse checks for this file's presence. If it returns a 404, the audit is marked as not applicable — the file is optional for now, not a requirement. If your server throws an error when it's requested, that's flagged.
The llms.txt convention is gaining traction, but most sites don't have it yet, and that's completely normal. Creating a basic version takes under an hour and requires no technical infrastructure beyond a text file at your domain root. It's the lowest-effort, highest-signal action available right now for teams that want to move early.
4. WebMCP — the emerging standard to watch, not panic about
Web Model Context Protocol (WebMCP) is an experimental browser API that lets websites explicitly expose their capabilities to AI agents. Instead of asking an agent to guess what a button does from its context, WebMCP tells it directly — through machine-readable definitions attached to forms and interactive elements.
There are two ways to register tools: a declarative approach using toolname and tooldescription attributes on HTML <form> elements, and an imperative JavaScript approach via navigator.modelContext.registerTool for more dynamic registrations.
The standard is still actively being developed. Most sites will fail this check, and Google expects that. The right response isn't to scramble — it's to inventory your key forms and interactions now (demos, signups, checkouts, contact flows) so your team is ready when the spec matures enough to act on. Monitor, don't rush.
Why this matters beyond the developer conversation
The Agentic Browsing category is a technical update, but its implications run much wider.
For e-commerce and financial services teams, AI shopping agents and financial assistants are already active. When a person delegates a task to an AI agent — finding a product, comparing plans, completing a checkout — that agent browses on their behalf. Sites with unlabeled forms, unstable layouts, and no machine-readable structure are harder to interact with. That friction has a direct conversion cost, not just a user experience one.
For SaaS and B2B technology companies, enterprise buyers increasingly use AI-powered evaluation tools to assess vendors before a human ever gets involved. A site that's structured, labeled, and stable signals technical maturity and trustworthiness. The accessibility tree is, in this context, a first impression for machines.
The connection to compliance is equally direct. The European Accessibility Act (EAA), in force since June 2025, pushed organizations across the EU to rethink their digital surfaces — and required them to meet WCAG 2.2 Level AA as the technical baseline. The Agentic Browsing category points in the same direction. Accessible websites are agentically ready websites. The work is the same.
How To Run The Audit In Chrome
Open Lighthouse In DevTools
When the Agentic Browsing category is available in your version of Chrome or Lighthouse:
Open the page you want to test.
Open Chrome DevTools (F12 or right‑click → Inspect).
Navigate to the Lighthouse panel.
In some experimental builds you may need Chrome Canary or a feature flag to see new categories. If you do not see an Agentic Browsing category, the feature is likely not exposed in your build yet.
Enable The Agentic Browsing Category
Within the Lighthouse panel you typically choose which categories to run. When Agentic Browsing is present, enable that checkbox alongside Performance, Accessibility, SEO, and others, then:
Choose the device type (Mobile or Desktop), since layout and behavior can differ
Optionally enable throttling for more realistic conditions
Click “Analyze page load”
The audit will run a fresh navigation of the page under test with the Agentic Browsing checks included.
Review Pass Ratios And Per‑Check Results
When the report completes, you should see:
An overall Agentic Browsing score or summary indicator
A list of passed checks that confirm the page is agent‑friendly in specific ways
A list of failed or “not applicable” checks, each with details and sometimes code snippets
To reproduce results more consistently, keep conditions stable:
Use the same URL and query parameters
Disable A/B tests or random content where possible
Run audits in the same Chrome version with the same Lighthouse settings
Remember that any CLS or timing variance can shift scores slightly between runs.
How To Interpret The Results
Which Failures Matter Most Now
Not all failures are equal in terms of current business impact. Prioritize:
Accessibility tree health issues, because they affect assistive tech and current Lighthouse Accessibility scores
Layout stability (CLS and similar) because they are part of Core Web Vitals and already a performance focus
Critical interaction issues where buttons, forms, or navigation are not consistently discoverable or clickable
Lower‑priority, experimental checks (such as missing llms.txt or WebMCP manifest) matter more for future‑looking preparedness than for today’s traffic or rankings.
What is next?
Accessibility has sometimes been framed as a compliance obligation — something to address because a regulation demands it. The Agentic Browsing category reframes that entirely. When AI agents use the same structural map that assistive technologies rely on, accessibility work becomes infrastructure for the modern web, not a box to tick.
Teams that have built accessible digital experiences aren't just ahead on EAA compliance. They're ahead on the next era of how the web works — and those managing accessibility continuously through a digital accessibility platform are best placed to stay there.
Sources: Lighthouse Agentic Browsing Scoring, Chrome for Developers (May 2026) · Registered WebMCP Tools · llms.txt audit · Build agent-friendly websites, web.dev
Editorial Board
That gap between what you're accountable for and what you can actually see is where risk lives. A digital accessibility platform closes it: not with another audit, but with a governance capability your team operates every day.
News
Editorial Board
In May 2026, Accessiway analysed 17 pages across 16 ATX Prime companies offering digital services, including banking platforms, telecoms, booking systems and energy portals.
News
Editorial Board
The GDPR guards how their data gets handled. The EAA guards whether they can use the thing at all. Most companies have bought solid protection for the first and left the second standing wide open.
Services