# tacto Inc. — Style Reference > A quiet typographic directory: warm gray, oversized information, electric-blue links, and generous empty space. **Original URL:** [tacto-inc.com/index.html](https://tacto-inc.com/index.html) **Final URL:** [tacto-inc.com/index.html](https://tacto-inc.com/index.html) — unchanged, HTTP 200 **Theme:** light in the supplied captures; no alternate theme was verified **Inspected:** supplied capture set retrieved October 2, 2026, at 01:24 JST / October 1, 2026, at 16:24 UTC (`2026-10-01T16:24:12.687Z`) **Viewports:** 1440 × 1000 desktop and 390 × 844 mobile, in CSS pixels **Scope:** the current corporate homepage: opening section, section-navigation links, news archive, contact footer, and the menu content present in the rendered DOM. Visual captures cover the desktop opening, a desktop news position, the desktop footer, the mobile opening, and the mobile footer. No open-menu capture or destination-page inspection was supplied. The homepage presents tacto as a design firm through typography and spatial organization. A small wordmark and two utility controls occupy the top edge. Most of the first screen remains empty, while the introductory statement sits near the bottom. Below it, three large section links lead into an unusually substantial news archive. The address, telephone number, social links, and copyright then receive the scale normally reserved for headlines. The composition relies on a consistent warm-gray canvas, nearly black text, and saturated blue links. Desktop information is pushed toward the right: dates and contact labels occupy a narrow intermediate column, while long text begins around one third of the viewport width. Mobile rearranges these relationships instead of merely shrinking the desktop layout. There are no visible rounded cards, filled CTA buttons, shadows, or decorative photography in the supplied current-page captures. ## How to Read This Reference - **Measured** means a value appears in the supplied rendered DOM or computed-style evidence. Values are rounded for readability where appropriate. - **Calculated** means a value is derived from supplied element bounds, such as the gap between two recorded elements. - **Estimated** means a visual approximation from a current-page screenshot. These values are not recovered CSS declarations. - **Recommended** means implementation guidance for a new build. Breakpoints, fallback behavior, accessibility additions, and the Quick Start interpolation are recommendations unless stated otherwise. - All custom-property names in this document are implementation aliases. The supplied custom-property collections were empty; no original token naming system was established. - A computed `font-family` identifies the declared stack. It does not independently prove which font file supplied every rendered glyph. - DOM-present menu content is documented separately from visually verified components. Its presence and bounds do not establish that the menu was open. ## Tokens — Colors ### Default Palette | Name | Value | Suggested token | Evidence and role | | --- | --- | --- | --- | | Warm Gray | `#efeeea` / `rgb(239, 238, 234)` | `--color-page` | Measured on the root, main, and footer; the continuous page canvas | | Soft Black | `#1f1f1d` / `rgb(31, 31, 29)` | `--color-ink` | Measured text color; primary typography and recommended rule color | | Electric Blue | `#0000ff` / `rgb(0, 0, 255)` | `--color-link` | Measured on CONTACT, news resource links, map, and footer social links | | Transparent | `rgba(0, 0, 0, 0)` | No separate surface token needed | Measured on the header and many content wrappers; reveals the underlying canvas | Blue functions as a text-link color rather than a filled-button color. Large footer links give it considerable visual presence without introducing colored panels. The three main section links are dark, so color alone does not identify every navigation target. Thin rules and the logo appear black or nearly black in the captures. Their precise asset or border colors were not supplied. Reusing `--color-ink` for rules is a recommendation, not a separate measured declaration. The empty logo anchor reports a browser-like blue color in computed styles, but the visible wordmark is dark. Do not interpret the anchor's inherited color as evidence of a second visible blue accent. ### Theme Behavior Only the light presentation is evidenced. No theme selector, dark palette, gradient system, or alternate surface treatment was verified. Preserve the relationship between warm gray, dark typography, and blue links when adapting the design. ## Tokens — Typography ### Latin Display and Utility Text **Measured declared family:** `neue-haas-grotesk-display, sans-serif`. This stack is recorded on CONTACT, News, footer address text, footer links, and menu text. Most sampled elements in these roles have computed weight `500`. The resulting typography is direct and compact: large letters remain plain rather than decorative, while utility text uses the same visual vocabulary at a much smaller scale. ### Mixed English and Japanese Text **Measured body stack:** `neue-haas-grotesk-display, 'Gothic Medium BBB', sans-serif`. The body has a computed weight of `300`, a `10px` font size, `15px` line height, and `0.3px` letter spacing. These are inherited defaults, not the visible size of every child. In particular, the large section-link wrappers report the small inherited size; their nested lettering was not separately measured. The supplied page evidence also contains a font-face declaration naming `Gothic Medium BBB`. It does not establish the complete font-file inventory, the availability of every weight, or the exact font used for each Japanese glyph. ### Root Size and Tracking The root font size is measured at `10px` in both viewports. The root's `Times` family is overridden by the body and should not be treated as a visible serif design feature. A `0.3px` letter-spacing value appears across the sampled body, utility, heading, and footer elements. Use this subtle spacing as a starting point; the widely spaced wordmark is a separate brand treatment and should use its approved artwork. ### Measured Type Scale Values below are `font-size / line-height` in CSS pixels. | Role | Desktop, 1440 × 1000 | Mobile, 390 × 844 | Weight | Notes | | --- | --- | --- | --- | --- | | Body inheritance | `10 / 15` | `10 / 15` | `300` | Not a recommended general reading size | | CONTACT | `16.8667 / 19.2912` | `13.52 / 15.6` | `500` | Compact uppercase utility link | | News heading | `54.8167 / 54.8167` | `37.44 / 55.1201` | `500` | Mobile changes both size and leading | | News resource link | `21.0833 / 14.7583` | `16.64 / 23.92` | `500` | Desktop inline-flex line box is unusually tight | | Footer address | `54.8167 / 66.4125` | `24.96 / 37.44` | `500` | Three desktop lines, five mobile lines | | Map and footer social links | `54.8167 / 66.4125` | `24.96 / 37.44` | `500` | Same scale as the address | | Menu title, DOM only | `210.833 / 199.237` | `79.0401 / 70.7201` | `500` | Open state not visually verified | | Menu primary links, DOM only | `54.8167 / 68.5208` | `31.2 / 31.2` | `500` | Different from the homepage section-link wrappers | | Menu social links, DOM only | `37.95 / 27.4083` | `26 / 31.2` | `500` | Recorded line height is not the same as glyph bounds | The desktop news resource line height is smaller than its font size. This is a measured layout detail, not a broadly reusable text rule. For a new implementation, approximately `1.2–1.4` leading is safer unless exact reproduction requires the original inline alignment. ### Screenshot Estimates | Role | Desktop estimate | Mobile estimate | Limitation | | --- | --- | --- | --- | | Main opening word | Not visible | Approximately `100–104px` | Mobile reads “unlock”; desktop word size cannot be established | | Opening subtitle | Approximately `55px` | Approximately `25px` | Text is “the another angle.” | | English introduction | Approximately `20px` | Approximately `16–17px` | Dedicated text node styles were not supplied | | Japanese introduction | Approximately `20px` | Approximately `14–15px` | Two lines in the mobile capture | | News announcement text | Approximately `38px`, with `48px` leading | Not visually verified | Desktop estimate from the news capture | | News date | Approximately `20px` | Not visually verified | Date-specific computed styles were not supplied | | Footer labels and copyright | Approximately `55px` | Approximately `25px` | Visually consistent with measured footer text | Do not substitute a heavy geometric headline font or a bold Japanese face throughout. The design depends on restrained weight, large scale, and precise alignment more than on typographic ornament. ## Tokens — Spacing & Shapes **Density:** sparse at the opening, substantial within long news entries, and oversized but orderly in the footer. **Geometry:** flat surfaces, square boundaries, fine straight rules, and simple directional marks. **Source scaling formula:** not supplied. Two measured viewport endpoints do not prove a particular fluid formula or breakpoint. ### Measured Spacing and Geometry | Use | Desktop | Mobile | Evidence | | --- | --- | --- | --- | | Header top and side inset | `42.1667px` | `20.8px` | Computed padding | | Logo anchor bounds | `79.05 × 14.75px` | `66.55 × 12.47px` | Rendered bounds | | Header total height | `61.45px` | `36.39px` | Rendered bounds; not a separate solid bar | | News heading bottom padding | `73.7916px` | `52.0001px` | Computed padding | | Section-index top clearance | `252.98px` | `156px` | Calculated from section and first-link bounds | | Section-index bottom clearance | `252.98px` | `156px` | Calculated from last-link and section bounds | | Mobile index row/column gap | Not a uniform measured gap | Approximately `46.80px` | Calculated from link bounds | | Footer top padding | `183.425px` | `114.4px` | Computed padding | | Footer right padding | `42.1667px` | `20.8px` | Computed padding | | Footer bottom padding | `137.042px` | `36.4px` | Computed padding | | Footer left padding | `268.812px` | `20.8px` | Computed padding | | Footer label-to-value origin distance | `227.67px` | `90.47px` | Calculated from footer padding and address bounds | | Gap between mobile social links | — | Approximately `6.23px` | Calculated from consecutive link boxes | | Visible rule thickness | Approximately `1px` | Approximately `1px` | Screenshot estimate | ### Alignment Rails The site does not use one universal centered content container. | Rail | Desktop x-coordinate | Mobile x-coordinate | Function | | --- | --- | --- | --- | | Outer inset | `42.16px` | `20.80px` | Logo, opening copy, News heading | | Header CONTACT | `500.03px` | `224.08px` | Close to the desktop copy rail; independently positioned on mobile | | First section-index link | `497.56px` | `72.80px` | Beginning of the navigation group | | News resource links | `497.55px` | `73.83px` | Main news content alignment | | Footer label origin | Approximately `268.81px` | Approximately `20.80px` | A, T, and S column | | Footer value origin | `496.48px` | `111.27px` | Address, telephone, social links, copyright | Desktop news links and footer values nearly align, but differ by about one pixel in the supplied measurements. Treat them as a shared visual rail rather than claiming identical underlying declarations. Mobile deliberately separates the news-content rail from the footer-value rail. ### Border Radius and Elevation Sampled wrappers have `border-radius: 0`. No rounded card treatment or shadow elevation is visible. The curved return arrow is an icon shape, not evidence of rounded component containers. ## Components ### Persistent Header **Role:** identity and two high-priority utilities. The header contains a small `tacto/` wordmark link at the left, a blue CONTACT link, and a dark MENU control at the right. The logo points to the homepage; CONTACT points to `/contact.html`. At desktop width, CONTACT starts at approximately `x=500px`, near the main information rail rather than the center of the screen. At mobile width, it moves to `x=224px`, with MENU remaining near the right inset. The wordmark scales only modestly, from about `79px` to `67px` wide. The controls remain at the top edge across the supplied scrolled captures. This supports persistent-header behavior, although the original `position` declaration was not included. The measured header background is transparent, and the news capture shows header controls sharing space with large article text underneath. For an adaptation, retain the compact, unboxed appearance while providing sufficient hit areas and preventing focused content from being hidden behind the header. Do not add a tall navigation bar that consumes the opening's empty space. ### Full-Height Opening **Role:** establish identity through scale, silence, and a short bilingual statement. The first section measures exactly `1000px` high on desktop and `844px` on mobile: one viewport in both supplied states. Its content sits toward the bottom, beneath a large empty field. The visible anatomy is: 1. A reserved headline region. 2. A fine horizontal rule. 3. The subtitle “the another angle.” 4. An English description of the firm. 5. The corresponding Japanese description. In the mobile capture, “unlock” occupies the headline region in very large dark text. The rule runs approximately from `x=21px` to `x=369px` at `y=646px`. The subtitle follows directly below; the descriptive copy has a larger separating gap. In the desktop capture, the large word is absent. A thin vertical stroke appears approximately at `x=83px`, from `y=601px` to `y=789px`, above a horizontal rule at about `y=800px`. The subtitle and bilingual description remain visible. The evidence does not establish whether this is a motion phase, a responsive difference, or another runtime state. Preserve the observed uncertainty: do not describe a confirmed typing loop, word rotation, reveal sequence, or cursor animation. The vertical stroke resembles a caret, but its behavior is unverified. ### Bilingual Introduction **Role:** explain the firm without competing with the opening word. The English sentence reads “tacto is a design firm that creates experiences with stories.” The Japanese text is “tactoはストーリーのある体験をつくるエクスペリエンスデザインファームです。” Desktop presents each language as one line. Mobile breaks each into two lines, retaining the English block above the Japanese block. Both align with the outer page inset, not the later news or footer content rails. Keep these as real text with separate language blocks. Avoid treating the Japanese line as a tiny caption or hiding it behind a language switch; both are visible together in the current captures. ### Section Index **Role:** direct visitors to the company's identity, services, and work. Three dark text links follow the opening: - Who We Are → `/whoweare.html` - What We Do → `/whatwedo.html` - Our Works, with the observed count `(17)` → `/our_works.html` The words are arranged as short stacked lines. Their wrapper bounds, rather than their child font declarations, are available in the evidence. On desktop, all three links occupy one horizontal band. Their left coordinates are approximately `497.56px`, `806.92px`, and `1144.31px`, with a shared top of `1252.98px`. Each wrapper is about `160.23px` tall. On mobile, Who We Are and What We Do share the first row at document `y=1000px`; Our Works begins a second row at `y=1136.25px`. The first column starts at `x=72.80px`, and the second at `x=219.06px`. Wrappers are about `89.45px` tall. These are typographic navigation blocks with generous surrounding space. No card surface, image thumbnail, border box, or hover transformation was established. The work count is content, not a permanent decorative number. ### News Heading and Archive **Role:** make company activity a substantial part of the homepage. The News heading returns to the outer left inset. Beneath it is a long chronological list rather than a short teaser grid. The supplied text contains eleven dated entries, spanning August 2022 through May 2026, including two entries marked `*new*`. The desktop news section measures approximately `3990.64px` high, compared with `4876.84px` on mobile. Its length is central to the page's character: this is a company homepage with an extensive information archive, not a compact conversion page. Do not assume every entry has the same height. Some contain a brief update and one link; others include multiple award categories, project names, and separated text groups. ### News Entry **Role:** present a date, a substantial announcement, and related links. The desktop screenshot shows a narrow date column around `x=270px` and a much wider text column beginning around `x=497px`. Thin horizontal separators span the viewport, unlike the inset rule in the opening. Announcements use large mixed English/Japanese text, estimated at approximately `38px` with `48px` leading. Dates are much smaller, around `20px`. Resource links use measured `21.0833px` blue text and a small outlined external-link-like marker. The visible 2025 award entry occupies roughly `275px` between separators. Its date and announcement begin near the top of the row, with approximately `40–45px` of top clearance. The following 2024 entry is much taller because it contains additional project and award lines. Treat the date as metadata, the announcement as primary reading content, and the blue links as separate actions. The evidence does not show that an entire news row is clickable. On mobile, resource links begin at `x=73.83px` and use `16.64px / 23.92px` typography. A mobile news screenshot and date-specific bounds were not supplied, so the exact mobile date/body arrangement and announcement type size remain unverified. ### Contact Footer **Role:** turn practical contact information into a major typographic section. The footer continues the same canvas color. It uses single-letter labels A, T, and S for address, telephone, and social information. A definition-list structure is a suitable implementation recommendation. On desktop, labels begin near `x=269px` and values near `x=496px`. On mobile, labels move to the outer inset near `x=21px`, while values begin around `x=111px`. This maintains a clear two-column relationship even at phone width. The measured address text is `54.8167px / 66.4125px` on desktop and `24.96px / 37.44px` on mobile. Desktop address lines are: - 8F Noda-Building 2-12-1 - Kami-Osaki Shinagawa-ku Tokyo - 141-0021 Japan Mobile presents five lines, separating the building, street number, neighborhood, city district, and postal/country line. This is an observed wrapping outcome; the evidence does not establish which breaks are manual. A blue Google map link follows the address. The telephone number is dark. No telephone anchor appears in the supplied link inventory, so click-to-call behavior should not be claimed as an existing feature. ### Footer Social Links **Role:** provide a large, readable directory of external channels. Every visible footer destination is introduced by a blue down-right arrow-like mark. The destinations are X, Instagram, Facebook, note, Podcast 体験採集, and Podcast アメリカのデザイン. Desktop groups X and Instagram on one line, Facebook and note on the next, and each podcast on its own subsequent line. The measured horizontal gap between the paired links is about `65.34px`. Mobile makes the social list a single vertical sequence. Consecutive one-line links have `37.44px` line boxes separated by approximately `6.23px`. Each podcast occupies two lines, with its Japanese name below “Podcast”; the continuation aligns with the link text rather than the arrow. The copyright, “©2026 tacto Inc.”, aligns with the value column. It remains large rather than becoming fine print. ### Return Arrow **Role:** visually indicate a return toward the page top. A thin curved upward arrow appears near the lower-right corner of the desktop news capture and near the upper-right area of the mobile footer capture. The rendered DOM includes an empty-text anchor targeting `/index.html#`. The recorded anchor bounds are approximately `66.39 × 77.98px` on desktop and `44.70 × 51.98px` on mobile. Its precise positioning logic, accessible name, click handler, and scrolling behavior were not supplied. Do not infer smooth scrolling or a particular visibility threshold. The mobile footer capture places this mark close to MENU. A new implementation should preserve the light stroke and compact footprint while ensuring the two controls do not overlap. ### Menu Content — DOM Evidence Only **Role:** provide a broader navigation directory. The DOM contains a Menu heading; links for Top, Who We Are, What We Do, Our Works, News, Contact, and Recruit; and the same six social destinations as the footer. Desktop measurements place the Menu heading near `x=42px`, with primary links beginning near `x=833px`. The title is very large at `210.833px`. Mobile places the title and links at the outer inset near `x=21px`, using a `79.04px` title and `31.2px` primary links. These bounds suggest a spacious two-part desktop layout and a single-column mobile layout. However, no open-menu screenshot or opening interaction was provided. Its visible background, entry animation, closing behavior, scroll locking, and focus handling remain unverified. The Top link uses a JavaScript placeholder URL in the evidence; its handler was not inspected. ## Tokens — Motion & Interaction ### Evidence and Limits | Feature | Available evidence | What remains unverified | | --- | --- | --- | | Opening headline | Mobile shows “unlock”; desktop shows a thin vertical stroke and no large word | Sequence, trigger, timing, easing, repetition, and whether the difference is animated | | Persistent header | Controls appear at the same top-edge positions across supplied scroll captures | Exact positioning declaration and any visibility logic | | Standard navigation | Destination URLs are present for CONTACT and section links | Hover appearance, click transitions, and destination-page behavior | | News resource links | Blue text and destination URLs are supplied | Hover, visited, focus, and new-tab behavior | | Return arrow | Visible curved mark and a homepage hash anchor | Smooth scrolling, animation, threshold, and exact positioning logic | | Menu | Menu text, link URLs, and computed bounds are present | Open/close interaction, overlay appearance, keyboard behavior, and animation | | Sampled CSS animation | Listed elements report `animation: none` | Unsampled descendants, pseudo-elements, and JavaScript-driven effects | | Sampled transition field | Evidence records `transition: all` | Duration and easing; this alone does not establish a visible transition | The capture process waited for load, layout/text stability, finite animations, and image decoding within stated time limits. It temporarily paused perpetual animations during readiness checks and then resumed them. Those checks do not prove that every delayed state or interaction was captured. ### Recommended Motion Direction For a new implementation, begin with stable readable content and ordinary navigation. Any added headline reveal should keep the final message available without motion and should be explicitly treated as a new design choice. Avoid inventing an elaborate animation system from the single vertical stroke. No source duration or easing token can be responsibly recovered from the supplied evidence. ## Surfaces | Layer | Appearance | Structural purpose | | --- | --- | --- | | Page canvas | Solid warm gray `#efeeea` | Unifies opening, navigation, news, and footer | | Header | Transparent, compact text and logo | Persistent utilities without a large enclosing bar | | Opening | Same canvas, large empty field, inset fine rule | Establishes pacing and typographic hierarchy | | Section index | Unboxed dark text links | Navigation through scale and grouping | | News | Same canvas, full-width separators | Organizes variable-length chronological entries | | Footer | Same canvas, oversized label/value typography | Makes contact information a primary visual section | | Menu | DOM text and geometry available | Visible surface treatment not established | There is no evidenced card-elevation system. Separation comes from whitespace, alignment, rules, size changes, and blue text. ## Imagery No photography, project imagery, or illustration is visible in the supplied current-page screenshots. The visible graphic elements are the wordmark, the opening stroke and rule, small news-link markers, directional footer arrows, and the curved return arrow. This absence is important to the observed composition. Do not fill the opening's empty space with a stock image, a device mockup, a decorative 3D object, or a background video. Other pages and any unrecorded assets remain outside the inspected scope. ### Observed Asset References No reliable asset filenames or image-source URLs were supplied. The references below identify visible elements without inventing paths or formats. | Element | Observed use | Asset knowledge | | --- | --- | --- | | `tacto/` wordmark | Small home link in the header | Visible dimensions measured; source file and format unknown | | “unlock” | Large mobile opening word | Present in rendered text; no image asset required for the word itself | | Opening vertical stroke | Desktop headline region | Rendering mechanism unknown | | News link marker | Small blue outlined mark before resource labels | Original icon path and format unknown | | Down-right arrow marks | Map and footer social links | Visible form known; original implementation unknown | | Curved upward arrow | Return control | Anchor dimensions known; original artwork source unknown | Use approved brand artwork when available. A text fallback can support development, but increasing ordinary letter spacing does not reproduce the wordmark exactly. Unicode arrows in the Quick Start are practical approximations, not recovered original assets. ## Layout & Responsive Behavior ### Document Structure | Region | Desktop top / height | Mobile top / height | | --- | --- | --- | | Opening | `0 / 1000px` | `0 / 844px` | | Section index | `1000 / 666.20px` | `844 / 537.70px` | | News | `1666.20 / 3990.64px` | `1381.70 / 4876.84px` | | Footer | `5656.84 / 1147.67px` | `6258.55 / 867.22px` | | Whole document | Approximately `6804.52px` | Approximately `7125.77px` | These are captured content-dependent dimensions, not section heights to hardcode. The news archive grows substantially on mobile because of wrapping, while the footer becomes shorter overall as its typography and padding decrease. ### Desktop Composition The opening spans the viewport and places copy near its bottom edge. Subsequent content uses asymmetry: a substantial empty left area precedes the section index, news text, and footer values. The News heading remains at the outer left edge, giving it a different alignment role from the entries below. The footer label rail and news date rail occupy roughly the first fifth of the viewport. Main information begins around `34.5%` of the viewport width. These are descriptive proportions calculated from this capture, not confirmed source formulas. ### Mobile Composition Mobile uses approximately `20.8px` outer insets, or `5.33%` of the captured width. It retains large typography but changes the layout in several distinct ways: - Header utilities regroup toward the right while the logo stays left. - “unlock” is visible above the opening rule. - English and Japanese introductory text each wrap into two lines. - The section index changes from three links in one row to two links above one. - News resource links begin around `74px` from the left. - Footer values begin around `111px`, retaining room for A, T, and S labels. - Social links become one per line, and podcast names occupy separate continuation lines. Do not reuse the desktop footer's large left offset on a phone. Likewise, do not force mobile news and footer content onto the same rail; the evidence shows different offsets. ### Unverified Ranges No tablet, intermediate desktop, landscape-phone, browser-zoom, or alternate text-size capture was provided. Exact media-query breakpoints and interpolation formulas are unknown. Any breakpoint used below is a practical recommendation rather than a recovered source rule. ## Do’s and Don’ts ### Do - Keep the measured warm-gray, soft-black, and electric-blue palette. - Let empty space carry the opening rather than filling it with decoration. - Preserve the contrast between small header controls and large information text. - Align desktop news text and footer values to nearly the same right-shifted rail. - Retain distinct mobile rails for the section index, news links, and footer values. - Present the news archive as variable-height editorial rows separated by fine rules. - Keep dates smaller than announcements and resource links visibly blue. - Preserve the footer's A/T/S label structure and oversized contact information. - Group desktop social links deliberately, then stack them on mobile. - Use the observed font stacks when licensed and available, with sensible sans-serif fallbacks. - Treat the headline-state difference and menu appearance as unresolved evidence boundaries. ### Don't - Don't turn the homepage into a generic sequence of feature cards and filled conversion buttons. - Don't replace the warm gray with pure white without understanding the tonal change. - Don't introduce shadows, rounded containers, gradients, or decorative color categories. - Don't center every section within one narrow container. - Don't shrink the footer into conventional small-print contact details. - Don't claim a typing animation or rotating headline from the supplied stills. - Don't use the desktop's missing headline as a reason to remove the visible mobile word. - Don't apply the body wrapper's `10px` font size to actual reading content. - Don't assume a menu is visible merely because its text appears in the DOM. - Don't invent icon asset paths, project imagery, production credits, or interaction timings. - Don't hardcode the current work count or copyright year as timeless design tokens. ## Recommended Implementation Additions These are additions for a new implementation, not verified original features: - Give the logo link and return arrow explicit accessible names. Hide purely decorative arrow marks from assistive technology where markup permits. - Implement MENU as a real button with `aria-expanded` and a controlled navigation region. Support Escape, appropriate focus restoration, and a clearly defined closed state. - Expand compact header hit areas without visually enlarging the text. - Provide visible keyboard focus and a non-color-only interaction cue, such as an underline on hover and focus. - Reserve sufficient clearance around the persistent header and return control. The supplied scrolled captures show potential visual crowding. - Keep opening text available if animation fails or reduced motion is requested. A stable headline is a suitable fallback. - Use `