Repository: w3c/sustyweb Branch: main Commit: 5b8defe30e82 Files: 16 Total size: 109.8 KB Directory structure: gitextract_qd2v8w_j/ ├── .gitignore ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE.md ├── README.md ├── Web_Sustainability_GRI_Impact_est.ipynb ├── glance.html ├── ig/ │ ├── charter.html │ └── wg-charter.html ├── index.html ├── intro.html ├── policies.html ├── quickref.html ├── star.html ├── w3c.json └── wg/ └── charter.md ================================================ FILE CONTENTS ================================================ ================================================ FILE: .gitignore ================================================ .DS_Store ================================================ FILE: CODE_OF_CONDUCT.md ================================================ # Code of Conduct All documentation, code and communication under this repository are covered by the [W3C Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/). ================================================ FILE: CONTRIBUTING.md ================================================ > [!WARNING] > This Community Group's activities are now under the direction of the [W3C Sustainable Web Interest Group](https://www.w3.org/groups/ig/sustainableweb/). This includes the curation of the [Web Sustainability Guidelines](https://www.w3.org/TR/web-sustainability-guidelines/). Thank you for supporting us as we reached this stage in our journey and we hope you will continue to support our work as it develops at our new home (where you are welcome to get involved). > > **Note:** If you are seeking an archived draft of our CG reports, please go to our [releases](https://github.com/w3c/sustyweb/releases) page and download the Source code (zip archive) for the assets of a particular version you wish to see. # Contributing This repository is being used for work in the **W3C Sustainable Web Design Community Group**, governed by the [W3C Community License Agreement (CLA)](http://www.w3.org/community/about/agreements/cla/). To make substantive contributions, you must join the [CG](https://www.w3.org/community/sustyweb/). ## Overview This repository is used to develop content for the Web Sustainability Guidelines (WSGs), as well as any supplementary documents. ## Collaboration We welcome content from individuals as well as group efforts and understand that this may pose difficulties for those either unfamiliar with pull requests (on a technical level) or with collaborative efforts (wishing to discuss progress before submitting results). In such cases, members can (if they choose) work with any open format they prefer to collaborate (referring to the specification and its supplements), and submit an issue request containing the URL to the document in question. A moderator (lead or chair) will help translate these requested updates into the living draft specification. ## File Structure The structure of the repository has been created to ensure ease of maintenance. The base directory contains links to all of the compiled files that are public facing such as the [specification](https://www.w3.org/TR/web-sustainability-guidelines/), [at-a-glance](https://w3c.github.io/sustainableweb-wsg/glance.html), [overview](https://w3c.github.io/sustainableweb-wsg/overview.html), [laws & policies](https://w3c.github.io/sustainableweb-wsg/policies.html), [quick reference](https://w3c.github.io/sustainableweb-wsg/quickref.html), [STAR](https://w3c.github.io/sustainableweb-wsg/star.html), [JSON API](https://w3c.github.io/sustainableweb-wsg/guidelines.json) and other supplements such as our draft Test Suite. ``` /ig/charter.html - Working Group Draft Charter glance.html - READ ONLY - At-A-Glance (Public) index.html - READ ONLY - WSG Specification (Public) intro.html - READ ONLY - Summary (Public) overview.pdf - READ ONLY - Project Progress Tracker (Public) policies.html - READ ONLY - Laws & Policies (Public) quickref.html - READ ONLY - Quick Reference (Public) star.html - READ ONLY - STAR (Public) TPAC_Slides.pdf - READ ONLY - W3C TPAC Slides Web_Sustainability_GRI_Impact_est.ipynb - READ ONLY - GRI Impact Calculator ``` When you contribute to our repo, you **MUST** only make changes to documents within the "ig" folders (the sources). Once a PR submission has been reviewed by our group (for quality control purposes), it will either be accepted, or rejected, or further discussion will be required (an issue can be raised for example). Once a PR has been accepted it will be visible within the living draft documents immediately. When enough issues have been collated to warrant a release publication, the necessary documents will be exported through ReSpec into their final HTML form and will replace their static namesakes in the base directory to be versioned as the next public release. Release notes will also be generated by a chair who will verify all submissions before publication. You will notice duplication within the content of our work (as the JSON API for example must reflect the specification). This work is not auto-generated so while we appreciate it if individuals choose to make adjustments to all affected files as required, time commitments may not allow for everyone to do so. As such, if you can only update a single document, as part of the approval process, a moderator (lead or chair) will update all necessary documents to ensure parity with your change. ## Pull Requests If you would like to contribute towards this specification, our primary method is through Pull Requests (PRs). Pull requests (PRs) should be made against the main branch. If you are not the sole contributor to a contribution (pull request), please identify all contributors in the pull request comment. To add a contributor (other than yourself, that's automatic), mark them one per line as follows: ``` +@github_username ``` If you added a contributor by mistake, you can remove them in a comment with: ``` -@github_username ``` If you are making a pull request on behalf of someone else but you had no part in designing the feature, you can remove yourself with the above syntax. ## Issues If you cannot submit a pull request, or if you cannot provide a direct solution, the preferred method is to create a [new issue](https://github.com/w3c/sustyweb/issues/new) with your public comments. You can also comment on any issue threads on [Github Issues](https://github.com/w3c/sustyweb/issues/). You could provide comments on technical errors (bugs) you have uncovered, new guidelines or success criteria you believe should be added, questions you have about existing or future content or an idea for a direction or feature we could utilize. Please check that your question hasn't already been posted first, and provide as much detail as possible (if you have a solution or content to add, it would be very helpful). We're all volunteers so please keep this in mind and try to be civil when commenting about our work. If filing issues in GitHub is not feasible, email our open discussion group [public-sustyweb@w3.org](public-sustyweb@w3.org) ([comment archive](https://lists.w3.org/Archives/Public/public-sustyweb/)). ## Credit All contributors will receive credit (in the specification and our GitHub release notes) if their feedback and ideas make it into the document. Certain exclusions will apply such as those who do not provide their full names or those whose feedback is deemed as invalid, duplicate, or general questions that don't add to the specification or its supplements. ================================================ FILE: LICENSE.md ================================================ All Reports in this Repository are licensed by Contributors under the [W3C Software and Document License](http://www.w3.org/Consortium/Legal/2015/copyright-software-and-document). Contributions to Specifications are made under the [W3C CLA](https://www.w3.org/community/about/agreements/cla/). Contributions to Test Suites are made under the [W3C 3-clause BSD License](https://www.w3.org/Consortium/Legal/2008/03-bsd-license.html) ================================================ FILE: README.md ================================================ > [!WARNING] > This Community Group's activities are now under the direction of the [W3C Sustainable Web Interest Group](https://www.w3.org/groups/ig/sustainableweb/). This includes the curation of the [Web Sustainability Guidelines](https://www.w3.org/TR/web-sustainability-guidelines/). Thank you for supporting us as we reached this stage in our journey and we hope you will continue to support our work as it develops at our new home (where you are welcome to get involved). > > **Note:** If you are seeking an archived draft of our CG reports, please go to our [releases](https://github.com/w3c-cg/sustyweb/releases) page and download the Source code (zip archive) for the assets of a particular version you wish to see. # Web Sustainability Guidelines (WSGs) Welcome to the repository for the [Sustainable Web Design Community Group](https://www.w3.org/community/sustyweb/). In this hub, you will find the draft specification for our [Web Sustainability Guidelines](https://www.w3.org/TR/web-sustainability-guidelines/) and any supplementary documentation, including [Sustainable Tooling And Reporting (STAR)](https://w3c.github.io/sustainableweb-wsg/star.html), our [at-a-glance](https://w3c.github.io/sustainableweb-wsg/glance.html), our [summary](https://w3c.github.io/sustainableweb-wsg/summary.html) of Web Sustainability, our sustainability [laws & policies](https://w3c.github.io/sustainableweb-wsg/policies.html) guide, our [quick reference](https://w3c.github.io/sustainableweb-wsg/quickref.html) sheet, our [PDF checklist](https://w3c.github.io/sustainableweb-wsg/checklist.pdf), our [JSON API](https://w3c.github.io/sustainableweb-wsg/guidelines.json), and our [Test Suite](https://github.com/w3c/sustainableweb-wsg/tree/main/test-suite). We also have a living implementation of the specification under active development called [Sustainable Web Design](https://sustainablewebdesign.org/). If you would like a brief introduction to both our group and our specification, you may find [the slides](https://w3c-cg.github.io/sustyweb/TPAC_Slides.pdf) from the presentation we gave at [TPAC 2023](https://www.w3.org/2023/09/breakouts/recording-32.html) useful. To learn more about our group, its goals, and our progress, check out our [wiki](https://www.w3.org/community/sustyweb/wiki/Main_Page), and [frequently asked questions](https://www.w3.org/community/sustyweb/wiki/Frequently_Asked_Questions) page. --- ## Progress Work is planned in accordance with our [overview](https://w3c-cg.github.io/sustyweb/overview.pdf) of the [issues](https://github.com/w3c-cg/sustyweb/issues) requiring resolution. Each [milestone](https://github.com/w3c-cg/sustyweb/milestones) corresponds to a [release](https://github.com/w3c-cg/sustyweb/releases) published. **Note:** W3C member feedback on our initial [proposed Working Group charter](https://w3c-cg.github.io/sustyweb/ig/wg-charter.html) has lead to many [proposed and planned](https://docs.google.com/presentation/d/1dcuSMLcAF8jTHNCovOfs31zrjCr3rtrwzTXRLSy3lAk/edit?usp=sharing) updates. View current Interest Group chartering efforts: * The [Current AC Poll](https://www.w3.org/2002/09/wbs/33280/SustyWeb/). (W3C Members Only) * Our [Proposed charter](https://www.w3.org/2024/09/sustyweb-charter-202409.html). (Feedback Welcome) * The latest [editor's draft](https://w3c-cg.github.io/sustyweb/ig/charter.html) of our charter. ([DIFF Changelog](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2F2024%2F09%2Fsustyweb-charter-202409.html&doc2=https%3A%2F%2Fw3c-cg.github.io%2Fsustyweb%2Fig%2Fcharter.html)) --- ## Contributing If you would like to contribute towards this specification, please refer to the [CONTRIBUTING.md](CONTRIBUTING.md) document for details. It contains detailed information on pull requests (PRs), submitting issues, and other methods of feedback in relation to this repository. **Note:** Please make your pull requests (including any changes or edits) against files **ONLY** located within the "drafts" or "ig" folders. Also, to make substantive contributions, you must join the [CG](https://www.w3.org/community/sustyweb/). You can also contribute at our monthly meetings. For details, see our [calendar](https://www.w3.org/groups/cg/sustyweb/calendar/) and [meeting minutes](https://docs.google.com/document/d/1nrdxfB076c-91GEDFnZF3wb73QqjJ7rmCVVQiKRNnuY/edit). --- ## JSON API We have a [JSON API](https://w3c.github.io/sustainableweb-wsg/guidelines.json) which is kept in sync with the changes occurring within our specification. This document is reachable via GitHub pages and can be queried using JavaScript to embed our data within your client of choice. The structure of the API is identical to that of the specification in its numbering scheme: `category[1][0].guideline = "Undertake Systemic Impacts Mapping"` --- ## Test Suite We have a [Test Suite](https://github.com/w3c/sustainableweb-wsg/tree/main/test-suite) which is used to showcase machine testability (as denoted in [STAR](https://w3c.github.io/sustainableweb-wsg/star.html)) for the Web Sustainability Guidelines (WSGs). The template structure for the file uses common W3C conventions for test cases to maintain interoperability for tooling that wishes to align our work with their own. Key concepts of note include: - Each title element contains a short identifier for the test. - The rel="author" link element contains details of who created that test. - The rel="help" link element links to the WSG guideline it relates to. - The name="flags" meta element identifies any requirements the test may have such as an external file (**asset**), scripting (**JavaScript**), user-involvement (**interaction**), or if it's trying to disprove something (**invalid**). - The name="assert" meta tag explains which **STAR** technique it relates to by title. - The conditions of passing are what requirements are necessary to pass the technique (and thus the success criteria). ================================================ FILE: Web_Sustainability_GRI_Impact_est.ipynb ================================================ { "nbformat": 4, "nbformat_minor": 0, "metadata": { "colab": { "provenance": [], "authorship_tag": "ABX9TyNeRiUVova28Sct86LUdj6F", "include_colab_link": true }, "kernelspec": { "name": "python3", "display_name": "Python 3" }, "language_info": { "name": "python" } }, "cells": [ { "cell_type": "markdown", "metadata": { "id": "view-in-github", "colab_type": "text" }, "source": [ "\"Open" ] }, { "cell_type": "markdown", "source": [ "This notebook tries to assess environmental impact of W3C Sustainable Web recommendations across a number of categories aligned with GRI reporting.\n", "\n", "As an input it takes a spreadsheet with recommendations and their indicators of impact on reduction of server resource usage, network transfer and end user device usage.\n", "Then it takes data from greenIT.fr report which estimates environmental impact of above categories across material use, water use, energy use and GHG emissions.\n", "It then combines these datasets and estimates comparative impact of given recomendation on different sections of GRI taxonomy." ], "metadata": { "id": "LAiULQzYwhvj" } }, { "cell_type": "code", "execution_count": 1, "metadata": { "id": "p2ZlWXdNbTKj" }, "outputs": [], "source": [ "import gspread\n", "import pandas as pd\n", "from google.colab import auth\n", "from google.colab import files\n", "from google.auth import credentials\n", "from google.auth import default\n", "\n" ] }, { "cell_type": "code", "source": [ "# All the recommendations in the spreadsheet are scored in terms of their impact on end user devices, network and servers in data centre\n", "# Scores are from 0 to MAX_THRESHOLD, by default 2\n", "# If maximum score in the spreadsheet is changed, it needs to updated here\n", "MAX_THRESHOLD = 2\n", "\n", "# Labels to be assigned to metrics\n", "labels = {'Low': MAX_THRESHOLD / 3 ,\n", " 'Moderate': MAX_THRESHOLD / 3 * 2,\n", " 'High': MAX_THRESHOLD }\n", "\n", "# Set to missing if assessment undefined\n", "MISSING = 'Missing'" ], "metadata": { "id": "NaYxpRteOqam" }, "execution_count": 2, "outputs": [] }, { "cell_type": "code", "source": [ "# Auth and read the spreadsheet into pandas\n", "auth.authenticate_user()\n", "creds, _ = default()\n", "gc = gspread.authorize(creds)\n", "\n", "sheet_url = 'https://docs.google.com/spreadsheets/d/12nGydnSv24fvmvCM-665_pFGPG9u3RgTwe1sCz4eiGk'\n", "df = pd.read_csv(sheet_url + '/export?gid=0&format=csv', skiprows=[0, 1])\n", "\n", "df.head(5)" ], "metadata": { "id": "SV8OdvVkbpNf", "colab": { "base_uri": "https://localhost:8080/", "height": 204 }, "outputId": "a0185329-29e0-4bdb-bd9a-0bcbcaff9a84" }, "execution_count": 3, "outputs": [ { "output_type": "execute_result", "data": { "text/plain": [ " Guideline Spec \\\n", "0 Undertake Systemic Impacts Mapping UX \n", "1 Assess And Research Visitor Needs UX \n", "2 Research Non-visitors Needs UX \n", "3 Consider Sustainability In Early Ideation UX \n", "4 Account For Stakeholder Issues UX \n", "\n", " Tags Data Centre Network \\\n", "0 Social Equity\\n Accessibility\\n Ideation\\n Res... 1 1 \n", "1 Social Equity\\n Accessibility\\n UI\\n Patterns\\... 1 1 \n", "2 Social Equity\\n Ideation\\n Research\\n Usabilit... 1 1 \n", "3 UI\\n Ideation\\n Research\\n Software\\n Strategy 0 0 \n", "4 Social Equity\\n Accessibility\\n Ideation\\n Res... 1 1 \n", "\n", " Device Comments \n", "0 1 NaN \n", "1 1 NaN \n", "2 1 NaN \n", "3 0 NaN \n", "4 1 NaN " ], "text/html": [ "\n", "
\n", "
\n", "\n", "\n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", "
GuidelineSpecTagsData CentreNetworkDeviceComments
0Undertake Systemic Impacts MappingUXSocial Equity\\n Accessibility\\n Ideation\\n Res...111NaN
1Assess And Research Visitor NeedsUXSocial Equity\\n Accessibility\\n UI\\n Patterns\\...111NaN
2Research Non-visitors NeedsUXSocial Equity\\n Ideation\\n Research\\n Usabilit...111NaN
3Consider Sustainability In Early IdeationUXUI\\n Ideation\\n Research\\n Software\\n Strategy000NaN
4Account For Stakeholder IssuesUXSocial Equity\\n Accessibility\\n Ideation\\n Res...111NaN
\n", "
\n", "
\n", "\n", "
\n", " \n", "\n", " \n", "\n", " \n", "
\n", "\n", "\n", "
\n", " \n", "\n", "\n", "\n", " \n", "
\n", "
\n", "
\n" ] }, "metadata": {}, "execution_count": 3 } ] }, { "cell_type": "code", "source": [ "\n", "# Impact factors across number of areas split by end user devices, network equipment and data centers\n", "# Source: GreenIT.fr: https://www.greenit.fr/wp-content/uploads/2019/11/GREENIT_EENM_etude_EN_accessible.pdf\n", "data = [ [.6, .63, .83, .75]\n", " , [.23, .22, .09, .16]\n", " , [.17, .15, .07, .08] ]\n", "\n", "factors = pd.DataFrame(data, columns=['Energy', 'Emissions', 'Water', 'Materials'],\n", " index=['Device', 'Network', 'Data Centre'])\n", "\n", "factors.head()\n" ], "metadata": { "colab": { "base_uri": "https://localhost:8080/", "height": 142 }, "id": "fesQf4yAd7La", "outputId": "b9e336c6-5de5-4eca-9419-abbba56596bb" }, "execution_count": 4, "outputs": [ { "output_type": "execute_result", "data": { "text/plain": [ " Energy Emissions Water Materials\n", "Device 0.60 0.63 0.83 0.75\n", "Network 0.23 0.22 0.09 0.16\n", "Data Centre 0.17 0.15 0.07 0.08" ], "text/html": [ "\n", "
\n", "
\n", "\n", "\n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", "
EnergyEmissionsWaterMaterials
Device0.600.630.830.75
Network0.230.220.090.16
Data Centre0.170.150.070.08
\n", "
\n", "
\n", "\n", "
\n", " \n", "\n", " \n", "\n", " \n", "
\n", "\n", "\n", "
\n", " \n", "\n", "\n", "\n", " \n", "
\n", "
\n", "
\n" ] }, "metadata": {}, "execution_count": 4 } ] }, { "cell_type": "code", "source": [ "# Calculate impacts (numerical)\n", "\n", "# GRI-301: Materials\n", "df['GRI-301'] = df['Data Centre'] * factors['Materials']['Data Centre'] \\\n", " + df['Network'] * factors['Materials']['Network'] \\\n", " + df['Device'] * factors['Materials']['Device']\n", "\n", "# GRI-302: Enegry\n", "df['GRI-302'] = df['Data Centre'] * factors['Energy']['Data Centre'] \\\n", " + df['Network'] * factors['Energy']['Network'] \\\n", " + df['Device'] * factors['Energy']['Device']\n", "\n", "# GRI-303: Water\n", "df['GRI-303'] = df['Data Centre'] * factors['Water']['Data Centre'] \\\n", " + df['Network'] * factors['Water']['Network'] \\\n", " + df['Device'] * factors['Water']['Device']\n", "\n", "# GRI-305: Emissions\n", "df['GRI-305'] = df['Data Centre'] * factors['Emissions']['Data Centre'] \\\n", " + df['Network'] * factors['Emissions']['Network'] \\\n", " + df['Device'] * factors['Emissions']['Device']\n", "\n" ], "metadata": { "id": "fWqVehnyb-7I" }, "execution_count": 5, "outputs": [] }, { "cell_type": "code", "source": [ "# Assign labels to calculated impacts\n", "# If assessment for a given recommendation is missing it will be set to MISSING\n", "df['GRI-301 Label'] = df.apply(lambda x: 'Low' if x['GRI-301'] < labels['Low']\n", " else ('Moderate' if x['GRI-301'] < labels['Moderate']\n", " else 'High' if x['GRI-301'] <= labels['High']\n", " else MISSING), axis=1 )\n", "\n", "df['GRI-302 Label'] = df.apply(lambda x: 'Low' if x['GRI-302'] < labels['Low']\n", " else ('Moderate' if x['GRI-302'] < labels['Moderate']\n", " else 'High' if x['GRI-302'] <= labels['High']\n", " else MISSING), axis=1 )\n", "\n", "df['GRI-303 Label'] = df.apply(lambda x: 'Low' if x['GRI-303'] < labels['Low']\n", " else ('Moderate' if x['GRI-303'] < labels['Moderate']\n", " else 'High' if x['GRI-303'] <= labels['High']\n", " else MISSING), axis=1 )\n", "\n", "df['GRI-305 Label'] = df.apply(lambda x: 'Low' if x['GRI-305'] < labels['Low']\n", " else ('Moderate' if x['GRI-305'] < labels['Moderate']\n", " else 'High' if x['GRI-305'] <= labels['High']\n", " else MISSING), axis=1 )\n", "\n", "\n", "df.head()" ], "metadata": { "id": "eY6WRm6jQW6A", "colab": { "base_uri": "https://localhost:8080/", "height": 306 }, "outputId": "5fe21fbd-4de5-4a32-f318-dd86d3b6b5f1" }, "execution_count": 6, "outputs": [ { "output_type": "execute_result", "data": { "text/plain": [ " Guideline Spec \\\n", "0 Undertake Systemic Impacts Mapping UX \n", "1 Assess And Research Visitor Needs UX \n", "2 Research Non-visitors Needs UX \n", "3 Consider Sustainability In Early Ideation UX \n", "4 Account For Stakeholder Issues UX \n", "\n", " Tags Data Centre Network \\\n", "0 Social Equity\\n Accessibility\\n Ideation\\n Res... 1 1 \n", "1 Social Equity\\n Accessibility\\n UI\\n Patterns\\... 1 1 \n", "2 Social Equity\\n Ideation\\n Research\\n Usabilit... 1 1 \n", "3 UI\\n Ideation\\n Research\\n Software\\n Strategy 0 0 \n", "4 Social Equity\\n Accessibility\\n Ideation\\n Res... 1 1 \n", "\n", " Device Comments GRI-301 GRI-302 GRI-303 GRI-305 GRI-301 Label \\\n", "0 1 NaN 0.99 1.0 0.99 1.0 Moderate \n", "1 1 NaN 0.99 1.0 0.99 1.0 Moderate \n", "2 1 NaN 0.99 1.0 0.99 1.0 Moderate \n", "3 0 NaN 0.00 0.0 0.00 0.0 Low \n", "4 1 NaN 0.99 1.0 0.99 1.0 Moderate \n", "\n", " GRI-302 Label GRI-303 Label GRI-305 Label \n", "0 Moderate Moderate Moderate \n", "1 Moderate Moderate Moderate \n", "2 Moderate Moderate Moderate \n", "3 Low Low Low \n", "4 Moderate Moderate Moderate " ], "text/html": [ "\n", "
\n", "
\n", "\n", "\n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", " \n", "
GuidelineSpecTagsData CentreNetworkDeviceCommentsGRI-301GRI-302GRI-303GRI-305GRI-301 LabelGRI-302 LabelGRI-303 LabelGRI-305 Label
0Undertake Systemic Impacts MappingUXSocial Equity\\n Accessibility\\n Ideation\\n Res...111NaN0.991.00.991.0ModerateModerateModerateModerate
1Assess And Research Visitor NeedsUXSocial Equity\\n Accessibility\\n UI\\n Patterns\\...111NaN0.991.00.991.0ModerateModerateModerateModerate
2Research Non-visitors NeedsUXSocial Equity\\n Ideation\\n Research\\n Usabilit...111NaN0.991.00.991.0ModerateModerateModerateModerate
3Consider Sustainability In Early IdeationUXUI\\n Ideation\\n Research\\n Software\\n Strategy000NaN0.000.00.000.0LowLowLowLow
4Account For Stakeholder IssuesUXSocial Equity\\n Accessibility\\n Ideation\\n Res...111NaN0.991.00.991.0ModerateModerateModerateModerate
\n", "
\n", "
\n", "\n", "
\n", " \n", "\n", " \n", "\n", " \n", "
\n", "\n", "\n", "
\n", " \n", "\n", "\n", "\n", " \n", "
\n", "
\n", "
\n" ] }, "metadata": {}, "execution_count": 6 } ] }, { "cell_type": "code", "source": [ "# Save to excel and download locally\n", "\n", "df.to_excel('Recommendations scored.xlsx')\n", "\n", "files.download('Recommendations scored.xlsx')" ], "metadata": { "colab": { "base_uri": "https://localhost:8080/", "height": 17 }, "id": "5FtienoEvf7_", "outputId": "a825f255-4104-4e6a-932f-7ae4fd6c78ef" }, "execution_count": 7, "outputs": [ { "output_type": "display_data", "data": { "text/plain": [ "" ], "application/javascript": [ "\n", " async function download(id, filename, size) {\n", " if (!google.colab.kernel.accessAllowed) {\n", " return;\n", " }\n", " const div = document.createElement('div');\n", " const label = document.createElement('label');\n", " label.textContent = `Downloading \"${filename}\": `;\n", " div.appendChild(label);\n", " const progress = document.createElement('progress');\n", " progress.max = size;\n", " div.appendChild(progress);\n", " document.body.appendChild(div);\n", "\n", " const buffers = [];\n", " let downloaded = 0;\n", "\n", " const channel = await google.colab.kernel.comms.open(id);\n", " // Send a message to notify the kernel that we're ready.\n", " channel.send({})\n", "\n", " for await (const message of channel.messages) {\n", " // Send a message to notify the kernel that we're ready.\n", " channel.send({})\n", " if (message.buffers) {\n", " for (const buffer of message.buffers) {\n", " buffers.push(buffer);\n", " downloaded += buffer.byteLength;\n", " progress.value = downloaded;\n", " }\n", " }\n", " }\n", " const blob = new Blob(buffers, {type: 'application/binary'});\n", " const a = document.createElement('a');\n", " a.href = window.URL.createObjectURL(blob);\n", " a.download = filename;\n", " div.appendChild(a);\n", " a.click();\n", " div.remove();\n", " }\n", " " ] }, "metadata": {} }, { "output_type": "display_data", "data": { "text/plain": [ "" ], "application/javascript": [ "download(\"download_db96e7f6-f5c1-484d-83b8-4c48871b6b04\", \"Recommendations scored.xlsx\", 13991)" ] }, "metadata": {} } ] }, { "cell_type": "code", "source": [], "metadata": { "id": "HNoO30Nqd8_T" }, "execution_count": null, "outputs": [] } ] } ================================================ FILE: glance.html ================================================ Web Sustainability Guidelines (WSG) at a Glance

Redirecting to https://w3c.github.io/sustainableweb-wsg/glance.html

================================================ FILE: ig/charter.html ================================================ Sustainable Web Interest Group Charter

PROPOSED Sustainable Web Interest Group Charter

The mission of the Sustainable Web Interest Group is to improve digital sustainability so that the Web works better for all people and the planet.

This proposed charter is available on GitHub. Feel free to raise issues.

Charter Status Initial Charter
Start date DD Month YYYY
End date DD Month YYYY (2 years)
Chairs Ines Akrap (Storyblok)
Tim Frick (Mightybytes)
Mike Gifford (CivicActions)
Team Contacts Tzviya Siegman (0.25 FTE)
Meeting Schedule Teleconferences: Approximately monthly.
Face-to-face: The environmental impact of travel will be considered when scheduling in-person meetings with accommodations made for virtual attendance. The group expects to meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants.

Motivation and Background

Web sustainability examines how digital technology impacts the physical world using an approach that puts people and the planet first (of critical value in the Ethical Web Principles). Upcoming or existing laws and policies in this sector also set mandatory digital sustainability-related targets. Web sustainability offers many benefits, including accurate measurement and reduction of planetary impact (such as emissions, resource usage, and waste). Web sustainability also includes intersectional issues relating to people (accessibility, privacy, etc.) and shared prosperity (good governance), which can lead to healthier ecosystems overall. PPP (Planet, People, and Prosperity) principles drive these efforts while accounting for a multitude of variables across different disciplines.

This guidance is intended for end-users, stakeholders, website or application creators, tool authors, educators, students, policymakers, purchasing agents, product owners, managers, and decision-makers who will either request or actively implement sustainable change within their organization.

The Sustainable Web Interest Group will provide evidence-led guidance alongside methods to observe, measure, and improve the sustainability of digital products and services. Through this guidance created by web developers, implementers, and other stakeholders of the Internet economy, they may better understand the Internet's impact on various forms of sustainability reporting and evolving implementable holistic practices. This not only includes digital emissions but also interconnecting variables that can additionally impact digital sustainability. To address these challenges, designers, developers, and product teams can apply stewardship principles to digital products, services, and data delivered via the Internet.

Scope

The Sustainable Web Interest Group develops and documents guidelines, patterns, processes, and best practices (along with supporting materials) for addressing sustainability issues within digital technology affecting both people and the planet.

The group provides coverage for websites & web applications, authoring tools & user agents, user experience design, web development (and tooling), hosting & infrastructure, business & product strategy, and metrics data (concerning research, statistics for measurability, and related weighting of the guidelines).

The Interest Group will focus on the following activities:

  • Publishing a set of guidelines (based upon the CG Draft Report).
  • Working with regulatory and standards groups to improve compliance targets within our work.
  • Improving measurability (how guidelines are endorsed and weighted through quantitative data) to provide more accurate advice within published deliverables.
  • Creating educational materials to foster wider adoption of the guidelines.

The Interest Group may recommend mitigations for sustainability issues in existing features of the Web platform, up to and including their deprecation.

The Interest Group may recommend methods to reduce emissions that reinforce (but don't replace) existing beneficial practices (Accessibility, Performance, Privacy, Security, etc).

Out of Scope

  • Non-web aspects of native applications in both mobile & desktop environments: However, Web applications remain in scope.
  • Hardware: Unless related to hosting & infrastructure, we will not provide coverage of the manufacturing or usage of products beyond the remit of Internet usage.

Deliverables

Updated document status is available on the group publication status page.

Draft state indicates the state of the deliverable at the time of the charter approval. Expected completion indicates when the deliverable is projected to become a Group Note, or otherwise reach a stable state.

Guidelines

The Interest Group will deliver the following guidelines:

Web Sustainability Guidelines (WSG)

These guidelines explain how to design and implement digital products and services that put people and the planet first. The guidelines are best practices based on measurable, evidence-based research; aimed at end-users, web designers, web developers, stakeholders, tool authors, educators, and policymakers.

Draft state: Adopted from Draft CG Report

Expected completion: [Q1-4 YYYY]

Other Deliverables

The Group expects to create these deliverables:

  • At-A-Glance & Introductory documents offering signposting to the group's work.
  • Quick Reference & Checklist which provide a compact list of the WSG's.
  • Laws & Policies document overviews related regulatory and best practice policies.
  • STAR evaluation methodologies, techniques (case studies), and test suite (metrics).
  • JSON API to facilitate third-party implementation of the guidelines.

In addition, the group may work on:

  • Educational materials to promote adoption.
  • Translations.

Note: While limited support for browser developers (user agents) and authoring tools currently exists, the inclusion of materials for such groups in the future is within the scope of this Interest Group.

Success Criteria

  • Request the publication of the WSGs as a W3C Statement.
  • Provide guidance based upon evidence (where possible), and if evidence is lacking; use industry best practices, develop measurability data, or conduct research to validate claims.
  • Where machine testing of sustainability features is possible, seek interoperable implementations. Where machine-testability is not possible (due to the nature of their function), indicate this in the deliverables.
  • Offer guidance across multiple disciplines of existing web technologies and expertise, and provide well-defined goals that benefit the wide spectrum of sustainability.
  • Align published guidance with existing regulatory requirements to increase compliance levels.

This Interest Group expects to follow the TAG Web Platform Design Principles.

Coordination

For all guidelines, this Interest Group will seek horizontal review for accessibility, internationalization, privacy, and security with the relevant Working and Interest Groups, and with the TAG. The Interest Group is encouraged to engage collaboratively with the horizontal review groups throughout development of the guidelines. The Interest Group is advised to seek a review at least 3 months before any request to advance a Note to W3C Statement.

Additional technical coordination with the following Groups will be made, per the W3C Process Document:

W3C Groups

Accessibility Guidelines Working Group
For guideline modeling and WSG interoperability.
Web Performance Working Group
For guideline interoperability with reducing resource waste.
Sustainable Web Design Community Group
The Sustainable Web Interest Group will maintain an ongoing, collaborative relationship with the current Sustainable Web Design Community Group in order to facilitate knowledge sharing and continuous learning for participants of both groups. This will improve the quality of deliverables for both groups.

External Organizations

As an emerging and rapidly growing field of knowledge, digital sustainability expertise comes from many places. The Interest Group recognizes that numerous organizations around the world focus on similar or adjacent topics. We have identified the below as early partners whose expertise and willingness to collaborate will support our success.

Green Software Foundation
Help align with sustainability targets.
Green Web Foundation
Help align with sustainability targets.
UNEP CODES
Help align with sustainability targets.

We will also monitor the work of and where appropriate collaborate with standards bodies (external to the W3C) such as those listed below as their work relates to the compliance adherence work we are including within the deliverables.

Global Reporting Initiative
Help align with sustainability targets.
IETF Environmental Impacts of Internet Technology
Co-ordination and collaboration on documents.
International Standards Organization
Help align with sustainability targets.

Participation

To be successful, this Interest Group is expected to have 6 or more active participants for its duration, including representatives from the key users of the guidelines, and active Editors and Test Leads. The Chairs, Editors, and Test Leads are expected to contribute half of a working day per week towards the Interest Group. There is no minimum requirement for other Participants.

The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in Communication.

The group also welcomes non-Members to contribute technical submissions for consideration, although active contributors are expected to join the group.

Participants in the group are required (by the W3C Process) to follow the W3C Code of Conduct.

Communication

Technical discussions for this Interest Group are conducted in public: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts will be developed in public repositories and may permit direct public contribution requests. The meetings themselves are not open to public participation, however, information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the Sustainable Web Interest Group home page.

Most Sustainable Web Interest Group teleconferences will be conducted on an as-needed basis.

This group primarily conducts its technical work on GitHub issues. The public is invited to review, discuss and contribute to this work. This group also uses utilizes the public mailing list public-[email-list]@w3.org (archive) for event notifications and important announcements.

The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and participants of the group, for Member-confidential discussions in special cases when a participant requests such a discussion.

Decision Policy

This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 5.2.1, Consensus). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with participants of the group and other reviewers, and consensus emerges with little formal voting being required.

However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.

To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Interest Group.

All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs.

This charter is written in accordance with the W3C Process Document (Section 5.2.3, Deciding by Vote) and includes no voting procedures beyond what the Process Document requires.

Patent Disclosures

The Interest Group provides an opportunity to share perspectives on the topic addressed by this charter. W3C reminds Interest Group participants of their obligation to comply with patent disclosure obligations as set out in Section 6 of the W3C Patent Policy. While the Interest Group does not produce Recommendation-track documents, when Interest Group participants review Recommendation-track specifications from Working Groups, the patent disclosure obligations do apply. For more information about disclosure obligations for this group, please see the licensing information.

Licensing

This Interest Group will use the W3C Software and Document license for all its deliverables.

About this Charter

This charter has been created according to section 3.4 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.

Charter History

The following table lists details of all changes from the initial charter, per the W3C Process Document (section 4.3, Advisory Committee Review of a Charter):

Charter Period Start Date End Date Changes
Initial Charter DD Month YYYY DD Month YYYY None

Change log

Changes to this document are documented in this section.


================================================ FILE: ig/wg-charter.html ================================================ Sustainable Web Working Group Charter

PROPOSED Sustainable Web Working Group Charter

The mission of the Sustainable Web Working Group is to improve sustainability so the Web works better for all people and the planet.

This proposed charter is available on GitHub. Feel free to raise issues.

Charter Status Initial Charter
Start date DD Month YYYY
End date DD Month YYYY
Chairs Ines Akrap (Storyblok)
Tim Frick (Mightybytes)
Mike Gifford (CivicActions)
Team Contacts Carine Bournez (.25 FTE)
Meeting Schedule Teleconferences: Approximately monthly.
Face-to-face: The environmental impact of travel will be considered when scheduling in-person meetings with accommodations made for virtual attendance. The group expects to meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants.

Motivation and Background

The vision of the Sustainable Web Working Group is to provide evidence-led guidance alongside methods to observe, measure, and improve the sustainability of digital products and services. Through this guidance created by web developers, implementers, and other stakeholders of the Internet economy, they may better understand the internet's impact on various forms of sustainability reporting and evolving ESG (Environmental, Social, Governance) practices. This not only includes digital emissions, but also interconnecting variables which can additionally impact digital sustainability. To address these challenges, designers, developers, and product teams can apply stewardship principles to digital products, services, and data delivered via the internet.

Scope

This group pursues the following sustainability goals:

  • Reducing global carbon emissions.
  • Reducing consumption of energy and material resources.
  • Improving resilience of digital products and businesses.

The Working Group discusses many use cases to determine how standards - both those focused on (and shaped by) sustainability can benefit the industry, including:

  • Wider adoption of guidelines to reduce carbon emissions and resource use.
  • Existing regulatory (CSRD etc) and standards (GRI) compliance to reach a wider global audience.
  • Methods to reduce emissions reinforce (but don't replace) existing beneficial practices (Accessibility, Performance, Privacy, Security, etc).
  • Broader interoperability, compatibility, and stability within the Web ecosystem.

The Sustainable Web Working Group develops guidelines and supporting materials that address how the following topics relate to the above sustainability goals:

  • Websites & Web Applications: User-facing digital products, services, and websites.
  • Authoring Tools & User Agents: Tools which directly interact with the Internet.
  • User Experience Design: Processes by which digital products or services are designed and created.
  • Metrics Data: Sustainability research analytics, ratings, and emissions or resource calculations.
  • Hosting & Infrastructure: Within the remit of transmitting, delivering, or managing digital assets.
  • Business: In relation to the creation or management of digital teams and assets.

Out of Scope

The following features are out of scope, and will not be addressed by this group.

  • Non-web aspects of native applications in both mobile & desktop environments: However, Web applications remain in scope.
  • Hardware: Unless denoted through in-scope section on Hosting & Infrastructure, we will not provide coverage of the manufacturing or usage of products beyond the remit of Internet-usage.
  • Horizontal Reviews: This working group will not conduct horizontal reviews of other groups' specifications.

Deliverables

Updated document status is available on the group publication status page.

Draft state indicates the state of the deliverable at the time of the charter approval. Expected completion indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.

Normative Specifications

The Working Group will deliver the following W3C normative specifications:

Web Sustainability Guidelines (WSG) 1.0

This specification explains how to design and implement digital products and services that put people and the planet first. The guidelines are best practices based on measurable, evidence-based research; aimed at end-users, web workers, stakeholders, tool authors, educators, and policymakers.

Draft state: Adopted from Draft CG Report

Expected completion: [Q1-4 yyyy]

Note: The Sustainable Web Design Community Group has taken a holistic approach to sustainability, encompassing environmental, social, and economic (ESG) considerations (see, for example United Nations, US Gov [Sustainability], NYPA, UK Gov [Defra]). This broad approach has the advantage of aligning with some regulatory expectations (Laws & Policies) and creating a framework that is more likely to achieve success by extending beyond code and hardware to people and practices. The scope of the Working Group charter is narrower than that of the Community Group, and as a result, the Community Group anticipates that some of the guidelines of the Community Group's initial report will not be part of a future Recommendation. The Community Group may continue to leverage some of the material not taken up by the Working Group in order to support the future Recommendation, for example through good practice documentation.

Other Deliverables

The Working Group will publish additional resources, not on the Recommendation Track:

  • At-A-Glance & Introductory documents offering signposting to the group's work.
  • Quick Reference & Checklist which provide a compact list of the WSG's.
  • STAR evaluation methodologies, techniques (case studies), and test suite (metrics).
  • JSON API that actively encourages third-party implementation of our work.

The Working Group may publish additional supporting resources not on the Recommendation Track:

  • Educational materials to promote adoption.
  • Translations.

Note: While limited support for browser developers (user-agents) and authoring tools currently exists, the inclusion of materials for such groups in the future is within the scope of this Working Group.

Success Criteria

In order to advance to Proposed Recommendation, each normative specification is expected to have at least two independent interoperable implementations of every feature defined in the specification, where interoperability can be verified by passing open test suites, and two or more implementations interoperating with each other. In order to advance to Proposed Recommendation, each normative specification must have an open test suite of every feature defined in the specification.

There should be testing plans for each specification, starting from the earliest drafts.

To promote interoperability, all changes made to specifications in Candidate Recommendation or to features that have deployed implementations should have tests. Testing efforts should be conducted via the Web Platform Tests project.

Each specification should contain sections detailing all known security and privacy implications for implementers, Web authors, and end users.

Each specification should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and recommendations for maximising accessibility in implementations.

This Working Group expects to follow the TAG Web Platform Design Principles.

Coordination

For all specifications, this Working Group will seek horizontal review for accessibility, internationalization, privacy, and security with the relevant Working and Interest Groups, and with the TAG. Invitation for review must be issued during each major standards-track document transition, including FPWD. The Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of each specification. The Working Group is advised to seek a review at least 3 months before first entering CR and is encouraged to proactively notify the horizontal review groups when major changes occur in a specification following a review.

Additional technical coordination with the following Groups will be made, per the W3C Process Document:

W3C Groups

Accessibility Guidelines Working Group
For specification guideline modeling and WSG interoperability.
Web Performance Working Group
For guideline interoperability with reducing resource waste.
Sustainable Web Design Community Group
The Sustainable Web Working Group will maintain an ongoing, collaborative relationship with the current Sustainable Web Design community group in order to facilitate knowledge sharing and continuous learning for members of both groups. This will improve the quality of deliverables for both groups.

External Organizations

As an emerging and rapidly growing field of knowledge, digital sustainability expertise comes from many places. The Working Group recognizes that numerous organizations around the world focus on similar or adjacent topics. We have identified the three below as early partners whose expertise and willingness to collaborate will support our success.

Green Software Foundation
Help the WSGs meet sustainability targets.
Green Web Foundation
Help the WSGs meet sustainability targets.
UNEP CODES
Help the WSGs meet sustainability targets.

Participation

To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants.

The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in Communication.

The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the W3C Patent Policy.

Participants in the group are required (by the W3C Process) to follow the W3C Code of Conduct.

Communication

Technical discussions for this Working Group are conducted in public: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests. The meetings themselves are not open to public participation, however.

Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the Sustainable Web Working Group home page.

Most Sustainable Web Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.

This group primarily conducts its technical work on GitHub issues. The public is invited to review, discuss and contribute to this work. This group also uses utilizes the public mailing list public-[email-list]@w3.org (archive) for event notifications and important announcements.

The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.

Decision Policy

This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 5.2.1, Consensus). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.

However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.

To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.

All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs.

This charter is written in accordance with the W3C Process Document (Section 5.2.3, Deciding by Vote) and includes no voting procedures beyond what the Process Document requires.

Patent Policy

This Working Group operates under the W3C Patent Policy (Version of 15 September 2020). To promote the widest adoption of Web standards, W3C seeks to issue Web specifications that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the licensing information.

Licensing

This Working Group will use the W3C Software and Document license for all its deliverables.

About this Charter

This charter has been created according to section 3.4 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.

Charter History

The following table lists details of all changes from the initial charter, per the W3C Process Document (section 4.3, Advisory Committee Review of a Charter):

Charter Period Start Date End Date Changes
Initial Charter [dd monthname yyyy] [dd monthname yyyy] none

Change log

Changes to this document are documented in this section.


================================================ FILE: index.html ================================================ Web Sustainability Guidelines (WSG)

Redirecting to https://www.w3.org/TR/web-sustainability-guidelines/

================================================ FILE: intro.html ================================================ Summary of Web Sustainability

Redirecting to https://w3c.github.io/sustainableweb-wsg/summary.html

================================================ FILE: policies.html ================================================ Web Sustainability Laws & Policies

Redirecting to https://w3c.github.io/sustainableweb-wsg/policies.html

================================================ FILE: quickref.html ================================================ Quick Reference for Web Sustainability Guidelines (WSG)

Redirecting to https://w3c.github.io/sustainableweb-wsg/quickref.html

================================================ FILE: star.html ================================================ Sustainable Tooling And Reporting (STAR)

Redirecting to https://w3c.github.io/sustainableweb-wsg/star.html

================================================ FILE: w3c.json ================================================ { "group": [62441] , "contacts": ["ijacobs"] , "repo-type": "cg-report" } ================================================ FILE: wg/charter.md ================================================ Superseded by the [draft Sustainable Web IG charter](https://w3c.github.io/sustyweb/ig/charter.html).