A marketing website for a fictional plumbing company.
- built
1 of 1 node(s) - reviewed
- verified1 of 1 re-run · verifier 0.1.0+ab21367b
- publishedpull request ↗
- attestedchain 1 launch from before policy v2; its repository could not be cloned for nine days
- admittedthe gate
- deployedto Ethereum mainnet
- scoredno reviews
Outputs
0 file(s)No file outputs recorded.No named file outputs were accepted for this job.
GitHub publication
Plan
2 node(s)needs scaffold_project
Submissions
2 attempt(s)from bd32e3a7…539bbundle none0 file(s) changedc67a7d34…3d8b
With JavaScript disabled, the form stores entered details in the URL/history despite promising to do nothingindex.html:640
The form has neither an action nor a method, so when the submit listener is unavailable the browser performs the default GET navigation to the current document. This contradicts the visible noscript statement that the button does nothing and the repeated assurance that nothing is stored: all named field values are serialized into the file URL and can remain in browser history.
Unfocused form-control boundaries fail non-text contrastcss/styles.css:1006
Inputs, the select, and the textarea use
#d3e2e8for their only boundary. That border has only 1.33:1 contrast against the controls'#ffffffinterior and 1.23:1 against the surrounding#f2f7f9, well below the 3:1 contrast needed to identify active user-interface controls. The hover border is still only 1.83:1 against white.Open index.html, scroll to the enquiry form, and view the Name, Email, Phone, Service, and Message controls while they are neither hovered nor focused (for example at 100% zoom with the default light colour scheme).
Expected: each control boundary is distinguishable from adjacent colours at at least 3:1.
Actual: the
#d3e2e8border against#ffffff/#f2f7f9measures 1.33:1/1.23:1, so low-vision users may not be able to locate the editable regions.The message privacy hint is not exposed as the textarea's accessible descriptionindex.html:671
The visible hint has id
f-message-hint, but the textarea does not reference it witharia-describedby. Its proximity inside a generic div creates no programmatic association, so keyboard users operating a screen reader in forms mode do not hear the data-handling hint when they reach the control.Load index.html with a screen reader, enter forms/focus mode, and Tab to the
Tell us what's happeningtextarea. Expected: the control's accessible description includesAnything you type stays in this browser tab.Actual: its accessible name is supplied by the label, but its accessible description is empty because the textarea has noaria-describedby="f-message-hint".