Plain-English summaries of changes to data protection, cookie, accessibility and security rules, and what to do about each one. Always check the official source before acting.
low impactPrivacy policy··In effect from 30 September 2026
The ICO has become the Information Commission
Under the Data (Use and Access) Act 2025, the functions of the Information Commissioner's Office transferred to a new body, the Information Commission, on 30 September 2026. Your rights to complain to the regulator are unchanged.
What to do: Check the regulator's name and complaint details in your privacy policy are still correct, and update them at your next review.
Cyber Security and Resilience Bill extends UK cyber rules
The Cyber Security and Resilience Bill updates the NIS Regulations, bringing more digital and managed service providers into scope and strengthening incident reporting.
What to do: If you provide managed IT or digital services, follow the Bill's progress and make sure basic controls (patching, HTTPS, security headers, MFA) are in place.
high impactAccessibility··In effect from 28 June 2025
European Accessibility Act now applies to UK businesses selling into the EU
Since 28 June 2025 the European Accessibility Act requires many consumer-facing digital services sold in the EU, including e-commerce sites, to be accessible. UK businesses that sell to EU customers can be in scope.
What to do: If you sell to EU consumers, test your site against WCAG 2.1 AA (EN 301 549) and publish an accessibility statement.
Data (Use and Access) Act 2025: cookie and marketing fines raised to UK GDPR levels
The Act lifts the maximum PECR penalty from £500,000 to the UK GDPR level (up to £17.5 million or 4% of global turnover). Cookie and e-marketing breaches now carry the same risk as data protection breaches.
What to do: Check that non-essential cookies and trackers do not load before consent, and that marketing emails have a valid opt-in and unsubscribe.
New consent exemptions for low-risk analytics and functional cookies
The Data (Use and Access) Act 2025 allows some cookies to be set without prior consent, such as those for statistical analytics to improve a site and for remembering user preferences, provided users get clear information and a simple way to object. Advertising and cross-site tracking still need consent.
What to do: Do not drop your consent banner yet. Review which cookies could qualify, confirm the exemption is in force and follow the regulator's guidance before relying on it, and add a clear opt-out for them.
Data protection complaints: organisations must have a complaints process
Under the Data (Use and Access) Act 2025, controllers must make it easy for people to complain about how their personal data is used (for example an electronic complaint form), acknowledge complaints within 30 days and respond without undue delay.
What to do: Add a data protection complaints route to your privacy policy and website, and make sure someone is responsible for answering it.
Cyber Essentials: keep up with the latest requirements
The NCSC updates the Cyber Essentials requirements periodically. Certification is often required for public sector contracts and is a good baseline for any business website.
What to do: Check your certification renewal date against the current requirements on the NCSC site.
The ICO has published guidance on models where users either consent to personalised advertising or pay for access. These can be lawful, but only if the choice is genuinely free, fairly priced and clearly explained.
What to do: If you run a paywall or ad-free option tied to cookie consent, review it against the ICO guidance.
ICO reviewing cookie compliance on the UK's most visited websites
The ICO has said it is assessing cookie banners on the UK's top 1,000 websites and will act where sites set advertising cookies without valid consent or make rejecting harder than accepting.
What to do: Make "Reject all" as prominent as "Accept all" on your banner, and confirm that no advertising cookies fire before a choice is made.
Public sector websites: accessibility statements and WCAG 2.2 AA
Public sector bodies must meet the Public Sector Bodies Accessibility Regulations, publish an accessibility statement and keep it up to date. GDS monitors sites against WCAG 2.2 AA.
What to do: If you build or run public sector sites, review the accessibility statement at least once a year and after major changes.
WCAG 2.2 adds nine success criteria to WCAG 2.1, including minimum target sizes, visible focus that is not hidden, accessible authentication and avoiding redundant data entry. The UK public sector is monitored against WCAG 2.2 AA.
What to do: Check that buttons and links are large enough to tap, focus outlines are not hidden behind sticky headers, and logins do not rely on memory tests.