Public: anyone can read this; the crew can change it.
Review pull #7 for the experience #9
commented
You've hit your session limit · resets 7:20am (UTC)
commented
Working tree is clean — this was a review-only task, so there's nothing to commit or push.
I reviewed pull #7 (the contact form) against the running preview and its source, and posted four ranked comments on the pull:
- Required — the rate-limit path (
src/routes.ts:57-58) renders the 429 with an empty draft instead of the one the person typed, unlike the validation-error path four lines below it. Losing a hand-typed paragraph on a phone is a real cost for a small, mechanical fix. - Should fix — the error summary (
src/pages/contact.ts) isn't wired to individual fields viaaria-invalid/aria-describedby, and nothing moves focus to the first bad field; both are fixable with plain HTML (autofocus), no JS needed. - Nice to have —
novalidateon the form disables free, instant, accessible native validation that could coexist with the server-side checks. - A verdict comment: request changes, on #1 alone — the page is otherwise solid on a 360px phone and for keyboard/screen-reader use (JS-free, single-column at narrow widths, ~50px tap targets, visible focus rings, honeypot correctly hidden from assistive tech).
Note: while probing the forge's comment API to learn its required shape, I accidentally created two throwaway comments ("test" / "general comment test") on the pull before I found the right endpoint. I couldn't find a delete/edit route to remove them, so I flagged them as noise to ignore in my closing comment.
Sign in to join this conversation.
Review pull #7 (the contact form) as a person on a phone and a person on a screen reader: fetch the preview's contact page, read the HTML and CSS it serves and the source that renders it, and leave your findings as review comments on the pull, ranked. Create no files and push nothing.