Keep vocamac.com headlines sans-serif on Windows Chrome - #228
Merged
Conversation
Windows does not ship Avenir Next or SF Pro Display. Chrome then tried Helvetica Neue italic, missed, and landed on Times New Roman. Headings now use the HQ display stack plus Segoe UI and Arial, and the hero em keeps that stack instead of the user-agent italic face.
github-actions
Bot
added
bug
The heading-stack test bans that face in the built stylesheet. Naming it in a comment made the test fail for the wrong reason.
The feature page used "Settings -> About". Latest html-validate treats the raw ">" as an error, and CI installs that checker with npx.
jatinkrmalik
marked this pull request as ready for review
August 19, 2026 04:56
jatinkrmalik
added a commit
that referenced
this pull request
Aug 19, 2026
#228 kept Windows headlines on a sans stack but left the hero accent in ink and the H1/H2 clamps short of vocahq.com. The hero em is teal again. Heading clamps, weight, and tracking match HQ. Body stays 16px. Display stack is unchanged.
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Windows Chrome was showing the homepage headline in Times New Roman. The display stack named Avenir Next and SF Pro Display, which Windows does not have. Chrome then hit Helvetica Neue italic (often a broken local face) and fell to a serif.
--displaynow matches HQ:Avenir Next,Helvetica Neue,ui-sans-serif,system-ui. Segoe UI and Arial sit on the end so Windows has a real sans. SF Pro Display is gone. Headings and headingemset that stack themselves. The hero line "Your Mac types." no longer uses the user-agent italic face.Display weight is 760, 780 on the hero H1, with tighter tracking and a larger H1. Body is 16px. No
@font-faceand no Google Fonts. Status stays Beta. No version bump. Tone picker is untouched.The GitHub Release Updates page said
Settings -> About. Latest html-validate rejects the raw>. That line is nowSettings / Aboutso the website job can stay green.HQ reference: https://vocahq.com/styles.css?v=4 and the typography tokens in https://github.com/VocaHQ/vocahq/blob/main/web/DESIGN.md.
brand/README.md§8 anddocs/website-design-standard.mdare not on vocahqmain; DESIGN.md is what that repo publishes.Local checks:
cd web && npm run check(10 tests), stylelint, html-validate.This is a new CSS PR, not #227.