The Square · Transparency Log

Vol. 01 · No. 01

Digital Responsibility Report

Every design decision has a reason.

This website was intentionally designed to minimise environmental impact, maximise accessibility and deliver an exceptional experience for every visitor.

Version
1.0
Last audit
July 2026
Published from
Lisbon
Maintained by
The Square × Venga
Standard
WCAG 2.2 AA

§ 02

Scorecard

Six measures of a responsible website.

Placeholder values, to be reconciled with each Lighthouse and third-party audit. Updated per release.

Accessibility

WCAG 2.2 AA
98/ 100

Measured against WCAG 2.2 AA criteria. Covers contrast, keyboard operability, semantic structure and assistive-technology support.

Performance

Core Web Vitals
100/ 100

Lighthouse performance score on a mid-range mobile profile. Reflects rendering speed, interactivity and layout stability.

SEO

Indexable
100/ 100

Semantic markup, per-route metadata, canonical tags and structured data ensure the site is fully discoverable.

Best Practices

Verified
100/ 100

HTTPS, safe browsing, modern APIs and no console errors. Vendored libraries kept to a minimum.

Privacy

No tracking cookies
Excellent

No third-party analytics, no advertising trackers, no fingerprinting. Sessions are anonymous by default.

Digital Sustainability

Website Carbon
Pendingaudit

Awaiting third-party audit via Website Carbon Calculator. Interim estimate: cleaner than 82% of pages tested.

Note · Scores are placeholders until connected to live Lighthouse and accessibility audits.

§ 03

Principles

Six commitments we hold ourselves to.

01Reviewed Jul 2026

Accessibility First

Every component is designed for keyboard, screen reader and reduced-motion users before it is designed for anyone else.

In production
02Reviewed Jul 2026

Performance by Default

No feature ships if it degrades Core Web Vitals. Budgets are enforced at build time, not after launch.

In production
03Reviewed Jul 2026

Privacy by Design

We collect the minimum data necessary. No behavioural profiling, no third-party cookies, no dark patterns.

In production
04Reviewed Jul 2026

Editorial Simplicity

Typography leads. Imagery supports. Interfaces are quiet so that ideas can be loud.

In production
05Reviewed Jul 2026

Sustainable Engineering

Fewer requests, smaller payloads, longer cache lifetimes. Every kilobyte is a decision.

In production
06Reviewed Jul 2026

Continuous Improvement

This report is a living document. Each release is measured against the previous one.

Ongoing

§ 04

Performance

A technical report, not a dashboard.

Field values reflect a mid-range mobile profile on a 4G connection. Targets are the internal budgets we build against.

Largest Contentful Paint
1.2s
< 2.5s
Good
Time to render the largest visible element.
Interaction to Next Paint
84ms
< 200ms
Good
Responsiveness to user input across the session.
Cumulative Layout Shift
0.02
< 0.1
Good
Visual stability of the page as it loads.
Page Weight
≈ 480 KB
< 1 MB
Good
Total transferred bytes for a first visit to the homepage.
Image Optimisation
AVIF + WebP
Modern formats
Good
Responsive sources with modern codecs and lazy loading.
Request Count
24
< 50
Good
Number of network requests to render the initial view.
Font Loading
Variable, subset
Single file
Good
One variable font, subset to Latin ranges, self-hosted.
Caching Strategy
Immutable, 1y
≥ 30d
Good
Static assets fingerprinted and cached aggressively at the edge.
JavaScript Budget
≈ 140 KB gz
< 200 KB gz
Good
Route-split bundles. Vendor code isolated and cache-stable.
CSS Budget
≈ 22 KB gz
< 40 KB gz
Good
Utility-first stylesheet, purged in production.

§ 05

Accessibility

How this website is built to be used by everyone.

Documented against WCAG 2.2 AA. Each implementation is paired with the next improvement we intend to ship.

01

Keyboard Navigation

Current implementation

All interactive elements reachable via tab order. Skip-to-content link on every route.

Future improvement

Add roving tab index to complex composite widgets.

02

Focus States

Current implementation

Visible focus ring on every focusable element, meeting 3:1 contrast against adjacent colours.

Future improvement

Refine focus offset for dense card layouts.

03

Semantic HTML

Current implementation

Landmarks, headings and lists used correctly. One <main> per route.

Future improvement

Continued audit of nested article regions.

04

Screen Reader Compatibility

Current implementation

Tested against VoiceOver and NVDA. Names, roles and states exposed.

Future improvement

Extend testing to TalkBack on Android.

05

Reduced Motion

Current implementation

prefers-reduced-motion honoured across all Framer Motion animations.

Future improvement

Static fallback illustrations for animated diagrams.

06

Colour Contrast

Current implementation

Body text meets 7:1. Interactive text meets 4.5:1 minimum.

Future improvement

Contrast audit for tertiary UI states.

07

Accessible Forms

Current implementation

Labels, descriptions and error messages programmatically associated.

Future improvement

Inline validation with polite live regions.

08

ARIA Landmarks

Current implementation

banner, navigation, main, contentinfo present on every page.

Future improvement

Named regions for repeated editorial modules.

09

Readable Typography

Current implementation

Base body 16px, line-height 1.6, max measure ≈ 68ch.

Future improvement

User-controlled type-size preference.

10

Language Attributes

Current implementation

Root <html lang> updates per language toggle (EN / PT / ES).

Future improvement

Per-quote lang attributes in mixed-language content.

§ 06

Digital Sustainability

Every kilobyte is a decision.

Each optimisation is documented against three questions: why it matters, what it saves, and what the visitor gains.

AVIF images

AVIF compresses 40–60% smaller than JPEG at equivalent quality.

Environmental
Less data transferred.
Performance
Faster LCP.
User
Sharper images on capable devices.

Responsive images

Serve the right size to the right screen — nothing more.

Environmental
Avoids wasted bytes on small screens.
Performance
Lower CPU decoding cost.
User
Faster loads on cellular.

Variable fonts

One font file expresses many weights and widths.

Environmental
Fewer requests, smaller total payload.
Performance
Reduced FOUT.
User
Consistent typography across breakpoints.

Critical CSS

Above-the-fold styles inlined; the rest deferred.

Environmental
Smaller render-blocking payload.
Performance
Faster first paint.
User
Instant visual response.

Minimal JavaScript

The site is content-first; interactivity is added deliberately.

Environmental
Less CPU, less battery.
Performance
Lower Total Blocking Time.
User
Smoother scroll and input.

Lazy loading

Off-screen media loads only when needed.

Environmental
Bandwidth spent only on what is seen.
Performance
Better bandwidth allocation.
User
Faster time-to-interactive.

No autoplay video

Video is opt-in, never ambient.

Environmental
Prevents multi-megabyte auto-downloads.
Performance
Preserves main thread.
User
No unexpected motion or sound.

Reduced tracking

No third-party analytics or ad networks.

Environmental
Removes an entire class of third-party requests.
Performance
Fewer blocking scripts.
User
Meaningful privacy by default.

Privacy-first analytics

Aggregate, cookieless measurement only.

Environmental
Small payload, no persistent identifiers.
Performance
Negligible runtime cost.
User
No consent friction.

Green hosting

Served from data centres powered by renewable energy.

Environmental
Lower operational carbon intensity.
Performance
Global edge delivery.
User
Lower latency worldwide.

Reduced animation

Motion used only when it clarifies meaning.

Environmental
Less GPU work per session.
Performance
Better battery life.
User
Calmer, more legible interface.

§ 07

Design decisions

Editorial notes on intentional design.

Not every choice is visible. These are the ones we want to make legible.

Note 01

Why the homepage video was removed

A looping brand film added roughly 8 MB per visit and offered little narrative return. We replaced it with a typographic manifesto that communicates the same idea at a fraction of the weight.

Note 02

Why typography became the primary design element

Type carries meaning without loading imagery. It scales, translates and remains legible on any device — the most sustainable design material available.

Note 03

Why images were reduced

Every image is a request, a decode and a repaint. We keep photography where it earns its place: portraits, work, and moments of human texture.

Note 04

Why subtle motion was chosen

Motion earns attention; it should not demand it. Small fades and slow transitions signal state without hijacking focus.

Note 05

Why pages prioritise readability

Line length, leading and contrast are treated as accessibility features first and aesthetic ones second.

Note 06

Why white space matters

Negative space is not empty — it is the interface's way of saying nothing is more important than what you are reading right now.

§ 08

Transparency

What we're still improving.

Publishing this list is not an admission — it is the report.

  1. 01

    Accessibility testing across a wider range of assistive technologies.

    In progress · Q3 2026
  2. 02

    Performance optimisation on low-end devices and 3G connections.

    In progress · Q3 2026
  3. 03

    Content refinement — clearer, shorter, more evidence-based.

    In progress · Q3 2026
  4. 04

    Image optimisation for the long-tail of editorial pages.

    In progress · Q3 2026
  5. 05

    Continuous auditing with automated Lighthouse runs per deploy.

    In progress · Q3 2026

§ 09

Methodology

How this website was built.

A linear diagram of a non-linear process. Each step feeds the next; the last feeds the first.

  1. Step 01

    Research

    Completed
  2. Step 02

    UX

    Completed
  3. Step 03

    UI

    Completed
  4. Step 04

    Accessibility

    Completed
  5. Step 05

    Performance

    Completed
  6. Step 06

    Testing

    Completed
  7. Step 07

    Launch

    Completed
  8. Step 08

    Continuous Improvement

    Ongoing

§ 10

Digital Experience Methodology

Built under the Venga methodology.

A philosophy of building for the web, not a service page. Seven disciplines, applied together, from the first sketch onwards.

01

Accessibility

Designed to WCAG 2.2 AA from the first wireframe, not retrofitted.

02

Performance

Budgets defined per route and enforced in CI.

03

Digital Sustainability

Every asset justifies its weight.

04

SEO

Semantic structure and per-route metadata as a design constraint.

05

Maintainability

Editorial systems editors can operate without engineering.

06

Editorial Design

Typography and rhythm treated as first-class citizens.

07

Privacy

Minimum viable data collection, always.

§ 11

Download

Digital Responsibility Report.

Signed, versioned, checksum-verified. Distributed as a static document, hosted alongside this page.

Document

Digital Responsibility Report · v1.0

A portable, printable edition of this page for archival and procurement reviews.

Available upon publication of v1.0

Format
PDF / A-2
Version
1.0
Publication date
July 2026
Report size
≈ 1.4 MB
SHA-256
e3b0c442 98fc1c14 9afbf4c8 996fb924
Last updated
July 2026

§ 12 · Closing statement

Responsible digital experiences are never finished.

Every update to this website is measured against accessibility, performance, sustainability and long-term maintainability.

Explore our methodology
Version 1.0Last audited July 2026Published from LisbonWCAG 2.2 AACore Web VitalsTransparency Log