Tokens & playbooks / Interaction checklist

Rauno Web Interface Guidelines

Inspect the small behaviors that make a page easier to use.

Documentation reviewed

Source review
Oct 18, 2026

Understand the resource

What it is.

Rauno Freiberg’s living guidelines collect details across interaction, typography, motion and layout. The document acknowledges subjective judgments and does not duplicate the WAI-ARIA specification.

When it is useful

The main flow works and you need a targeted craft review.

A proposed application

Put it to work.

This example illustrates a possible use. The proposed workflow and expected result are separate from the bounded checks recorded below.

Try this

Check whether labels focus inputs, controls submit correctly and decorative layers intercept clicks.

Result to aim for

A concrete list of interaction fixes.

Before you start

What you need.

An implemented interface and a way to test its actual states.

The practical boundaries

What to watch for.

Some advice, including broad autocomplete restrictions, needs contextual judgment rather than literal adoption.
Use current accessibility guidance and user needs when a stylistic preference conflicts with familiar browser behavior.

Review record

What we could establish.

Public primary documentation reviewed. See the account-free evaluation for executed checks and remaining workflow limits.

Source coverage and runtime coverage are separate

The source-review notes describe documentation and identity. The account-free evaluation below records exactly which public interaction or local fixture was checked, what happened, and what remains untested.

Check current access, terms, licensing and data handling before using a resource with your own material.

Runtime and security evaluation

What the evaluation covers.

Bounded runtime checkedAccount-free · Oct 19, 2026

The guidelines loaded and the Accessibility section could be brought into view. This confirms that the document is navigable, not that its recommendations certify an implementation.

Methods: Public HTTP response · Public browser sample. A completed check covers the stated sample; it is not a safety certification.

Target: https://interfaces.rauno.me/
Version or capture: Unversioned public page observed on 2026-10-19
Integrity scope: sha256:2ee97ef75073cc321d604f40cd6a47f7a0023a64c167e53363e1f8d0382d1ade — initial HTTP 200 response body only; not whole-application integrity.

Test conditions

Chromium 155.0.8059.82, 1365×900 desktop viewport.
Separate fresh, ephemeral browser contexts for entry and interaction; no owner profile, credentials or stored session.
Only GET/HEAD network requests allowed; forms, downloads, WebSockets and service workers blocked. Some analytics endpoints also blocked.
Short bounded waits; no mobile, assistive-technology, cross-browser or performance certification.

Individual checks and observations

Public HTTP response
pass
Public HTTP response: Anonymous GET with redirects followed, response-body SHA-256 and selected security-header summaries; no cookies retained.
Observed: The standalone client received 200 at https://interfaces.rauno.me/. This establishes response delivery only.
Fresh browser entry
pass
Public browser sample: Open the catalog URL in a new anonymous Chromium context with read-only network guards and no inherited profile.
Observed: The document returned 200 and identified itself as “Web Interface Guidelines”. 0 image elements were present; no account was used.
Observed public sample or navigation
pass
Public browser sample: Bring the “Accessibility” section into view.
Observed: The section was visible after navigation; scroll position was 1998px.

Security findings and boundaries

Passive inspection of the initial public document’s response headers and anonymous browser request hostnames, with read-only guards. No source exploitation, account access, dependency audit or private data.

Observed · info

Public response protections

The initial browser page used HTTPS. Its response included HSTS. No enforcing Content-Security-Policy response header was observed. This records the sampled response only; meta policies, backend authorization and exploit resistance were not assessed.

Observed · info

Observed host boundary

The initial Rauno Web Interface Guidelines browser visit attempted requests only to interfaces.rauno.me. This does not cover later features, server-side processing or a complete session.

Practical advice · caution

Before using this reference

Use the recommendations alongside current platform semantics and accessibility requirements; resolve advice that depends on the component’s context.

Practical caveats

Use the recommendations alongside current platform semantics and accessibility requirements; resolve advice that depends on the component’s context.
Some advice, including broad autocomplete restrictions, needs contextual judgment rather than literal adoption.

What remains untested

No component was built from the guidance and no keyboard, assistive-technology or cross-browser implementation test was performed.
Results describe the observed public pages and a bounded action, not the entire product or the referenced designs.

Security limits

No authentication, authorization, tenant separation, data retention or backend handling was tested.
Header presence or absence is a sampled configuration observation, not a security certification or an exploit finding.
0 blocked-request records were retained across entry and interaction checks. Guards may alter normal page behavior; the logs do not represent unrestricted traffic.

Evaluation sources

Public resource entry

Download this evaluation record (JSON)

Follow the evidence

Sources and further reading.

Keep exploring