The WSG-o-matic

Basic Information

Organisation: wsg-o-matic
Website or application: The WSG-o-matic
Address of product or service: https://wsg-o-matic.com/
Publication date: 2026-09-04
Overall conformance: Partially conformant: some parts of the content do not fully conform to the below.
Phone: n/a
E-mail: morgan+sustainability@morganwebdev.com
Address: https://github.com/airbr/wsg
Other contact options: https://github.com/airbr/wsg
Typical duration for response: 7 business days
Additional sustainability considerations: Some has not been tested, some has been quickly assessed, this is in progress.
Greenwashing declaration: Yes: the content does not contain any greenwashing or claims that cannot be reinforced with evidence without any exceptions.

Approval and Complaints Process

Formal complaints procedure: Please, if you find any error or apparent mistake in this report, let me know so I can log it and assess myself. Thank you so much in advance!
Approved by: Morgan Murrah
Position or function: Chief volunteer

Application of Sustainability

The organisation's sustainability practices are assessed against the below best practices, standards and legislation:

W3C Web Sustainability Guidelines (WSG)

Summary

The assessment contains 196 Web Sustainability Guidelines criteria.

Result	Number
Fully conformant	105
Partially conformant	16
Non conformant	6
Non present	0
Unable to assess	0
Not checked	69

Web Sustainability Guidelines

User Experience Design

Criterion	Result	Observations
2.1 - Identify, assess, disclose, review, and mitigate sustainability impacts
Impact analysis	Fully conformant	wsg-o-matic was created with the WSG's themselves in mind in its early design and updates. From the start I considered the potential footprint.
External impact	Fully conformant	This website was created with broad inspiration to limit impact on people and the planet. It uses local copies of JSON resources and minimal scripts to operate the app only, no trackers or data is sent from the app.
2.2 - Understand user requirements or constraints
Audience evaluation	Fully conformant	The use case resonated and was practical. For example, a way of simplifying things for an overwhelmed user, wanting a way to get started with the large works of the standard may benefit from a random or topic based selection to get started. Someone wanting to randomly re-visit. Potentially other use cases.
2.3 - Integrate sustainability into every stage of the ideation process
Sustainable brand development	Fully conformant	This website keeps in mind the credit it has been given and to give credit back to the W3C Sustainable web participants who made the data that made this possible. Official JSON is the only data loaded, from the domain itself.
Wireframes and prototypes	Fully conformant	The visual design for example is very simple, and has consisted of a button and a Package emoji for a box to unbox the random choice of WSG. I would wireframe any future changes that were major.
Participation and testing	Fully conformant	I shared this in early versions and made this open source early in the project.
Environmental ideation	Fully conformant	The non-user case of data sent over the wire in terms of network traffic was considered. The data in the form of JSON is therefore cached when caching is available, so on repeat visits and interactions with the app it does not cause the file to be sent over a network instead it is just accessing locally.
2.4 - Design efficient and streamlined user journeys
Efficient paths	Fully conformant	The call to action is immediately able to be activated, presenting a random guideline in seconds or if with URL params instantly. Tested on a screen reader (VoiceOver) seemed to be fine.
Patterns for efficiency	Fully conformant	This is not always obvious but the large clickable and focusable button give it some pattern of simplicity.
Content discovery	Partially conformant	No current human readable Sitemap? or sitemap.xml either? Its a single page. There is a return to home link at the top of the page, after the loaded JSON is activated.
2.5 - Design to assist and not to distract
Respect user attention	Fully conformant	Yes - at September 4 2026.
Distraction-free design	Fully conformant	Yes - at September 4 2026.
Remove engagement traps	Fully conformant	Yes - at September 4 2026.
2.6 - Avoid being manipulative or deceptive
Deceptive design patterns	Fully conformant	Yes - at September 4 2026.
Advertisements	Fully conformant	Yes - at September 4 2026.
Analytics and tracking	Fully conformant	Yes, no trackers of any kind - at September 4 2026.
Search Engine Optimization	Fully conformant	Yes - at September 4 2026.
2.7 - Make deliverables understandable and reusable
Deliverables reusability	Fully conformant	Tracked in GitHub
Deliverables documentation	Fully conformant	README.md updated.
Deliverables readability	Fully conformant	Yes - at September 4 2026.
2.8 - Use a design system for interface consistency
Design system	Partially conformant	Not sure if design systems were really said to be used, but many design features were considered. Seems not applicable.
2.9 - Optimize media to reduce resource use
Need for media	Fully conformant	Yes - at September 4 2026.
Optimized media	Fully conformant	Yes - at September 4 2026.
Lazy loading	Fully conformant	Yes - at September 4 2026.
User-controlled media	Fully conformant	Yes - at September 4 2026.
Media management and use	Non conformant	Did not do this... Can do in future. No - at September 4 2026.
2.10 - Ensure animation is proportionate and easy to control
Need for animation	Fully conformant	Small amount of optional bouncing animation used to draw attention to the CTA. This is used with prefers reduced motion media query.
Avoiding overburdening	Fully conformant	Yes, at September 4 2026
Control animation	Partially conformant	None
Efficient animation	Fully conformant	Yes, at September 4 2026
2.11 - Use optimized web typography
Pre-installed typefaces	Fully conformant	Yes, at September 4 2026
Web font optimization	Fully conformant	Yes, at September 4 2026
Web font subsetting	Fully conformant	Yes, at September 4 2026
2.12 - Avoid unwanted notifications
Need for notification	Fully conformant	No notifications used
Notification settings	Fully conformant	No notifications used
2.13 - Reduce the impact of downloadable and physical documents
Printed documents	Fully conformant	None
Optimized documents	Non conformant	None
Optimized delivery	Non conformant	None
Labels and choice	Non conformant	None
2.14 - Involve users early in the project
Early user testing	Fully conformant	None
2.15 - Audit and test for bugs or issues requiring resolution
Ongoing evaluation	Fully conformant	Yes, at September 4 2026
Automated tests	Fully conformant	Includes Lighthouse, Arc Toolkit, W3C Validator
Performance testing	Fully conformant	Includes Lighthouse, Yellow Lab Tools
2.16 - Validate usability through testing and real-world usage
Usage changes	Fully conformant	None
Usability testing	Non conformant	Hmm... didnt really do this.
2.17 - Provide cross-platform compatibility support
Compatibility documentation	Fully conformant	HTML5, CSS, JS used only, and local to the domain.
Maintaining compatibility	Fully conformant	Yes, at September 4 2026
User constraints	Fully conformant	Yes, tested on CPU Slowdown and a variety of device profiles. Yes, at September 4 2026

Web Development

Criterion	Result	Observations
3.1 - Set goals based on performance and energy impact
Performance goals	Fully conformant	None
Energy intensity	Fully conformant	None
3.2 - Minify and remove unused code
Minified code	Fully conformant	None
Remove redundancy	Fully conformant	None
3.3 - Modularize bandwidth-heavy components
Code splitting	Fully conformant	None
3.4 - Avoid redundancy and duplication in code
Remove or simplify	Fully conformant	None
Iteration over recreation	Fully conformant	None
Organize code arrangement	Fully conformant	None
3.5 - Treat third parties the same as first parties
Assess and reduce	Fully conformant	None
Third-party implementation	Fully conformant	None
Self-hosting	Fully conformant	None
Third-party preferences	Fully conformant	None
3.6 - Ensure code follows good semantic practices
Semantic code	Fully conformant	None
Optional features	Fully conformant	None
Non-standard code	Fully conformant	None
Custom code	Fully conformant	None
3.7 - Defer the loading of non-critical resources
Asynchronous code	Fully conformant	None
Optimized loading	Fully conformant	None
3.8 - Structure metadata for machine readability
Required elements	Fully conformant	Yes, at September 4 2026
Meta tags	Fully conformant	Yes, at September 4 2026
Structured data	Partially conformant	None
3.9 - Use media queries that support sustainability goals
Media and preference queries	Fully conformant	None
3.10 - Ensure layouts work for different devices and requirements
Device-adaptable	Fully conformant	None
Progressive enhancement	Partially conformant	None
Carbon-aware design	Fully conformant	None
Alternative browsing	Fully conformant	None
3.11 - Use sustainable JavaScript and APIs
Sustainable JavaScript	Fully conformant	None
Energy-relevant APIs	Fully conformant	None
API requests	Fully conformant	None
3.12 - Use dependencies sparingly and maintain them
Dependency management	Fully conformant	None
Dependency necessity	Fully conformant	None
Dependency updates	Fully conformant	None
3.13 - Include expected and beneficial files
Expected files	Partially conformant	None
Beneficial files	Partially conformant	None
3.14 - Use the most efficient solution for your service
Appropriate Implementation	Fully conformant	None
Optimized methodology	Fully conformant	None
Static over dynamic	Fully conformant	None
Extensions and plugins	Fully conformant	None
Interface components	Fully conformant	None
3.15 - Use the latest stable language version
Versioning	Partially conformant	Not really a lot of structure to the version status - Taken a note to improve! September 4 2026
Language choice	Fully conformant	None
3.16 - Reduce the number and complexity of database queries
Efficient database querying	Fully conformant	None
Reuse of retrieved data	Fully conformant	None
Data minimization in queries	Fully conformant	None
Data lifecycle controls	Fully conformant	None

Hosting, Infrastructure, and Systems

Criterion	Result	Observations
4.1 - Use sustainable hosting
Provider selection	Fully conformant	None
Efficient operation	Fully conformant	None
Equipment longevity	Fully conformant	None
Low-carbon electricity	Fully conformant	None
Remaining emissions	Fully conformant	None
Domain names	Fully conformant	None
4.2 - Optimize caching and support offline access
Caching resources	Fully conformant	None
Offline access	Non conformant	None
4.3 - Reduce data transfer with compression
Server-side compression	Partially conformant	Not sure what is being used...
Media compression	Fully conformant	None
4.4 - Setup necessary error pages and redirection links
Error pages	Fully conformant	None
Redirection	Fully conformant	None
4.5 - Avoid maintaining unnecessary virtualized environments or containers
Unused environments	Fully conformant	None
4.6 - Use automation wisely
Task automation	Partially conformant	None
Necessary tasks	Partially conformant	None
Automated scaling	Partially conformant	None
Suspicious activity management	Partially conformant	None
4.7 - Define the frequency of data refreshes
Refresh frequency	Fully conformant	None
4.8 - Back up critical data at routine intervals
Data backups	Partially conformant	None
4.9 - Assess the impact and requirements of data processing
Carbon shifting	Fully conformant	None
Protocol efficiency	Fully conformant	None
Event-driven architecture	Fully conformant	None
Data processing efficiency	Fully conformant	None
Efficient location	Fully conformant	None
4.10 - Use Content Delivery Networks (CDNs) when beneficial
Global CDNs	Fully conformant	None
Sustainability commitment	Fully conformant	None
Inappropriate resources	Fully conformant	None
4.11 - Ensure infrastructure fits project requirements
Lowest requirements	Fully conformant	None
4.12 - Store data according to the needs of your users
Remove unused data	Fully conformant	None
Lifecycle management	Fully conformant	None
Efficient storage	Fully conformant	None
Optimized logging	Partially conformant	None
Asset downloads	Partially conformant	None

Business Strategy and Product Management

Criterion	Result	Observations
5.1 - Have an ethical and sustainable product strategy
Public documents	Not checked	None
Achievements and compliance	Not checked	None
Governance over time	Not checked	None
Technology legislation	Not checked	None
5.2 - Assign a sustainability advocate
Advocate for sustainability	Not checked	None
5.3 - Inform, raise awareness, and train for sustainability
Inform and aware	Not checked	None
Routine training	Not checked	None
Active participation	Not checked	None
Training materials	Not checked	None
Incentivize progress	Not checked	None
5.4 - Communicate the environmental impact of user choices
Communication of impact	Not checked	None
5.5 - Calculate the environmental impact
Life-cycle assessment	Not checked	None
Competitor impact	Not checked	None
Tooling impact	Not checked	None
5.6 - Define clear organizational sustainability goals and metrics
Web sustainability goals	Not checked	None
5.7 - Validate web sustainability efforts through external verification
Obtaining verification	Not checked	None
Maintaining verification	Not checked	None
5.8 - Support mandatory disclosures and reporting
Policies and practices	Not checked	None
Impact reports	Not checked	None
Disclosure reporting	Not checked	None
Impact reduction	Not checked	None
5.9 - Create one or more impact business models
Theory of change	Not checked	None
5.10 - Follow a product management and maintenance strategy
Management and maintenance	Not checked	None
Planning Strategy	Not checked	None
Resourcing products	Not checked	None
Resource measurement	Not checked	None
Failure indicators	Not checked	None
5.11 - Implement continuous improvement procedures
Continuous improvement	Not checked	None
Retrospectives conducted	Not checked	None
Iterative consideration	Not checked	None
Functionality decisions	Not checked	None
5.12 - Document updates and evolutions
Feature changes	Fully conformant	Version control used in GitHub: https://github.com/airbr/wsg
5.13 - Evaluate if a digital product or service is necessary
Sustainable Development Goals	Not checked	None
Creation evaluation	Not checked	None
Obstacle consideration	Not checked	None
5.14 - Provide a supplier standards of practice document
Vetting potential partners	Not checked	None
Collaborative measurement	Not checked	None
Informative partner promotion	Not checked	None
5.15 - Share economic benefits
Living wage	Not checked	None
Incentivisation	Not checked	None
Employee benefits	Not checked	None
5.16 - Share decision-making power with affected parties
Decision-making	Not checked	None
5.17 - Use Diversity, Equity, Justice, Inclusion (DEJI) practices
DEJI practices	Not checked	None
DEJI training	Not checked	None
DEJI improvements	Not checked	None
5.18 - Promote responsible data practices
Data practices	Not checked	None
Data ownership	Not checked	None
Outdated content	Not checked	None
5.19 - Establish responsible practices around AI and emerging or disruptive technologies
AI (Artificial Intelligence) and data collection	Not checked	None
Business adaptation	Not checked	None
Environmental responsibilities	Not checked	None
Automated tooling	Not checked	None
Quantum resilience	Not checked	None
5.20 - Adopt responsible financial practices
Fuel divestment	Not checked	None
Responsible finance	Not checked	None
5.21 - Adopt organizational philanthropy practices
Philanthropy policy	Not checked	None
Voluntary work	Not checked	None
5.22 - Plan for a digital product or service's care and end-of-life
End-of-life care	Not checked	None
5.23 - Repair, reuse, refurbish, recycle or reduce e-waste
E-waste management	Not checked	None
E-waste policy	Not checked	None
Refurbishment strategy	Not checked	None
Right to repair	Not checked	None
5.24 - Define performance, environmental, and human budgets
Environmental budget	Not checked	None
Performance budget	Not checked	None
Human budget	Not checked	None
Measurable improvements	Not checked	None
5.25 - Use and contribute to open source
Open source governance	Not checked	None
Collaboration and contribution	Not checked	None
5.26 - Create a business continuity and disaster recovery plan
Plan of action	Not checked	None
Audience awareness	Not checked	None