Website Compliance Audit — West Lakes Demolition

A. Completed

• Privacy Notice created with accurate description of actual data processing (enquiry form only, no analytics, no tracking)
• Cookie Policy created listing only the storage technologies actually used (local storage for consent, Google Fonts)
• Cookie consent banner updated with separate Accept and Reject buttons — refusal is as easy as acceptance
• Cookie banner no longer treats continued browsing as consent
• Cookie consent choice stored in local storage; preferences can be managed via Cookie Policy page
• Terms & Conditions created covering website use, services, enquiries, quotes, and governing law
• Disclaimer added to Terms page noting website information is general, not professional structural/engineering advice
• Enquiry form updated with privacy consent checkbox linked to Privacy Notice
• Enquiry form labels associated with inputs via htmlFor/id for screen reader accessibility
• Enquiry form required fields marked with visible asterisk and HTML required attribute
• Form error and success messages have ARIA roles (status/alert)
• Footer updated with links to Privacy Notice, Cookie Policy, Terms & Conditions, and Cookie Preferences
• Skip-to-content link added for keyboard navigation
• Privacy Notice and Terms pages use standard compliant language for retention periods, international transfers, company registration, payment terms, and cancellation — no placeholders remain
• Sitemap.xml updated with new legal pages
• No exposed API keys or secrets in frontend code — form submissions go through authenticated SDK
• No AI chatbot present — no AI safety layer required
• No analytics, advertising, or tracking scripts present — nothing to gate behind consent
• No payment systems, booking systems, maps, video embeds, or social media embeds present

B. Needs Client Confirmation

The following items are optional enhancements. All legal pages are complete and publishable without them.

• Registered office address

  The Terms page currently states company registration details are available on request. If you would like to display the registered office address publicly, provide it and it can be added to the Terms page and the footer NAP block.
• Public liability insurance details

  Recommended for transparency. Confirm the public liability insurance cover amount and insurer name if you wish to display it.

C. Not Applicable

• AI chatbot disclosures — no chatbot exists on this website
• AI safety handling (self-harm, medical, dangerous instructions) — no AI chatbot exists
• Newsletter / marketing consent — no newsletter or marketing signup exists
• Google Analytics consent gating — no Google Analytics is used
• Meta Pixel / advertising consent — no advertising pixels are used
• Payment system compliance — no online payments are processed
• Booking system terms — no online booking system exists
• Maps privacy (Google Maps embed) — no map embeds are used (the Contact page uses a static SVG)
• Video embed privacy — no YouTube or video embeds are used
• Social media embed privacy — no social media embeds are used
• Customer database — no customer database is accessible from the marketing site
• Login / account functionality — auth pages exist in the codebase but are not used on the public marketing site

D. Recommended Future Improvements

• Add the registered office address to the footer NAP block and to the LocalBusiness schema in index.html if you wish to display it publicly
• Add the company registration number to the Terms page if you wish to display it publicly
• Consider adding a physical address to the Contact page if the business has one clients can visit
• Review colour contrast on small text elements (white/45 opacity on dark backgrounds) — some labels may not meet WCAG AA contrast ratio of 4.5:1
• Consider self-hosting Google Fonts to eliminate the request to Google's servers and the associated IP address disclosure
• Submit the updated sitemap to Google Search Console once the changes are published
• Review and update all legal pages if the business adds analytics, marketing, payments, or any new data collection in the future
• Consider adding a 'Last reviewed' date to legal pages and setting a review schedule (e.g. annually)