{
	"title": "Web Sustainability Guidelines",
	"edition": "Group Note Draft",
	"lastModified": "2026-07-28",
	"category": [
		{
			"id": "1",
			"name": "Introduction"
		},
		{
			"id": "2",
			"name": "User Experience Design",
			"shortName": "UX Design",
			"guidelines": [
				{
					"id": "identify-assess-disclose-review-and-mitigate-sustainability-impacts",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#identify-assess-disclose-review-and-mitigate-sustainability-impacts",
					"guideline": "Identify, assess, disclose, review, and mitigate sustainability impacts",
					"subheading": "Assess and report the planet, people, and prosperity impacts of digital projects, and plan measurable reductions to the real-world effects of their activity.",
					"criteria": [
						{
							"title": "Impact analysis",
							"description": "Review the planet, people, and prosperity impacts of your project at the start and at regular intervals. Record the main issues you identify, where improvements are needed, and the progress you make. Reflect these findings in your public-facing governance documents and project reporting."
						},
						{
							"title": "External impact",
							"description": "Create a plan to reduce the non-digital environmental and social impacts of digital activities associated with your project. Include impacts from logistics and delivery emissions, infrastructure emissions, local health effects, and supply chain pressures. Use measurable actions to improve external planet, people, and prosperity outcomes."
						}
					],
					"tags": ["Accessibility", "Compatibility", "Hardware", "Ideation", "Networking", "Performance", "Privacy", "Reporting", "Research", "Social Equity", "Software"]
				},
				{
					"id": "understand-user-requirements-or-constraints",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#understand-user-requirements-or-constraints",
					"guideline": "Understand user requirements or constraints",
        			"subheading": "Identify and involve users and affected communities, and research their needs.",
					"criteria": [
						{
							"title": "Audience evaluation",
							"description": "Identify the primary and secondary users, and affected communities, for the project. Use research, testing, analytics, and reviews to understand their needs and the project's impact on them. Involve users throughout the project."
						}
					],
					"tags": ["Accessibility", "Compatibility", "Ideation", "KPIs", "Patterns", "Privacy", "Reporting", "Research", "Social Equity", "UI", "Usability"]
				},
				{
					"id": "integrate-sustainability-into-every-stage-of-the-ideation-process",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#integrate-sustainability-into-every-stage-of-the-ideation-process",
					"guideline": "Integrate sustainability into every stage of the ideation process",
					"subheading": "Design and review sustainable branding and experiences, involve users throughout the process, and reduce unnecessary development and environmental impact through early testing and environmentally aware design.",
					"criteria": [
						{
							"title": "Sustainable brand development",
							"description": "Optimize approved branding materials and assets to meet the organization's sustainability requirements before release and review them regularly after launch. Where brand guidelines exist, include information about the environmental impact of materials and assets, along with guidance for sustainable production, use, and disposal."
						},
						{
							"title": "Wireframes and prototypes",
							"description": "Use wireframes and rapid prototypes to test ideas early, build agreement quickly, reduce risk, and avoid unnecessary development work and resource use."
						},
						{
							"title": "Participation and testing",
							"description": "Use participatory design methods throughout the design process. Involve users in testing and iteration, and give communities opportunities to share their knowledge and experience to improve the product or service."
						},
						{
							"title": "Environmental ideation",
							"description": "Address planetary needs and environmental boundaries during the ideation phase. This can include creating non-user, non-human personas, such as animal- or planet-focused perspectives, and developing climate-specific user stories and sprints."
						}
					],
					"tags": ["Accessibility", "Content", "HTML", "Marketing", "Patterns", "Performance", "Privacy", "Social Equity", "UI", "Usability"]
				},
				{
					"id": "design-efficient-and-streamlined-user-journeys",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#design-efficient-and-streamlined-user-journeys",
					"guideline": "Design efficient and streamlined user journeys",
					"subheading": "Design clear, efficient journeys that help users complete tasks and find content with minimal effort.",
					"criteria": [
						{
							"title": "Efficient paths",
							"description": "Make tasks simple and efficient to complete. Help users understand what is required at the start of a task, reduce unnecessary choices, and show how long journeys are expected to take."
						},
						{
							"title": "Patterns for efficiency",
							"description": "Design user journeys that are clear and efficient. Use established design patterns that people already understand."
						},
						{
							"title": "Content discovery",
							"description": "Provide a human-readable sitemap, especially for large, complex, or legacy websites where navigation is not straightforward. Keep it regularly updated. Provide clear and accessible navigation and search features so users can quickly find the content or services they need. Use lightweight and efficient ways to help users discover new content and services, including news pages, updates, and changelogs."
						}
					],
					"tags": ["Accessibility", "Content", "HTML", "Marketing", "Patterns", "Performance", "Privacy", "Social Equity", "UI", "Usability"]
				},
				{
					"id": "design-to-assist-and-not-to-distract",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#design-to-assist-and-not-to-distract",
					"guideline": "Design to assist and not to distract",
					"subheading": "Give users control over notifications and focus, prioritize task-relevant content, and avoid designs that distract or unnecessarily extend engagement.",
					"criteria": [
						{
							"title": "Respect user attention",
							"description": "Ensure users can control when and how they receive information, while respecting their attention, focus, and mental effort."
						},
						{
							"title": "Distraction-free design",
							"description": "Show users information relevant to their current task and avoid unnecessary interruption and competing interface elements. Delay or collapse information not immediately needed, but keep it easy to find. Only show pop-ups, modal windows, or other disruptive interface elements when the user chooses to open them. Use decorative design only when it improves the user experience, and make optional assets removable or turned off by default. Do not remove information or functionality that may be important for accessibility, safety, or different user needs."
						},
						{
							"title": "Remove engagement traps",
							"description": "Avoid design patterns that engage users longer than necessary, such as infinite scroll or disabling standard browser controls and navigation features."
						}
					],
					"tags": ["Accessibility", "Assets", "Patterns", "UI", "Usability"]
				},
				{
					"id": "avoid-being-manipulative-or-deceptive",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#avoid-being-manipulative-or-deceptive",
					"guideline": "Avoid being manipulative or deceptive",
					"subheading": "Avoid deceptive patterns, clearly label ads, respect consent for tracking, and ensure search, sharing, and discoverability practices prioritize user needs over optimization or manipulation.",
					"criteria": [
						{
							"title": "Deceptive design patterns",
							"description": "Avoid deceptive design patterns that pressure or mislead users. This includes practices such as bait and switch, hidden fees, or fake scarcity."
						},
						{
							"title": "Advertisements",
							"description": "Clearly label advertisements and sponsored content. Deliver advertising in a lightweight and minimally disruptive way while enabling users to control the experience."
						},
						{
							"title": "Analytics and tracking",
							"description": "Remove unnecessary analytics and tracking, and respect user consent over tracking analytics."
						},
						{
							"title": "Search Engine Optimization",
							"description": "Optimize content for search and social sharing in ways that support user needs rather than manipulation. Do not misuse accessibility features, create low-quality content, or add unnecessary duplication only to influence search rankings."
						}
					],
					"tags": ["Accessibility", "Assets", "Compatibility", "JavaScript", "Patterns", "Privacy", "Security", "Social Equity", "UI", "Usability"]
				},
				{
					"id": "make-deliverables-understandable-and-reusable",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#make-deliverables-understandable-and-reusable",
					"guideline": "Make deliverables understandable and reusable",
					"subheading": "Create discoverable, maintainable, and reusable documentation and code resources that support long-term understanding, reuse, and sustainability.",
					"criteria": [
						{
							"title": "Deliverables reusability",
							"description": "Create documentation and other deliverables in reusable formats to reduce duplicated work and support long-term sustainability."
						},
						{
							"title": "Deliverables documentation",
							"description": "Document functionality and technical requirements in clear and easy-to-maintain resources. Keep documentation updated over time and provide guidance for replacing or retiring outdated information."
						},
						{
							"title": "Deliverables readability",
							"description": "Provide developers with access to source code and code comments so they can easily understand, maintain, and reuse the code."
						}
					],
					"tags": ["Accessibility", "Assets", "Content", "Education", "Patterns", "Software"]
				},
				{
					"id": "use-a-design-system-for-interface-consistency",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#use-a-design-system-for-interface-consistency",
					"guideline": "Use a design system for interface consistency",
					"subheading": "Use design systems and established patterns to ensure consistent, efficient, and sustainable interfaces through reusable components and clear maintenance practices.",
					"criteria": [
						{
							"title": "Design system",
							"description": "Use a design system for large projects or those with many contributors to improve consistency, performance, and long-term sustainability. Use reusable components based on web standards, load only the components needed for each page or feature, and maintain the system through clear ownership, versioning, and updated documentation. Follow established design patterns and conventions."
						}
					],
					"tags": ["Accessibility", "Assets", "CSS", "Education", "Patterns", "Strategy", "UI", "Usability"]
				},
				{
					"id": "optimize-media-to-reduce-resource-use",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#optimize-media-to-reduce-resource-use",
					"guideline": "Optimize media to reduce resource use",
					"subheading": "Include media only when it supports user needs. Manage, optimize, and load media efficiently. Ensure users have control over playback and data use.",
					"criteria": [
						{
							"title": "Need for media",
							"description": "Only include media when it supports user experience or improves understanding and keep the number of media items to a minimum."
						},
						{
							"title": "Optimized media",
							"description": "Resize, optimize, and compress media for different screen sizes, devices, and user needs. Use widely supported, efficient formats that enable native presentation or playback where possible. Avoid unnecessary custom or non-native media players. Use hardware-accelerated playback when available and compatible with security requirements."
						},
						{
							"title": "Lazy loading",
							"description": "Incorporate lazy and/or deferred loading from the start by identifying which media elements are required immediately and which should load only on user interaction. Load large or data-intensive media only when needed, using a non-functional static facade or placeholder to defer loading until user request or interaction."
						},
						{
							"title": "User-controlled media",
							"description": "Disable autoplay for audio, video, and other media by default. Ensure users can control playback and resolution. Inform users about media length, format, and expected data use. Provide the option to disable data-intensive media or offer lower-bandwidth alternatives."
						},
						{
							"title": "Media management and use",
							"description": "Create a media management and usage policy. Include guidance on compression, rendering performance, file formats, data retention, storage, review, and deletion."
						}
					],
					"example": "<picture> \n  <source type=\"image/avif\" srcset=\"image.avif\">\n  <source type=\"image/webp\" srcset=\"image.webp\">\n  <img width=\"100px\" height=\"100px\" src=\"image.jpg\" alt=\"\" loading=\"lazy\"/>\n</picture>",
					"tags": ["Accessibility", "Assets", "Content", "HTML", "Performance", "Software", "UI", "Usability"]
				},
				{
					"id": "ensure-animation-is-proportionate-and-easy-to-control",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#ensure-animation-is-proportionate-and-easy-to-control",
					"guideline": "Ensure animation is proportionate and easy to control",
					"subheading": "Use animation sparingly and efficiently, only when it supports understanding, while limiting performance impact and giving users control over motion.",
					"criteria": [
						{
							"title": "Need for animation",
							"description": "Use animation only when it supports the user experience or helps users understand content or actions."
						},
						{
							"title": "Avoiding overburdening",
							"description": "Limit the number and frequency of animations to reduce distraction, minimize resource use, and maintain expected device performance. Set a maximum number of replays or iterations."
						},
						{
							"title": "Control animation",
							"description": "Let users start, pause, stop, or control animated and moving content."
						},
						{
							"title": "Efficient animation",
							"description": "Keep interactive and animated content as lightweight as possible. Reduce rendering cost by accounting for formats, lengths, complexity, dimensions, quality, tooling, and implementation approach. Where multiple approaches are available, choose browser- or platform-native animation capabilities and minimize main-thread or layout-intensive work."
						}
					],
					"example": "@media (prefers-reduced-motion: reduce) {\r\n\tbody *,\r\n\tbody *::before,\r\n\tbody *::after {\r\n\t\tanimation-delay: -1ms !important;\r\n\t\tanimation-duration: 1ms !important;\r\n\t\tanimation-iteration-count: 1 !important;\r\n\t\tbackground-attachment: initial !important;\r\n\t\ttransition-duration: 1ms !important;\r\n\t\ttransition-delay: -1ms !important;\r\n\t\tscroll-behavior: auto !important;\r\n\t}\r\n}",
					"tags": ["Accessibility", "CSS", "JavaScript", "Performance", "UI", "Usability"]
				},
				{
					"id": "use-optimized-web-typography",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#use-optimized-web-typography",
					"guideline": "Use optimized web typography",
					"subheading": "Use font strategies that minimize downloads and complexity while supporting required languages and dynamic content.",
					"criteria": [
						{
							"title": "Pre-installed typefaces",
							"description": "Use system fonts or other pre-installed fonts to reduce font downloads and improve performance."
						},
						{
							"title": "Web font optimization",
							"description": "Limit the number and complexity of downloaded fonts. When using variable fonts, restrict supported axes and ranges to only those required by the project to reduce file size. Use the most performant font formats available and provide suitable fallback fonts to maintain readability and performance during font loading or when custom fonts cannot be loaded."
						},
						{
							"title": "Web font subsetting",
							"description": "Remove unused font styles, weights, and character sets. Subset fonts based on explicitly supported languages, scripts, and Unicode ranges required by the project. Where you have full control over all input and output, subset fonts to include only the relevant Unicode ranges or character sets. In cases involving dynamic content or user-generated input, provide broader script coverage and use Incremental Font Transfer (IFT) to load required font segments on demand."
						}
					],
					"example": "font-family: -apple-system, BlinkMacSystemFont, avenir next, avenir, segoe ui, helvetica neue, helvetica, Cantarell, Ubuntu, roboto, noto, arial, sans-serif;",
					"tags": ["Accessibility", "CSS", "Performance", "UI", "Usability"]
				},
				{
					"id": "avoid-unwanted-notifications",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#avoid-unwanted-notifications",
					"guideline": "Avoid unwanted notifications",
					"subheading": "Send only user-requested notifications and provide clear, accessible controls for managing preferences, opt-in, and account and contact settings.",
					"criteria": [
						{
							"title": "Need for notification",
							"description": "Only send notifications that match user preferences or that the user has explicitly requested. Avoid unnecessary emails, SMS messages, and push notifications. Give users clear control over each notification type."
						},
						{
							"title": "Notification settings",
							"description": "Let users manage their notification and messaging settings easily. Make unsubscribe, logout, and account closure options visible and accessible. Turn off optional notifications by default and enable them only after user opt-in."
						}
					],
					"tags": ["Accessibility", "JavaScript", "Privacy", "UI", "Usability"]
				},
				{
					"id": "reduce-the-impact-of-downloadable-and-physical-documents",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#reduce-the-impact-of-downloadable-and-physical-documents",
					"guideline": "Reduce the impact of downloadable and physical documents",
					"subheading": "Reduce paper use through digital-first workflows, optimize and reuse accessible downloadable documents, and provide clear, user-controlled document previews and formats.",
					"criteria": [
						{
							"title": "Printed documents",
							"description": "Design workflows to reduce the need for paper documents. When paper use is necessary, reduce paper use through efficient print layouts and minimal page counts. Include print style sheets and test them with real content. Encourage the use of digital formats instead of paper storage and archiving."
						},
						{
							"title": "Optimized documents",
							"description": "Optimize and compress downloadable documents, provide them in accessible formats that suit different user needs, and choose open, widely supported formats (such as HTML) over proprietary file formats."
						},
						{
							"title": "Optimized delivery",
							"description": "Avoid duplicating work. When a document is reused, generate and store it once on the server so it can be reused efficiently, preferably on a cookie-free domain."
						},
						{
							"title": "Labels and choice",
							"description": "Show users the document name, format, size, and a short summary before download. Let users choose the most suitable format and language. Avoid embedding documents directly in pages; instead provide download or browser-view links."
						}
					],
					"tags": ["Accessibility", "Assets", "Compatibility", "Content", "E-Waste", "Hardware", "Performance", "Software", "UI", "Usability"]
				},
				{
					"id": "involve-users-early-in-the-project",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#involve-users-early-in-the-project",
					"guideline": "Involve users early in the project",
					"subheading": "Define and validate prototypes and interface components through user testing to ensure they work effectively in real-world use cases and across diverse user needs.",
					"criteria": [
						{
							"title": "Early user testing",
							"description": "Create defined processes for prototyping and testing new features and interface components. Validate them with representative users to ensure they work in real-world conditions and across different needs."
						}
					],
					"tags": ["Accessibility", "Education", "Governance", "Ideation", "Research", "Social Equity", "Strategy", "UI", "Usability"]
				},
				{
					"id": "audit-and-test-for-bugs-or-issues-requiring-resolution",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#audit-and-test-for-bugs-or-issues-requiring-resolution",
					"guideline": "Audit and test for bugs or issues requiring resolution",
					"subheading": "Regularly audit for issues or problems, running tests at regular intervals in both simulated and real-world scenarios to ensure stability of the project.",
					"criteria": [
						{
							"title": "Ongoing evaluation",
							"description": "Evaluate current user experience and check the codebase for bugs, identify performance issues, and account for accessibility, sustainability, or security problems at appropriate regular intervals, such as every month or quarter."
						},
						{
							"title": "Automated tests",
							"description": "Maintain an automated test suite that covers critical functionality and run it consistently during builds and releases to catch regressions early."
						},
						{
							"title": "Performance testing",
							"description": "Identify and resolve bottlenecks or issues in the underlying code or infrastructure which could impact sustainability and performance to encourage a smooth, frictionless user journey. Account for both simulated and real-world metrics. Monitor performance across every release cycle using appropriate tooling or through research and auditing."
						}
					],
					"tags": ["Accessibility", "Compatibility", "KPIs", "Performance", "Privacy", "Reporting", "Research", "Security", "Social Equity", "Software", "Strategy", "UI", "Usability"]
				},
				{
					"id": "validate-usability-through-testing-and-real-world-usage",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#validate-usability-through-testing-and-real-world-usage",
					"guideline": "Validate usability through testing and real-world usage",
					"subheading": "Monitor user feedback and real usage to evaluate feature effectiveness, and use usability testing and user research to guide ongoing improvements.",
					"criteria": [
						{
							"title": "Usage changes",
							"description": "Monitor user feedback, adoption, and churn for each feature. Use these insights to guide updates and future releases."
						},
						{
							"title": "Usability testing",
							"description": "Use usability testing, real user metrics, and user interviews throughout product development. Measure the impact of findings and check whether released features meet user needs and internal goals."
						}
					],
					"tags": ["Accessibility", "Education", "Governance", "Ideation", "KPIs", "Research", "Social Equity", "Strategy", "UI", "Usability"]
				},
				{
					"id": "provide-cross-platform-compatibility-support",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#provide-cross-platform-compatibility-support",
					"guideline": "Provide cross-platform compatibility support",
					"subheading": "Document compatibility, avoid unnecessary obsolescence, and test across devices, systems, and network conditions.",
					"criteria": [
						{
							"title": "Compatibility documentation",
							"description": "Document supported devices, operating systems, and browsers, including version ranges. Review and update it regularly to reflect current releases."
						},
						{
							"title": "Maintaining compatibility",
							"description": "Avoid planned obsolescence. Keep compatibility for as long as reasonably possible. Clearly explain whether updates are major changes that may affect performance or smaller updates that fix issues or improve security."
						},
						{
							"title": "User constraints",
							"description": "Test for a wide range of user conditions, including slow, restricted or unstable connections, Virtual Private Network (VPN) use, different operating systems and browsers, and older or low-performance devices."
						}
					],
					"tags": ["Accessibility", "Compatibility", "Ideation", "KPIs", "Patterns", "Reporting", "Research", "Security", "Social Equity", "Software", "Strategy", "UI", "Usability"]
				}
			]
		},
		{
			"id": "3",
			"name": "Web Development",
			"shortName": "Web Development",
			"guidelines": [
				{
					"id": "set-goals-based-on-performance-and-energy-impact",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#set-goals-based-on-performance-and-energy-impact",
					"guideline": "Set goals based on performance and energy impact",
					"subheading": "Define performance and environmental targets, and design content with awareness of the relative energy and processing cost.",
					"criteria": [
						{
							"title": "Performance goals",
							"description": "Set clear performance and environmental goals for the project, including limits on requests, elements rendered, or other measurable resource use."
						},
						{
							"title": "Energy intensity",
							"description": "Prioritize lower-impact design choices, paying attention to measurable differences in energy use across components. Complex structure, styling, and script-driven experiences along with graphics-heavy and media-rich rendering increase the computational complexity of rendering. Use more intensive approaches only where these add clear value."
						}
					],
					"tags": ["KPIs", "Networking", "Performance", "Research", "Social Equity", "Strategy"]
				},
				{
					"id": "minify-and-remove-unused-code",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#minify-and-remove-unused-code",
					"guideline": "Minify and remove unused code",
					"subheading": "Minify code and data, and remove unused characters to reduce file size and improve loading efficiency and maintainability.",
					"criteria": [
						{
							"title": "Minified code",
							"description": "Minify code and data files by removing unnecessary whitespace, comments, attributes, and non-essential characters. Apply this consistently across the system to reduce file size and improve loading efficiency. This helps to reduce cumulative data transfer and processing overhead at scale, improving resource efficiency and reducing energy consumption. Ensure that minification does not introduce any errors."
						},
						{
							"title": "Remove redundancy",
							"description": "Identify and remove unused or dead code, especially in CSS and JavaScript."
						}
					],
					"example": "!function(e,t){\"use strict\";\"object\"==typeof module&&\"object\"==typeof module.exports?module.exports=e.document?t(e,!0):function(e){if(!e.document)throw new Error(\"jQuery requires a window with a document\");return t(e)}:t(e)}(\"undefined\"!=typeof window?window:this,function(g,e){\"use strict\";var t=[],r=Object.getPrototypeOf,s=t.slice,v=t.flat?function(e){return t.flat.call(e)}:function(e){return t.concat.apply([],e)},u=t.push,i=t.indexOf",
					"tags": ["Accessibility", "CSS", "HTML", "JavaScript", "Performance"]
				},
				{
					"id": "modularize-bandwidth-heavy-components",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#modularize-bandwidth-heavy-components",
					"guideline": "Modularize bandwidth-heavy components",
					"subheading": "Split large components into smaller, on-demand modules to improve loading efficiency while balancing maintainability and caching performance.",
					"criteria": [
						{
							"title": "Code splitting",
							"description": "Split large or bandwidth-heavy components into smaller modules that load only when needed. Avoid excessive splitting, as it can increase overhead, reduce caching efficiency, and make code harder to maintain."
						}
					],
					"example": "link.addEventListener(\"click\", (e) => {\r\n\te.preventDefault();\r\n\timport(\"\/modules\/my-module.js\")\r\n\t.then((module) => {\r\n\t\t\/* Do something *\/\r\n\t})\r\n\t.catch((err) => {\r\n\t\tconsole.error(err.message);\r\n\t});});",
					"tags": ["CSS", "JavaScript", "Performance"]
				},
				{
					"id": "avoid-redundancy-and-duplication-in-code",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#avoid-redundancy-and-duplication-in-code",
					"guideline": "Avoid redundancy and duplication in code",
					"subheading": "Reduce code duplication through refactoring and reuse, ensure maintainability, and favor evolving existing solutions over rebuilding them.",
					"criteria": [
						{
							"title": "Remove or simplify",
							"description": "Refactor code to reduce duplication and redundancy by improving structure, consolidating repeated logic, and encouraging reuse."
						},
						{
							"title": "Iteration over recreation",
							"description": "Prioritize improving and extending existing user-facing solutions over rebuilding them from scratch. Only replace an existing solution when doing so provides clear benefits to user experience, performance, scalability, or maintainability."
						},
						{
							"title": "Organize code arrangement",
							"description": "Apply DRY (Don't Repeat Yourself) principles to CSS and JavaScript where they improve maintainability. Ensure that efforts to reduce duplication do not increase complexity, introduce unnecessary dependencies, or adversely affect performance."
						}
					],
					"example": ".opinions_box {\r\n\tmargin: 0 0 8px 0;\r\n\ttext-align: center;\r\n\t&__view-more {\r\n\t\ttext-decoration: underline;\r\n\t}\r\n\t&__text-input {\r\n\t\tborder: 1px solid #ccc;\r\n\t}\r\n\t&--is-inactive {\r\n\t\tcolor: gray;\r\n\t}\r\n}",
					"tags": ["Accessibility", "CSS", "JavaScript", "Patterns", "Performance"]
				},
				{
					"id": "treat-third-parties-the-same-as-first-parties",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#treat-third-parties-the-same-as-first-parties",
					"guideline": "Treat third parties the same as first parties",
					"subheading": "Minimize and carefully manage third-party services by using lightweight, user-controlled integrations that are loaded only when needed.",
					"criteria": [
						{
							"title": "Assess and reduce",
							"description": "Review third-party content and/or services early in the design or ideation process, including plugins, widgets, feeds, maps, carousels, tracking scripts, and similar components. Use as few as possible, preferring lightweight options to reduce overall environmental impact, including GHG Protocol Scope 3 emissions. Ensure third-party providers enforce the same compliance, security, privacy, data retention limits, data deletion policies, and mandatory security update standards as the first party. Account for long-term dependency risks when selecting third-party services, including data portability and transition options."
						},
						{
							"title": "Third-party implementation",
							"description": "Load third-party content only when the user interacts with it. Offer simple alternatives, such as linking to a form instead of embedding a widget."
						},
						{
							"title": "Self-hosting",
							"description": "Serve assets such as content, icons, fonts, scripts, and widgets from infrastructure you control where practical, rather than embedding or depending on third-party services for their storage or delivery. This reduces dependency on external systems, improves reliability, and can reduce unnecessary network requests."
						},
						{
							"title": "Third-party preferences",
							"description": "Respect user preferences around third-party content and services. Provide clear controls to disable or opt out of non-essential third-party features."
						}
					],
					"example": "<iframe src=\"https:\/\/example.com\" loading=\"lazy\" width=\"600\" height=\"400\"><\/iframe>",
					"tags": ["Accessibility", "JavaScript", "Performance", "Privacy", "Security", "Software", "UI", "Usability"]
				},
				{
					"id": "ensure-code-follows-good-semantic-practices",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#ensure-code-follows-good-semantic-practices",
					"guideline": "Ensure code follows good semantic practices",
					"subheading": "Use standards-compliant HTML and web platform features, and avoid unnecessary complexity or non-standard code.",
					"criteria": [
						{
							"title": "Semantic code",
							"description": "Use valid and standards-compliant markup."
						},
						{
							"title": "Optional features",
							"description": "Remove optional HTML elements, attribute quotes, and default attributes if doing so does not negatively impact accessibility, readability, functionality, or performance. Include them when they improve accessibility, maintain clarity without compromising performance, or ensure consistent browser rendering."
						},
						{
							"title": "Avoid non-standard code",
							"description": "Avoid deprecated, proprietary, or non-standard technologies unless there is a clear, justified need such as legacy compatibility or accessibility. Use polyfills only when necessary and review them regularly for removal."
						},
						{
							"title": "Custom code",
							"description": "Use standard HTML elements, attributes, features, and APIs wherever they meet the requirement. Use custom elements, Web Components, or custom functionality only when built-in web platform capabilities cannot meet the need or when building reusable design system components."
						}
					],
					"example": "<button onclick=\"window.dialog.showModal()\">open dialog</button>\r\n<dialog id=\"dialog\">\r\n\t<p>I'm a dialog.</p>\r\n\t<form method=\"dialog\">\r\n\t\t<button>Close</button>\r\n\t</form>\r\n</dialog>",
					"tags": ["Accessibility", "Compatibility", "Content", "HTML", "Security", "Social Equity", "Usability"]
				},
				{
					"id": "defer-the-loading-of-non-critical-resources",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#defer-the-loading-of-non-critical-resources",
					"guideline": "Defer the loading of non-critical resources",
					"subheading": "Load non-essential assets asynchronously or with prioritization to improve rendering performance and avoid visual issues.",
					"criteria": [
						{
							"title": "Asynchronous code",
							"description": "Load non-essential external assets asynchronously or defer them to avoid rendering issues such as Flash Of Unstyled Content (FOUC), Flash of Invisible Text (FOIT), or Flash of Faux Text (FOFT)."
						},
						{
							"title": "Optimized loading",
							"description": "Use resource and priority hints to improve loading performance when multiple assets compete for bandwidth or rendering order."
						}
					],
					"example": "<link rel=\"prefetch\" href=\"\/articles\/\" as=\"document\">",
					"tags": ["Accessibility", "Assets", "CSS", "JavaScript", "Performance"]
				},
				{
					"id": "structure-metadata-for-machine-readability",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#structure-metadata-for-machine-readability",
					"guideline": "Structure metadata for machine readability",
					"subheading": "Include essential document metadata and structured data to improve usability, accessibility, and machine readability.",
					"criteria": [
						{
							"title": "Required elements",
							"description": "Include a required title element and add optional HTML head elements where they improve usability, accessibility, or performance."
						},
						{
							"title": "Meta tags",
							"description": "Include relevant meta tags that are widely used by browsers, search engines, and other user agents."
						},
						{
							"title": "Structured data",
							"description": "Use structured data, such as schema.org, implemented with JSON-LD, microdata, RDFa, or microformats, to enable consistent interpretation and reuse of content by both humans and machines across tools and services."
						}
					],
					"example": "<html>\r\n\t<head>\r\n\t\t<title>Example: A website about Examples<\/title>\r\n\t\t<script type=\"application\/ld+json\">\r\n\t\t{\r\n\t\t\t\"@context\" : \"https:\/\/schema.org\",\r\n\t\t\t\"@type\" : \"WebSite\",\r\n\t\t\t\"name\" : \"Example\",\r\n\t\t\t\"url\" : \"https:\/\/example.com\/\"\r\n\t\t}\r\n\t<\/script>\r\n\t<\/head>\r\n\t<body>\r\n\t<\/body>\r\n<\/html>",
					"tags": ["Accessibility", "AI", "HTML", "Marketing", "Usability"]
				},
				{
					"id": "use-media-queries-that-support-sustainability-goals",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#use-media-queries-that-support-sustainability-goals",
					"guideline": "Use media queries that support sustainability goals",
					"subheading": "Support user preferences via media queries for color, motion, contrast, data use, and related settings to improve accessibility and efficiency.",
					"criteria": [
						{
							"title": "Media and preference queries",
							"description": "Accommodate common user preferences using CSS media queries such as prefers-color-scheme. Account for additional preference queries, including monochrome, prefers-contrast, prefers-reduced-data, prefers-reduced-transparency, and prefers-reduced-motion where these will benefit your users. Use print and scripting media queries where they can improve efficiency or sustainability."
						}
					],
					"example": "@media (prefers-color-scheme: dark) {\r\n\t\/* wants dark mode *\/\r\n}\r\n@media (prefers-color-scheme: light) {\r\n\t\/* wants light mode *\/\r\n}",
					"tags": ["Accessibility", "Assets", "CSS", "UI", "Usability"]
				},
				{
					"id": "ensure-layouts-work-for-different-devices-and-requirements",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#ensure-layouts-work-for-different-devices-and-requirements",
					"guideline": "Ensure layouts work for different devices and requirements",
					"subheading": "Use responsive, progressively enhanced, and carbon-aware design to ensure accessible, adaptable functionality across devices and interaction methods while managing resource use.",
					"criteria": [
						{
							"title": "Device-adaptable",
							"description": "Use responsive and adaptive design so the product works across devices and screen sizes such as phones, tablets, laptops, desktops, TVs, and emerging platforms. Ensure the project still functions when certain features or technologies are not supported."
						},
						{
							"title": "Progressive enhancement",
							"description": "Use progressive enhancement to enhance sustainability by starting with a baseline of HTML, then progressively improving the user experience without relying on style or interaction for core functionality, ensuring a robust and resilient project."
						},
						{
							"title": "Carbon-aware design",
							"description": "Use carbon-aware design to reduce energy use when electricity demand or system load is high. Use situational design to replace, reduce, or disable high-impact features for lower-impact alternatives. Automated thresholds may also adjust or disable non-essential features, provided changes remain transparent. Clearly communicate what changed and why, and allow users to restore full functionality where possible."
						},
						{
							"title": "Alternative browsing",
							"description": "Support sustainable non-visual and indirect interaction methods such as assistive technologies, voice input, QR codes, reader view (browser, application, or RSS), and connected devices."
						}
					],
					"example": "@media screen and (min-width: 600px) {\r\n\tbody {\r\n\t\tcolor: red;\r\n\t}\r\n}",
					"tags": ["Accessibility", "AI", "Compatibility", "Content", "CSS", "Performance", "Social Equity", "UI", "Usability"]
				},
				{
					"id": "use-sustainable-javascript-and-apis",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#use-sustainable-javascript-and-apis",
					"guideline": "Use sustainable JavaScript and APIs",
					"subheading": "Write efficient JavaScript and use APIs that minimize processing, data use, and energy consumption.",
					"criteria": [
						{
							"title": "Sustainable JavaScript",
							"description": "Write JavaScript that supports long-term application performance by reducing unnecessary calculations, limiting DOM updates, and minimizing network requests."
						},
						{
							"title": "Energy-relevant APIs",
							"description": "Leverage JavaScript APIs, such as Compression Streams, Page Visibility, or Vibration, when they help reduce energy use or improve efficiency."
						},
						{
							"title": "API requests",
							"description": "Only call client-side or server-side APIs when needed. Ensure only data required for the task is included in requests and responses."
						}
					],
					"example": "const audio = document.querySelector(\"audio\");\r\n\/\/ Handle page visibility change:\r\n\/\/ - If the page is hidden, pause the video\r\n\/\/ - If the page is shown, play the video\r\ndocument.addEventListener(\"visibilitychange\", () => {\r\nif (document.hidden) {\r\n\taudio.pause();\r\n} else {\r\n\taudio.play();\r\n}\r\n});",
					"tags": ["Accessibility", "JavaScript", "Privacy", "Security"]
				},
				{
					"id": "use-dependencies-sparingly-and-maintain-them",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#use-dependencies-sparingly-and-maintain-them",
					"guideline": "Use dependencies sparingly and maintain them",
					"subheading": "Regularly review dependencies, remove unused or unnecessary libraries and frameworks, and keep required packages up to date. Opt for minimal, secure, and modular solutions.",
					"criteria": [
						{
							"title": "Dependency management",
							"description": "Review dependencies regularly and remove unused libraries and frameworks. Uninstall packages that are not needed."
						},
						{
							"title": "Dependency necessity",
							"description": "Limit the use of external libraries and frameworks to what is necessary, as this reduces the amount of code that must be downloaded and parsed by the browser. Prioritize plain code where possible. Review package size and evaluate whether individual modules can be imported instead of entire libraries, or whether a more performant alternative can be used. Do not replace established and trusted security libraries with custom implementations, as this increases vulnerability and can negatively impact sustainability."
						},
						{
							"title": "Dependency updates",
							"description": "Keep all dependencies up to date through regular review and maintenance."
						}
					],
					"example": "npm uninstall <package-name>",
					"tags": ["Accessibility", "JavaScript", "Patterns", "Performance", "Privacy", "Security", "Software"]
				},
				{
					"id": "include-expected-and-beneficial-files",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#include-expected-and-beneficial-files",
					"guideline": "Include expected and beneficial files",
					"subheading": "Include standard website metadata and configuration files to support discoverability, transparency, and operational best practices.",
					"criteria": [
						{
							"title": "Expected files",
							"description": "Include favicon.ico, robots.txt, opensearch.xml, site.webmanifest, and sitemap.xml by default. Include additional default files if they become standard."
						},
						{
							"title": "Beneficial files",
							"description": "Include additional standard files, such as ads.txt, carbon.txt, humans.txt, and security.txt. Include additional default files if they become standard."
						}
					],
					"example": "User-agent: *\r\nDisallow: \/cgi-bin\/",
					"tags": ["Accessibility", "Assets", "Compatibility", "Marketing", "Patterns", "Security", "UI"]
				},
				{
					"id": "use-the-most-efficient-solution-for-your-service",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#use-the-most-efficient-solution-for-your-service",
					"guideline": "Use the most efficient solution for your service",
					"subheading": "Choose lightweight, efficient implementation approaches that balance effort, performance, and environmental impact while favoring simple, native, and static solutions.",
					"criteria": [
						{
							"title": "Appropriate Implementation",
							"description": "Choose implementation approaches that balance effort, performance, and environmental impact. Simpler solutions may reduce complexity and runtime impact but require more human effort, while prebuilt tools may reduce build time and development effort but increase ongoing resource use. Evaluate the environmental cost of build processes, asset transformations, and external dependencies, ensuring every layer delivers genuine user value."
						},
						{
							"title": "Optimized methodology",
							"description": "Use the most performant approach for your use case. Most of the time, coding from scratch can provide the most performant results, but where a well-maintained existing solution is available it may be better optimized than what you can produce yourself. Favor native components and file systems over WYSIWYG editors, visual page builders, or heavy frameworks. Be mindful of the performance, maintenance, and environmental impact of third-party solutions."
						},
						{
							"title": "Static over dynamic",
							"description": "Deliver static content in place of dynamic content wherever possible. If code generation is required, favor the efficient tools, such as Static Site Generators (SSGs). Be aware that dynamic CMS-driven content typically involves greater server-side processing and relies on bulkier libraries compared to static approaches."
						},
						{
							"title": "Extensions and plugins",
							"description": "Review plugins, extensions, and themes regularly to ensure they remain compatible with the platform and other components, are efficient, and accessible."
						},
						{
							"title": "Interface components",
							"description": "Use user interface components that are lightweight, focused, and efficient, avoiding unnecessary complexity that increases resource use, environmental impact, or maintenance burden."
						}
					],
					"tags": ["Accessibility", "AI", "Compatibility", "Ideation", "Performance", "Privacy", "Security", "Software", "Strategy"]
				},
				{
					"id": "use-the-latest-stable-language-version",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#use-the-latest-stable-language-version",
					"guideline": "Use the latest stable language version",
					"subheading": "Use up-to-date technologies and select the most suitable programming language for each task to ensure efficiency and maintainability.",
					"criteria": [
						{
							"title": "Versioning",
							"description": "Use the latest stable version of the chosen language and framework."
						},
						{
							"title": "Language choice",
							"description": "Use the best programming language for the task, recognizing that many tools and languages are optimized for specific types of work. Adoption effort is justified where benefits outweigh costs and there is a reasonable user base, provided it does not impact the wellbeing of those involved or become cost-prohibitive."
						}
					],
					"tags": ["Accessibility", "Compatibility", "Performance", "Security"]
				},
				{
					"id": "reduce-the-number-and-complexity-of-database-queries",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#reduce-the-number-and-complexity-of-database-queries",
					"guideline": "Reduce the number and complexity of database queries",
					"subheading": "Optimize database use by minimizing and scoping queries, reducing repeated requests, and applying data governance practices.",
					"criteria": [
						{
							"title": "Database queries",
							"description": "Optimize database queries to reduce load by retrieving required data in as few queries as possible, and by applying filtering and selection at the database level rather than in application or ORM code, especially for frequently accessed data."
						},
						{
							"title": "Database queries",
							"description": "Retrieve data only once per request or process and reuse it locally instead of repeating database queries."
						},
						{
							"title": "Database queries",
							"description": "Scope database queries to return only the fields and records that are required."
						},
						{
							"title": "Database queries",
							"description": "Apply data lifecycle and governance controls such as Time-to-Live (TTL), use of non-sensitive identifiers like UUIDs, de-identification, and minimization of stored data in line with purpose limitation principles."
						}
					],
					"example": "$value = get_post_meta( int $post_id, string $key = '', bool $single = false ): mixed",
					"tags": ["Networking", "Performance"]
				}
			]
		},
		{
			"id": "4",
			"name": "Hosting, Infrastructure, and Systems",
			"shortName": "Hosting and Infrastructure",
			"guidelines": [
				{
					"id": "use-sustainable-hosting",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#use-sustainable-hosting",
					"guideline": "Use sustainable hosting",
					"subheading": "Select and manage infrastructure using sustainability metrics, prioritizing low-carbon energy use and low-impact hosting and domain choices in selection, and extending hardware lifespan and minimising emissions in management.",
					"criteria": [
						{
							"title": "Provider selection",
							"description": "Include sustainability metrics when selecting and evaluating potential infrastructure, hosting, cloud, platform, externally managed content, or other digital services. Favor providers that publicly and transparently disclose their environmental policies and related performance indicators, including Power Usage Effectiveness (PUE), Water Usage Effectiveness (WUE), Carbon Usage Effectiveness (CUE), renewable energy use, emissions reduction commitments, and hardware maintenance and sourcing practices."
						},
						{
							"title": "Efficient operation",
							"description": "Monitor and reduce the negative environmental impact of all running infrastructure over time. Whether external or self-hosted, track all available relevant indicators, such as energy use, water use, and server resource utilization. This includes CPU/cores, memory, storage, and network usage. Use this information to identify inefficiencies, reduce overprovisioning, optimize resource use, and support transparent sustainability reporting."
						},
						{
							"title": "Equipment longevity",
							"description": "Extend the lifespan of hardware. Use equipment efficiently and at the right capacity and keep it securely patched and properly maintained. New hardware should be sourced from suppliers that commit to device longevity, patching, and repair options."
						},
						{
							"title": "Low-carbon electricity",
							"description": "Use electricity with the lowest possible carbon intensity. Hosting providers should measure and report carbon intensity using available location-based grid data, including on-site generation, backup systems, and storage. Use this information to select lower-carbon hosting providers and improve energy sourcing and infrastructure efficiency."
						},
						{
							"title": "Remaining emissions",
							"description": "Reduce remaining emissions using market-based carbon accounting for indirect electricity emissions under the GHG Protocol (Scope 2). When purchasing low-carbon electricity through Energy Attribute Certificates (EACs) or Renewable Energy Certificates (RECs), ensure the certificates match the time and location of the electricity used, identify when the renewable electricity was generated, can be validly issued and retired in a way that prevents double counting."
						},
						{
							"title": "Domain names",
							"description": "Verify that the impact of domain name registration is disclosed by domain registries and registrars. Where environmental impact data is available from registrars, use it to inform domain registration decisions and mitigate environmental impact. Where such data is unavailable, assess the assumed environmental impact when making registration decisions and make sustainability-focused choices where possible."
						}
					],
					"tags": ["AI", "E-Waste", "Hardware", "Networking", "Social Equity"]
				},
				{
					"id": "optimize-caching-and-support-offline-access",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#optimize-caching-and-support-offline-access",
					"guideline": "Optimize caching and support offline access",
					"subheading": "Use caching and offline capabilities to reduce network load, improve resilience, and balance performance with sustainability.",
					"criteria": [
						{
							"title": "Caching resources",
							"description": "Use caching to reduce processing time and repeated database queries, API calls, and network requests. Apply server-side caching for dynamic content and client-side caching for resources that do not change frequently. Control cache lifetimes, serve static versions for stable assets, and minimize repeated requests for frequently used resources, balancing against added complexity and maintenance costs to improve how data is delivered."
						},
						{
							"title": "Offline access",
							"description": "Keep essential content and functionality available during network interruptions. Provide offline access using web platform capabilities, such as Progressive Web Applications (PWAs), Service Workers, Web Workers, or local storage."
						}
					],
					"example": "<IfModule mod_expires.c>\r\n\tExpiresActive on\r\n\t# Default: Fallback\r\n\tExpiresDefault                                      \"access plus 1 year\"\r\n\t# Specific: Assets\r\n\tExpiresByType image\/x-icon                          \"access plus 1 week\"\r\n\tExpiresByType application\/rss+xml                   \"access plus 1 hour\"\r\n\tExpiresByType application\/json                      \"access\"\r\n<\/IfModule>",
					"tags": ["Accessibility", "Assets", "HTML", "JavaScript", "Networking", "Performance", "Software"]
				},
				{
					"id": "reduce-data-transfer-with-compression",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#reduce-data-transfer-with-compression",
					"guideline": "Reduce data transfer with compression",
					"subheading": "Compress server responses and media files to reduce bandwidth, storage use, and delivery overhead while balancing processing costs.",
					"criteria": [
						{
							"title": "Server-side compression",
							"description": "Use server-side compression settings and tools to compress commonly used file types when appropriate. Ensure that compression reduces energy consumption, minimizes load times, saves bandwidth, and improves overall performance. Do not apply additional compression to files that are already appropriately sized for upload."
						},
						{
							"title": "Media compression",
							"description": "Compress media files such as images, video, and audio before uploading anywhere to reduce storage and transfer requirements."
						}
					],
					"example": "<IfModule mod_deflate.c>\r\n\t<IfModule mod_setenvif.c>\r\n\t\t<IfModule mod_headers.c>\r\n\t\t\tSetEnvIfNoCase ^(Accept-EncodXng|X-cept-Encoding|X{15}|~{15}|-{15})$ ^((gzip|deflate)\\s*,?\\s*)+|[X~-]{4,13}$ HAVE_Accept-Encoding\r\n\t\t\tRequestHeader append Accept-Encoding \"zstd, gzip, br, deflate\" env=HAVE_Accept-Encoding\r\n\t\t<\/IfModule>\r\n\t<\/IfModule>\r\n\t<IfModule mod_filter.c>\r\n\t\tAddOutputFilterByType DEFLATE \"application\/atom+xml application\/javascript application\/json application\/ld+json application\/manifest+json application\/rdf+xml application\/rss+xml application\/schema+json application\/geo+json application\/vnd.ms-fontobject application\/wasm application\/x-font-ttf application\/x-javascript application\/x-web-app-manifest+json application\/xhtml+xml application\/xml font\/eot font\/opentype font\/otf font\/ttf image\/bmp image\/svg+xml image\/vnd.microsoft.icon image\/x-icon text\/cache-manifest text\/calendar text\/css text\/html text\/javascript text\/plain text\/markdown text\/vcard text\/vnd.rim.location.xloc text\/vtt text\/x-component text\/x-cross-domain-policy text\/xml\"\r\n\t<\/IfModule>\r\n\t<IfModule mod_mime.c>\r\n\t\tAddEncoding gzip              svgz\r\n\t<\/IfModule>\r\n<\/IfModule>",
					"tags": ["Assets", "Networking", "Performance"]
				},
				{
					"id": "setup-necessary-error-pages-and-redirection-links",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#setup-necessary-error-pages-and-redirection-links",
					"guideline": "Setup necessary error pages and redirection links",
					"subheading": "Provide clear error handling and ensure broken links are either fixed or redirected to destinations to prevent navigation issues.",
					"criteria": [
						{
							"title": "Error pages",
							"description": "Implement clear error handling and user-friendly error pages that explain what went wrong and guide users back to content."
						},
						{
							"title": "Redirection",
							"description": "Update broken and outdated links if they are no longer valid. Use redirects only when they clearly benefit users or preserve SEO value, and avoid long or unnecessary redirect chains. Apply proportionality so engineering and maintenance costs do not outweigh performance or SEO gains. Test redirects to prevent errors and loops, and choose the simplest effective approach."
						}
					],
					"example": "ErrorDocument 404 /404.html",
					"tags": ["Accessibility", "Compatibility", "Content", "Marketing", "Networking", "UI", "Usability"]
				},
				{
					"id": "avoid-maintaining-unnecessary-virtualized-environments-or-containers",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#avoid-maintaining-unnecessary-virtualized-environments-or-containers",
					"guideline": "Avoid maintaining unnecessary virtualized environments or containers",
					"subheading": "Remove unnecessary virtualized environments to improve efficiency and maintainability.",
					"criteria": [
						{
							"title": "Unused environments",
							"description": "Reduce the number of active environments by deactivating, offlining, or removing unused or redundant virtual and physical environments (e.g., containers and virtual machines) wherever this can be done without reducing required security, isolation, or compliance guarantees. Optimize active environments by tailoring resource allocations to actual workload demand, sharing common services, and eliminating duplicate tasks while maintaining necessary isolation."
						}
					],
					"tags": ["AI", "Hardware", "Networking", "Performance", "Software"]
				},
				{
					"id": "use-automation-wisely",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#use-automation-wisely",
					"guideline": "Use automation wisely",
					"subheading": "Automate and scale tasks and infrastructure efficiently, run processes only when needed, and control unwanted traffic.",
					"criteria": [
						{
							"title": "Task automation",
							"description": "Automate recurring tasks such as deployment, testing, and compilation in alignment with continuous integration and continuous delivery (CI/CD) best practices to reduce manual effort and improve consistency. Choose automation tools and platforms with lower environmental impact. Avoid complexity and duplication of automation systems."
						},
						{
							"title": "Necessary tasks",
							"description": "Run automated tasks only when they are needed to avoid unnecessary resource use. Regularly review automated tasks to ensure they remain necessary, efficient, secure, and beneficial."
						},
						{
							"title": "Automated scaling",
							"description": "Regularly review infrastructure utilization and reduce allocated capacity when resources are consistently underused. Manage workloads to ensure efficient resource use by isolating, limiting, and prioritizing processes where needed to prevent resource contention and unnecessary consumption. Use autoscaling, buffering, throttling and other techniques to scale resource utilization to avoid overprovisioning."
						},
						{
							"title": "Suspicious activity management",
							"description": "Restrict unwanted and unnecessary third-party crawlers, user agents, bots, and scrapers using security controls, while ensuring content remains accessible to legitimate users, search engines, and helpful or authorized crawlers. Regularly monitor activity logs to evaluate control effectiveness and identify unexpected traffic patterns. Take into account that some scrapers may be used for beneficial purposes, or to inform or train large language models."
						}
					],
					"tags": ["Accessibility", "AI", "Performance", "Security", "Software"]
				},
				{
					"id": "define-the-frequency-of-data-refreshes",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#define-the-frequency-of-data-refreshes",
					"guideline": "Define the frequency of data refreshes",
					"subheading": "Decide when to refresh data based on a balance of user and sustainability requirements.",
					"criteria": [
						{
							"title": "Refresh frequency",
							"description": "Define cache refresh rates based on user needs, accuracy requirements, and resource efficiency to determine when data is updated."
						}
					],
					"tags": ["JavaScript", "Networking", "Performance", "Usability"]
				},
				{
					"id": "back-up-critical-data-at-routine-intervals",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#back-up-critical-data-at-routine-intervals",
					"guideline": "Back up critical data at routine intervals",
					"subheading": "Back up data at regular intervals to ensure that there are failsafes that can be relied upon should an issue occur.",
					"criteria": [
						{
							"title": "Data backups",
							"description": "Ensure backups of systems and user data are secure and incremental to minimize storage use and reduce backup time. Limit access to backups, and establish mechanisms to prevent user-identifiable information from being stored long term. Protect backups against data loss or misuse."
						}
					],
					"tags": ["Hardware", "Performance", "Security"]
				},
				{
					"id": "assess-the-impact-and-requirements-of-data-processing",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#assess-the-impact-and-requirements-of-data-processing",
					"guideline": "Assess the impact and requirements of data processing",
					"subheading": "Use carbon-aware scheduling, efficient and secure protocols, and simple system designs to reduce unnecessary processing while balancing performance, security, and constraints.",
					"criteria": [
						{
							"title": "Carbon shifting",
							"description": "Use carbon-aware computing to dynamically optimize workload execution by scheduling or batching tasks to run at a time when carbon intensity is lower based on real-time grid carbon intensity data, or shifting workloads to regions with lower carbon intensity when possible, while respecting security, performance, and data residency constraints."
						},
						{
							"title": "Protocol efficiency",
							"description": "Choose communication protocols that balance user needs, security, and sustainability by improving efficiency and reducing resource use. Prioritize secure options like HTTPS and SFTP/SSH, avoid insecure legacy protocols such as HTTP and FTP, and adopt modern standards like HTTP/2 or HTTP/3 for better performance and lower network overhead. Maintain backward compatibility only where necessary."
						},
						{
							"title": "Event-driven architecture",
							"description": "Use event-driven architecture and microservices when building products with state changes that do not require full page refreshes. Favor those where they offer a more energy-efficient alternative to REST-style synchronous APIs based on performance, power, and processing factors, and choose the approach that reduces server workload and environmental impact while meeting requirements."
						},
						{
							"title": "Data processing efficiency",
							"description": "Avoid unnecessary data processing. Decide carefully whether processing should happen on the client or server based on performance, security, sustainability metrics, and resource use."
						},
						{
							"title": "Efficient location",
							"description": "Perform data transformations, transfers, and processing between the layers of an application as close to the source as possible. This reduces unnecessary serialization overhead and avoids wasting resources."
						}
					],
					"tags": ["AI", "JavaScript", "Networking", "Performance"]
				},
				{
					"id": "use-content-delivery-networks-cdns-when-beneficial",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#use-content-delivery-networks-cdns-when-beneficial",
					"guideline": "Use Content Delivery Networks (CDNs) when beneficial",
					"subheading": "Use CDNs and data location strategically for static content and processing only when they improve efficiency and sustainability, while avoiding unnecessary distribution and transfers.",
					"criteria": [
						{
							"title": "Global CDNs",
							"description": "Use a Content Delivery Network (CDN) for static content, assets, and other read-only resources only where it provides clear benefits, evaluating performance improvements and environmental impact on a case-by-case basis in line with broader web hosting choices. When serving an exclusively local audience, evaluate whether a CDN is necessary, and prefer geographically close hosting instead."
						},
						{
							"title": "Sustainability commitment",
							"description": "Choose CDN providers that demonstrate credible, evidence-based web sustainability commitments."
						},
						{
							"title": "Inappropriate resources",
							"description": "Avoid deploying dynamic or frequently changing resources to a CDN, as browser mechanisms like cache partitioning and cross-origin resource sharing (CORS) can limit caching benefits and interaction performance, reducing resource efficiency, while workarounds may introduce security or privacy risks."
						}
					],
					"tags": ["Accessibility", "AI", "Content", "Hardware", "Networking", "Performance"]
				},
				{
					"id": "ensure-infrastructure-fits-project-requirements",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#ensure-infrastructure-fits-project-requirements",
					"guideline": "Ensure infrastructure fits project requirements",
					"subheading": "Use demand-matched, autoscaling infrastructure to meet demand efficiently without overprovisioning.",
					"criteria": [
						{
							"title": "Lowest requirements",
							"description": "Select infrastructure that meets your requirements and customer agreements without over-provisioning. Favor standalone instances over multi-zone or distributed setups when requirements allow. Provision for average loads rather than peak loads to ensure efficient resource use."
						}
					],
					"tags": ["E-Waste", "Hardware", "Performance"]
				},
				{
					"id": "store-data-according-to-the-needs-of-your-users",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#store-data-according-to-the-needs-of-your-users",
					"guideline": "Store data according to the needs of your users",
					"subheading": "Regularly manage and reduce stored data (including content, logs, media, and downloads) using retention, compression, and lifecycle policies, while maintaining efficient access to long-term assets.",
					"criteria": [
						{
							"title": "Remove unused data",
							"description": "Regularly remove unused or obsolete data (\"dark data\") to reduce storage and energy costs, and manage whether and how long data is stored."
						},
						{
							"title": "Lifecycle management",
							"description": "Use classification and tagging policies to define and manage data lifecycle rules, including retention, expiration, and archiving. Align storage choices to how frequently data is accessed, shifting less frequently used data to energy-efficient storage."
						},
						{
							"title": "Efficient storage",
							"description": "Store data only where it provides lasting operational, analytical, or legal value and cannot be easily regenerated or replaced. Remove or archive it when it becomes obsolete. Avoid unnecessary duplication and use efficient storage practices such as compression, caching, and storage optimization techniques."
						},
						{
							"title": "Optimized logging",
							"description": "Manage logs with regular rotation, retention, compression, and backup practices to reduce storage and processing overhead. Schedule resource-intensive operations during low-activity periods, use resilient backups, including off-site storage where needed, and remove sensitive information where possible to minimize security and privacy risks. Use logs, monitoring, and alerts at a regular frequency and scope to provide value while avoiding unnecessary processing, storage, and network use. Use collected data to identify and reduce avoidable resource consumption, such as unnecessary automated requests."
						},
						{
							"title": "Asset downloads",
							"description": "Make large, long-term assets easily downloadable so users do not need repeated server requests."
						}
					],
					"tags": ["Accessibility", "Content", "E-Waste", "Hardware", "Performance", "Privacy"]
				}
			]
		},
		{
			"id": "5",
			"name": "Business Strategy And Product Management",
			"shortName": "Business and Product",
			"guidelines": [
				{
					"id": "have-an-ethical-and-sustainable-product-strategy",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#have-an-ethical-and-sustainable-product-strategy",
					"guideline": "Have an ethical and sustainable product strategy",
					"subheading": "Implement organizational practices around ethics, sustainability, and responsible data use. Publish and maintain policies that demonstrate their implementation.",
					"criteria": [
						{
							"title": "Public documents",
							"description": "Develop, publish, and maintain key organizational policies such as a code of ethics, product guidelines, cloud sustainability strategy, and accessibility and sustainability statements. Use clear language to describe digital products, services, and emerging or disruptive technologies, such as AI. Make these policies publicly accessible and keep them versioned for transparency."
						},
						{
							"title": "Achievements and compliance",
							"description": "Publish web sustainability-related achievements, features, compliance updates, and other relevant information within a dedicated sustainability section."
						},
						{
							"title": "Governance over time",
							"description": "Provide evidence that sustainability policies and practices are actively implemented, monitored, and governed over time."
						},
						{
							"title": "Technology legislation",
							"description": "Advocate for and comply with evidence-based legislation and standards that advance digital privacy, employment rights, transparency, accountability, responsible emerging technologies, and digital sustainability. Simultaneously make efforts to go beyond minimum expectations, especially in regard to avoiding unnecessary data collection to preserve an efficient and accessible user journey in compliance with accessibility and data protection requirements."
						}
					],
					"tags": ["Accessibility", "AI", "Education", "Ideation", "KPIs", "Privacy", "Research", "Security", "Social Equity", "Strategy"]
				},
				{
					"id": "assign-a-sustainability-advocate",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#assign-a-sustainability-advocate",
					"guideline": "Assign a sustainability advocate",
					"subheading": "Appoint a sustainability advocate who is provided with what they require to speak about and for issues relating to sustainability.",
					"criteria": [
						{
							"title": "Advocate for sustainability",
							"description": "Assign clear responsibility for digital sustainability by appointing a sustainability lead with specific digital expertise and providing them with the resources, budget, tools, and time they need to achieve their stated goals. In some organizations, expanding this into a climate working group comprising motivated individuals can add further benefits."
						}
					],
					"tags": ["Accessibility", "Education", "Ideation", "Marketing", "Privacy", "Social Equity"]
				},
				{
					"id": "inform-raise-awareness-and-train-for-sustainability",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#inform-raise-awareness-and-train-for-sustainability",
					"guideline": "Inform, raise awareness, and train for sustainability",
					"subheading": "Provide ongoing training, onboarding, and guidance on sustainability practices, and support participation in sustainability initiatives through clear materials, knowledge sharing, and organizational encouragement.",
					"criteria": [
						{
							"title": "Inform and aware",
							"description": "Produce, provide, and/or facilitate the delivery of onboarding materials and workshops to everyone connected to your project, including internal teams, external contributors, colleagues, and organizational decision-makers. Include education on general and digital climate literacy, as well as guidance on your own sustainable technology policies."
						},
						{
							"title": "Routine training",
							"description": "Provide active and routine training to develop, establish, and refresh sustainability skills through ongoing learning opportunities that support teams in achieving sustainability objectives."
						},
						{
							"title": "Active participation",
							"description": "Encourage individuals to reduce their environmental impact. Share climate and sustainable initiatives and ideas. Provide resources on sustainable design, best practices, and concepts."
						},
						{
							"title": "Training materials",
							"description": "Create and/or deliver dedicated training manuals, workshops, and materials to outline the adopted sustainability policies and practices and how to implement them. Manage and maintain these materials over time, adapting them as new policies and best practices arise."
						},
						{
							"title": "Incentivize progress",
							"description": "Encourage leadership, teams, and individuals to make progress toward their training goals by recognizing completion, allocating time for sustainability-related activities, and providing incentives and benefits."
						}
					],
					"tags": ["Content", "Education", "Marketing", "Reporting"]
				},
				{
					"id": "communicate-the-environmental-impact-of-user-choices",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#communicate-the-environmental-impact-of-user-choices",
					"guideline": "Communicate the environmental impact of user choices",
					"subheading": "Empower users, allowing them to make decisions when their choices can influence the environmental impact they have.",
					"criteria": [
						{
							"title": "Communication of impact",
							"description": "Show users how their actions affect energy use, emissions, or resource consumption, and provide options that help them make more informed choices."
						}
					],
					"tags": ["Content", "Education", "Marketing", "Reporting"]
				},
				{
					"id": "calculate-the-environmental-impact",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#calculate-the-environmental-impact",
					"guideline": "Calculate the environmental impact",
					"subheading": "Assess and compare full life cycle environmental impacts, including those of third-party services, to inform sustainable design decisions.",
					"criteria": [
						{
							"title": "Life-cycle assessment",
							"description": "Conduct a life cycle assessment (LCA) to understand the environmental impact of each functional unit - a defined measure of a product or service being assessed - including lifecycle greenhouse gas (GHG) emissions and other relevant environmental impacts across the full project lifecycle."
						},
						{
							"title": "Competitor impact",
							"description": "Evaluate the environmental impact of your project against comparable alternatives to inform decision-making targets. Determine whether the project's additional value or sustainability benefits justify its environmental impacts."
						},
						{
							"title": "Tooling impact",
							"description": "Include the impact or estimated impact of any tooling or third-party solutions used at any stage in your pipeline. While not created by you, the emissions generated in production, maintenance, and use are also integral to your overall solution."
						}
					],
					"tags": ["Accessibility", "AI", "Ideation", "KPIs", "Research", "Social Equity", "Software", "Strategy"]
				},
				{
					"id": "define-clear-organizational-sustainability-goals-and-metrics",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#define-clear-organizational-sustainability-goals-and-metrics",
					"guideline": "Define clear organizational sustainability goals and metrics",
					"subheading": "Define measurable sustainability goals and metrics, and communicate progress over time.",
					"criteria": [
						{
							"title": "Web sustainability goals",
							"description": "Define and publish clear web sustainability goals. Identify measurable performance metrics and communicate progress against those goals so that people can understand and evaluate sustainability performance."
						}
					],
					"tags": ["AI", "Governance", "Ideation", "KPIs", "Research", "Social Equity"]
				},
				{
					"id": "validate-web-sustainability-efforts-through-external-verification",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#validate-web-sustainability-efforts-through-external-verification",
					"guideline": "Validate web sustainability efforts through external verification",
					"subheading": "Use independent verification to support and improve sustainability claims.",
					"criteria": [
						{
							"title": "Obtaining verification",
							"description": "Use independent third-party verification or assurance to validate sustainability claims."
						},
						{
							"title": "Maintaining verification",
							"description": "Reassess sustainability claims over time and update them when new evidence affects their accuracy."
						}
					],
					"tags": ["Governance", "KPIs"]
				},
				{
					"id": "support-mandatory-disclosures-and-reporting",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#support-mandatory-disclosures-and-reporting",
					"guideline": "Support mandatory disclosures and reporting",
					"subheading": "Publish transparent, standards-aligned sustainability reports that track progress over time and clearly explain real impact reductions without misleading reporting.",
					"criteria": [
						{
							"title": "Policies and practices",
							"description": "Create and publish policies and practices for disclosing the environmental, social, and governance impacts of digital products, programs, and services in line with recognized standards."
						},
						{
							"title": "Impact reports",
							"description": "Publish a public sustainability impact report at least annually, including progress against previous reports and web sustainability goals."
						},
						{
							"title": "Disclosure reporting",
							"description": "Create and maintain transparent reporting practices for the emissions and the environmental, social, and governance impacts of digital products and web services."
						},
						{
							"title": "Impact reduction",
							"description": "Clearly explain how the environmental, social, and governance impacts are reduced, while avoiding misleading practices such as double counting, greenwashing, data exclusion, or selective reporting."
						}
					],
					"tags": ["AI", "Content", "KPIs", "Reporting"]
				},
				{
					"id": "create-one-or-more-impact-business-models",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#create-one-or-more-impact-business-models",
					"guideline": "Create one or more impact business models",
					"subheading": "Describe how revenue generation supports environmental and social outcomes.",
					"criteria": [
						{
							"title": "Theory of change",
							"description": "Document how the organization generates revenue and how those revenue streams relate to environmental and social impacts. Describe how impacts are measured, reviewed, and improved over time."
						}
					],
					"tags": ["Content", "Ideation", "Research", "Strategy"]
				},
				{
					"id": "follow-a-product-management-and-maintenance-strategy",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#follow-a-product-management-and-maintenance-strategy",
					"guideline": "Follow a product management and maintenance strategy",
					"subheading": "Maintain clear documentation, resourcing, and measurement practices for long-term product support, including security, sustainability, and early detection of failure risks.",
					"criteria": [
						{
							"title": "Management and maintenance",
							"description": "Produce and maintain documentation to outline how the organization approaches product management and maintenance."
						},
						{
							"title": "Planning strategy",
							"description": "Develop, implement, and maintain maintenance and security plans for all digital products and services that prioritize long-term sustainability, energy efficiency, and responsible resource use across the product lifecycle."
						},
						{
							"title": "Resourcing products",
							"description": "Ensure products, prototypes, testing, and supporting processes are adequately resourced over time. Maintain sufficient staffing and budget to support ongoing maintenance, including addressing technical debt, refactoring, and evolving functionality, without abandoning projects."
						},
						{
							"title": "Resource measurement",
							"description": "Include carbon and resource measurement in maintenance processes, and track improvements over time. Prioritize metrics that reflect essential value delivered and sustainability outcomes. Avoid metrics that incentivize unnecessary work, resource consumption, or emissions."
						},
						{
							"title": "Failure indicators",
							"description": "Identify and document Key Failure Indicators (KFIs), including those related to accessibility, usability, and other environmental, social, and governance impacts. Monitor KFIs to detect emerging risks and inform corrective action."
						}
					],
					"tags": ["Accessibility", "Compatibility", "Security", "Strategy"]
				},
				{
					"id": "implement-continuous-improvement-procedures",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#implement-continuous-improvement-procedures",
					"guideline": "Implement continuous improvement procedures",
					"subheading": "Maintain continuous improvement processes that balance feature changes, maintenance, and updates with user value and sustainability outcomes.",
					"criteria": [
						{
							"title": "Continuous improvement",
							"description": "Embed continuous improvement practices that clearly report what is changing, why it is changing, and whether it improves environmental sustainability outcomes. Ensure that environmental and other ESG impacts are assessed alongside operational and business performance metrics."
						},
						{
							"title": "Retrospectives conducted",
							"description": "Review deliverables and update frequently to ensure project teams have enough time to conduct user research, identify and eliminate technical debt, and produce high-quality output as well as share what they learned."
						},
						{
							"title": "Iterative consideration",
							"description": "Display a track record of continuous improvement (iteration) processes to analyze the digital product or service. Simultaneously address any potential consequences of ongoing experimentation, such as technical debt, product performance, and emissions. Limit analytics to strictly necessary features that aid decision-making, encouraging user feedback, and comparing performance against organization goals and user needs."
						},
						{
							"title": "Functionality decisions",
							"description": "Regularly review all functionality across the product lifecycle. Justify and prioritize decisions to retain, change, add, or remove features based on environmental impact, user value, usage, and maintenance cost. This includes decommissioning unused or low-traffic functionality and content."
						}
					],
					"tags": ["Accessibility", "AI", "Compatibility", "KPIs", "Performance", "Privacy", "Security", "Strategy", "UI"]
				},
				{
					"id": "document-updates-and-evolutions",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#document-updates-and-evolutions",
					"guideline": "Document updates and evolutions",
					"subheading": "Provide documentation to help users find their way whenever functionality changes.",
					"criteria": [
						{
							"title": "Feature changes",
							"description": "Provide clear, structured documentation when features are added, changed, or removed. Use a consistent versioning or change-tracking system to communicate the nature and impact of changes."
						}
					],
					"example": "# Changelog - Website\r\n\r\n## [Unreleased]\r\n- N\/A\r\n\r\n## 1.0.0 - YYYY-MM-DD\r\n### Added\r\n- Content.\r\n\r\n## [Guide]\r\n- Added: New features.\r\n- Changed: Altered functionality.\r\n- Deprecated: Disappearing features.\r\n- Removed: Eliminated features.\r\n- Fixed: Bugs patched.\r\n- Security: Solved vulnerabilities.",
					"tags": ["Compatibility", "Content", "Education", "Security", "Usability"]
				},
				{
					"id": "evaluate-if-a-digital-product-or-service-is-necessary",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#evaluate-if-a-digital-product-or-service-is-necessary",
					"guideline": "Evaluate if a digital product or service is necessary",
					"subheading": "Assess alignment with sustainability goals, validate product need, and reduce barriers to access, usability, and fairness.",
					"criteria": [
						{
							"title": "Sustainable Development Goals",
							"description": "Identify whether the product or service aligns with any relevant UN Sustainable Development Goals (SDGs) and, where applicable, include corresponding targets within a sustainability statement."
						},
						{
							"title": "Creation evaluation",
							"description": "Evaluate whether a product or service is needed based on desirability, feasibility, and viability."
						},
						{
							"title": "Obstacle consideration",
							"description": "Remove or reduce barriers that prevent people from using a product or service, including accessibility, technical, geographic, and fairness-related barriers."
						}
					],
					"tags": ["Accessibility", "AI", "E-Waste", "Ideation", "Reporting", "Software"]
				},
				{
					"id": "provide-a-supplier-standards-of-practice-document",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#provide-a-supplier-standards-of-practice-document",
					"guideline": "Provide a supplier standards of practice document",
					"subheading": "Select and work with suppliers based on sustainability principles, measure their impact, and transparently publish partnership outcomes.",
					"criteria": [
						{
							"title": "Vetting potential partners",
							"description": "Apply sustainability principles when selecting and managing suppliers, partners, and service providers across supply chains. Establish procurement criteria and due diligence practices that consider environmental and social impacts and relevant lifecycle considerations."
						},
						{
							"title": "Collaborative measurement",
							"description": "Partner with suppliers to create, track, and measure impacts on affected parties."
						},
						{
							"title": "Informative partner promotion",
							"description": "Promote and disclose partnerships in a publicly available place, along with information on how the partnership creates a collective impact."
						}
					],
					"tags": ["AI", "Content", "Governance", "Hardware", "Ideation", "Social Equity"]
				},
				{
					"id": "share-economic-benefits",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#share-economic-benefits",
					"guideline": "Share economic benefits",
					"subheading": "Commit to fair pay, align workers and contractors with shared impact goals, and provide employee benefits within available resources.",
					"criteria": [
						{
							"title": "Living wage",
							"description": "Publicly commit to paying employees, contractors, and other affected parties a living wage."
						},
						{
							"title": "Incentivisation",
							"description": "Embed incentives for affected parties such as workers and contractors into organizational practices to support impact goals, underpinned by clear policies that guide how incentives are designed and applied."
						},
						{
							"title": "Employee benefits",
							"description": "Provide employee benefits that match available resources, which may include healthcare, retirement support, flexible working, and profit sharing."
						}
					],
					"tags": ["Governance", "Social Equity"]
				},
				{
					"id": "share-decision-making-power-with-affected-parties",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#share-decision-making-power-with-affected-parties",
					"guideline": "Share decision-making power with affected parties",
					"subheading": "Involve users and staff in decision-making, ensure human oversight, and provide transparency, and create challenge mechanisms for automated decisions.",
					"criteria": [
						{
							"title": "Decision-making",
							"description": "Involve people, including users and staff, in decisions that impact them. Provide meaningful opportunities to participate in relevant decision-making processes and ensure decision-makers have clear authority and accountability. Where automated systems are used, provide transparency about their role in decisions, enable human oversight, and allow people to opt out, object, withdraw their consent, and challenge decisions. Ensure challenges are reviewed by a human decision-maker."
						}
					],
					"tags": ["Accessibility", "Ideation", "Social Equity", "Strategy"]
				},
				{
					"id": "use-diversity-equity-justice-inclusion-deji-practices",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#use-diversity-equity-justice-inclusion-deji-practices",
					"guideline": "Use Diversity, Equity, Justice, Inclusion (DEJI) practices",
					"subheading": "Publish and act on Diversity, Equity, Justice, Inclusion (DEJI) and accessibility commitments, support training and measurable progress, and ensure inclusive outcomes across products and operations.",
					"criteria": [
						{
							"title": "DEJI practices",
							"description": "Publish clear commitments to DEJI. Explain how the organization applies these commitments to reduce exclusion and support the long-term sustainability of access to the product for diverse and underserved or marginalized communities."
						},
						{
							"title": "DEJI training",
							"description": "Provide DEJI training and topics such as algorithmic bias, the digital divide, employment equity, mis- and disinformation."
						},
						{
							"title": "DEJI improvements",
							"description": "Track and publish measurable progress in DEJI across hiring, leadership, and operations."
						}
					],
					"tags": ["Accessibility", "Ideation", "Social Equity", "Strategy"]
				},
				{
					"id": "promote-responsible-data-practices",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#promote-responsible-data-practices",
					"guideline": "Promote responsible data practices",
					"subheading": "Respect user data rights and manage data lifecycle through minimized collection, user control, portability, deletion, and content archiving.",
					"criteria": [
						{
							"title": "Data practices",
							"description": "Maintain publicly accessible privacy, legal, and policy documents in plain language and accessible formats. Follow strong data protection practices aligned with recognized international standards, apply stronger protections where risks to users are higher or safeguards are insufficient, and support good practices in privacy, accessibility, and sustainability through transparent data use and governance."
						},
						{
							"title": "Data ownership",
							"description": "Respect user data rights, including access, correction, deletion, opt-out, and data portability. Provide clear user controls to manage accounts, data, and subscriptions. Only collect and retain personal data for a defined purpose and for no longer than necessary. Provide data export in open, commonly used formats. Ensure that deletion and consent changes apply across all systems, including databases, derived datasets, backups, and caches, within a reasonable timeframe."
						},
						{
							"title": "Outdated content",
							"description": "Archive and delete outdated or otherwise expired product content and data via automated expiration dates and scheduled product audits. Publish the archiving schedule, ensuring a lightweight version of the old searchable content is maintained for those that may require it."
						}
					],
					"tags": ["Privacy", "Security", "Social Equity", "Strategy"]
				},
				{
					"id": "establish-responsible-practices-around-ai-and-emerging-or-disruptive-technologies",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#establish-responsible-practices-around-ai-and-emerging-or-disruptive-technologies",
					"guideline": "Establish responsible practices around AI and emerging or disruptive technologies",
					"subheading": "Ensure responsible use of automated systems by only using ethically sourced and suitably sized data and models, managing environmental impacts, supporting workforce adaptation, respecting user agent controls, and using post-quantum encryption only where justified.",
					"criteria": [
						{
							"title": "AI and data collection",
							"description": "Ensure datasets used, created, or referenced by automated systems are no larger than necessary for the task, ethically sourced, screened, validated, stored, and used in a fair and non-discriminatory, responsible way."
						},
						{
							"title": "Business adaptation",
							"description": "Support employees in adapting to new technologies that may change or disrupt their roles or the organization's operations."
						},
						{
							"title": "Environmental responsibilities",
							"description": "Evaluate the need for AI and emerging or disruptive technologies before implementation to avoid unnecessary resource use. Optimize models and deployment processes for efficiency. Measure, assess, and account for their environmental impacts throughout their lifecycle. Include impacts from first-party and third-party sources, using available data or credible estimates where direct data is unavailable. Prioritize approaches that minimize negative environmental impacts."
						},
						{
							"title": "Automated tooling",
							"description": "Ensure bots, crawlers, user agents, scrapers, artificial intelligence, and all other automated tools respect opt-out signals at the host, server, and site level. Providers must declare themselves as non-human within the user agent in the HTTP header."
						},
						{
							"title": "Quantum resilience",
							"description": "Use post-quantum encryption only where there is a clear need to protect against “harvest now, decrypt later” attacks and long-term data confidentiality risks. Treat it as supplementary to rather than replacing existing encryption methods, using both during any transition. Apply caution when adopting post-quantum encryption in high-traffic services, as the bandwidth consumption, processing demand, design complexity, and migration risks may outweigh the security benefits."
						}
					],
					"tags": ["Accessibility", "AI", "Content", "E-Waste", "Governance", "Hardware", "Networking", "Performance", "Privacy", "Security", "Social Equity", "Software"]
				},
				{
					"id": "adopt-responsible-financial-practices",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#adopt-responsible-financial-practices",
					"guideline": "Adopt responsible financial practices",
					"subheading": "Adopt responsible financing practices by divesting from high-carbon assets and aligning budgeting and financial partnerships with long-term sustainability.",
					"criteria": [
						{
							"title": "Fuel divestment",
							"description": "Divest from fossil fuels and move financial relationships, including banking and sponsorships, toward more sustainable partners."
						},
						{
							"title": "Responsible finance",
							"description": "Use responsible budgeting and financing practices that support long-term maintenance and environmental responsibility."
						}
					],
					"tags": ["Governance", "Ideation", "Social Equity"]
				},
				{
					"id": "adopt-organizational-philanthropy-practices",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#adopt-organizational-philanthropy-practices",
					"guideline": "Adopt organizational philanthropy practices",
					"subheading": "Align partnerships and corporate giving with the organization's purpose, and support skill-building voluntary and pro bono work through clear partnership and giving policies.",
					"criteria": [
						{
							"title": "Philanthropy policy",
							"description": "Create a corporate giving policy and establish philanthropic partnerships with strategically aligned organizations."
						},
						{
							"title": "Voluntary work",
							"description": "Support voluntary and pro-bono work that helps teams learn and benefits non-profit and charitable organizations."
						}
					],
					"tags": ["Content", "Governance", "Social Equity"]
				},
				{
					"id": "plan-for-a-digital-product-or-service-s-care-and-end-of-life",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#plan-for-a-digital-product-or-service-s-care-and-end-of-life",
					"guideline": "Plan for a digital product or service's care and end-of-life",
					"subheading": "Document when a project is shut down and make users aware of what will happen to their data.",
					"criteria": [
						{
							"title": "End-of-life care",
							"description": "Provide clear, documented end-of-life guidelines that include data disposal, archiving, file deletion, and other relevant guidance."
						}
					],
					"tags": ["Compatibility", "E-Waste", "Privacy", "Research", "Security", "Social Equity", "Software", "Strategy"]
				},
				{
					"id": "repair-reuse-refurbish-recycle-or-reduce-e-waste",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#repair-reuse-refurbish-recycle-or-reduce-e-waste",
					"guideline": "Repair, reuse, refurbish, recycle or reduce e-waste",
					"subheading": "Prioritize repair, reuse, refurbishment, and responsible recycling of hardware and e-waste through certified services, including supporting users doing repairs.",
					"criteria": [
						{
							"title": "E-waste management",
							"description": "Recycle, repair, or upcycle unwanted hardware and materials. Recover, redeploy, and reuse components where possible, and dispose of remaining materials in a sustainable way. Use certified repair and recycling services to handle end-of-life digital equipment and operational e-waste responsibly. Service providers should maintain a clear policy for responsible e-waste management."
						},
						{
							"title": "E-waste policy",
							"description": "Maintain policies for repairing and recycling hardware and encourage repair."
						},
						{
							"title": "Refurbishment strategy",
							"description": "Prioritize reuse, refurbishment, and redeployment of existing hardware before purchasing new equipment."
						},
						{
							"title": "Right to repair",
							"description": "Allow users to repair purchased products to the best of their ability, provide replacement parts at cost where possible, and give clear instructions to help fix faults when they occur."
						}
					],
					"tags": ["Content", "E-Waste", "Governance", "Hardware", "Ideation", "Social Equity"]
				},
				{
					"id": "define-performance-environmental-and-human-budgets",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#define-performance-environmental-and-human-budgets",
					"guideline": "Define performance, environmental, and human budgets",
					"subheading": "Define and apply lifecycle sustainability and performance budgets, set evidence-based KPIs, and track measurable improvements over time.",
					"criteria": [
						{
							"title": "Environmental budget",
							"description": "Outline and document digital sustainability budget criteria covering the full lifecycle of products and services, including creation, usage, and decommissioning. Ensure these limits are actively applied and communicated to all affected parties."
						},
						{
							"title": "Performance budget",
							"description": "Use performance budgets to cap the size and complexity of digital products or services, actively reducing data transfer and file sizes to improve performance and create more sustainable, lower-impact digital experiences."
						},
						{
							"title": "Human budget",
							"description": "Define KPIs for engineering effort, development time, or sprints. Optimize workflows sustainably so work is done with care, while prioritizing worker health, wellbeing, and sustainable workloads."
						},
						{
							"title": "Measurable improvements",
							"description": "Establish baseline measurements and track improvements over time. Require that improvement claims are supported by evidence."
						}
					],
					"example": "[\r\n{\r\n\t\"resourceSizes\": [],\r\n\t\"timings\": [\r\n\t{\r\n\t\t\"metric\": \"largest-contentful-paint\",\r\n\t\t\"budget\": 2500\r\n\t},\r\n\t{\r\n\t\t\"metric\": \"max-potential-fid\",\r\n\t\t\"budget\": 100\r\n\t},\r\n\t{\r\n\t\t\"metric\": \"cumulative-layout-shift\",\r\n\t\t\"budget\": 0.1\r\n\t}\r\n\t]\r\n}\r\n]",
					"tags": ["Accessibility", "Ideation", "KPIs", "Performance", "Research", "Usability"]
				},
				{
					"id": "use-and-contribute-to-open-source",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#use-and-contribute-to-open-source",
					"guideline": "Use and contribute to open source",
					"subheading": "Define and maintain an open-source policy and actively contribute to open-source communities through code, time, and financial or in-kind support.",
					"criteria": [
						{
							"title": "Open source governance",
							"description": "Define and maintain processes for the sustainable use and contribution of open-source tools, including selection, approval, and release workflows that prioritize reuse, reduce duplication, and support long-term maintainability."
						},
						{
							"title": "Collaboration and contribution",
							"description": "Collaborate with the open-source ecosystem to support sustainable software development, grounded in open-source principles, and contribute regularly to community-based projects through code, time, or financial support to improve shared maintenance, reuse, and reduce duplication of effort."
						}
					],
					"tags": ["Accessibility", "Assets", "Ideation", "Social Equity", "Software", "UI"]
				},
				{
					"id": "create-a-business-continuity-and-disaster-recovery-plan",
					"url": "https://www.w3.org/TR/web-sustainability-guidelines/#create-a-business-continuity-and-disaster-recovery-plan",
					"guideline": "Create a business continuity and disaster recovery plan",
					"subheading": "Maintain tested incident response plans and communicate transparently with users about service issues, risks, and recovery.",
					"criteria": [
						{
							"title": "Plan of action",
							"description": "Create, maintain, regularly review, and test incident response plans to determine readiness and ensure systems and services can quickly recover from any incident."
						},
						{
							"title": "Audience awareness",
							"description": "Communicate transparently with users about incidents, service issues, and any risks to data or availability."
						}
					],
					"tags": ["AI", "Governance", "Security", "Strategy"]
				}
			]
		}
	]
}