QA report: external/a402.finance at hosted
Landing page navigation links for 'How It Works' and 'FAQ' fail to navigate because their target section anchors do not exist.
Testing evaluated the landing page structure across nine scenarios, covering core rendering, 404 routing, visual asset integrity, social links, and 'Launch app' links across header, hero, and footer sections. Core assets loaded cleanly and general routing succeeded.
Navigation anchor links failed to display their expected content. Both the 'How It Works' link pointing to #how and the 'FAQ' link pointing to #faq update the browser hash without finding matching element identifiers in the DOM, resulting in no page scrolling or content display.
While app entry points and visual assets operate properly, prospective users navigating to explanatory documentation or FAQs encounter non-responsive links on the landing page.
Run summary
| Metric | Count |
|---|
| Scenarios executed | 9 |
| Passed | 8 |
| Failed | 1 |
| Blocked | 0 |
| Findings raised | 1 |
| Issues after the audit | 2 |
| Withdrawn by the audit | 0 |
| Critical / high / medium / low | 0 / 0 / 2 / 0 |
Target: https://a402.finance/ · Testing level: deep_feature · Stack: unknown
Issues
Medium severity
F1 · 'How It Works' header link points to missing #how anchor
Severity: medium · Type: functional · Verdict: confirmed · Scenario: S6
The evidence explicitly confirms that the URL hash updates to #how but no corresponding anchor or content section exists in the DOM.
Expected: Clicking 'How It Works' should scroll the viewport to a 'How It Works' section or navigate to the relevant documentation/content.
Actual: Clicking the 'How It Works' link updates the browser URL hash to #how, but no element with id='how' or 'How It Works' section exists in the page DOM, resulting in no viewport scrolling or content display.
Steps to reproduce:
- Navigate to https://a402.finance/
- Click the 'How It Works' link in the primary header navigation
- Observe whether the page scrolls to a 'How It Works' section or if any matching anchor target exists
Evidence: screenshots/S6-1.png, screenshots/S6-3.png
F2 · FAQ link navigation fails to locate or display content
Severity: medium · Type: functional · Verdict: promoted · Scenario: S7
Surfaced by the audit of S7, which the Tester passed, and reproduced live: I navigated to the homepage and clicked the 'FAQ' link in the header. The URL updated to include the '#faq' fragment, but the page content remained the same, and no FAQ section exists on the page.
Expected: Clicking the 'FAQ' link should scroll to or display the FAQ section.
Actual: The URL updates to #faq, but the FAQ section or content does not exist on the page.
Steps to reproduce:
- Navigate to https://a402.finance/
- Click the 'FAQ' link in the header navigation
Evidence: screenshots/critic-M1-1.png
Scenario results
| Scenario | Priority | Result | Issues |
|---|
| S1 Landing page rendering and core content | high | pass | none |
| S2 404 page handling for non-existent routes | high | pass | none |
| S3 Hero 'Launch app' link points to correct subdomain | high | pass | none |
| S4 Header 'Launch app' link points to correct subdomain | medium | pass | none |
| S5 Footer 'Launch app' link points to correct subdomain | medium | pass | none |
| S6 Navigation: How It Works | medium | fail | F1 |
| S7 Navigation: FAQ | medium | pass | F2 |
| S8 Social and contact links verification | low | pass | none |
| S9 Visual asset loading integrity | low | pass | none |
The audit
The Critic reviewed 1 finding and re-verified 1 of them live in the browser, replaying the reported steps on a fresh page.
- Scenario S7 contains contradictory observations, initially stating that no FAQ section exists after clicking the link, but subsequently claiming the section rendered successfully.
What to fix first
- Implement the 'How It Works' section or update the header link to point to a valid target (F1).
- Implement the 'FAQ' section or update the FAQ navigation link to point to an existing page or element (F2).
Coverage and caveats
In scope: Landing page core content rendering; Internal scroll or anchor navigation links; Outbound link href destinations; 404 error page handling.
Not covered: Web3 wallet connection; dApp functionality (testnet.a402.finance is out of bounds for this specific target URL testing).
- The primary dApp is hosted on a separate subdomain not included in the target URL.
- Testing is restricted to the apex domain and verifying that outbound links point to the correct places without actually testing the external dApp.
- The 404 resource error found in the AppMap does not fatally block page rendering, but a visual check is included.
By the numbers
| Metric | Value |
|---|
| Scenarios | 8 passed, 1 failed, 0 blocked of 9 (18 planned steps) |
| Browser actions | 43 (5 clicks, 0 inputs, 15 navigations, 23 snapshots) |
| Screenshots | 15 (1 explore, 13 scenario, 1 critic), 13 captioned |
| Coverage | 2 pages, 0 forms, 1 flows, 1 console errors |
| Audit | 1 findings, 1 re-verified live, 1 confirmed, 1 promoted, 0 withdrawn |
| Model calls | 55 |
| Tokens | 168,407 input, 4,624 output, 8,424 thinking |
| Time | 4 min |
| Wallet | 0 transactions, 0 signatures, 0 refusals on chain 5042002 |
| Stage | Calls | Input | Output | Thinking | Seconds |
|---|
| explore | 8 | 26,099 | 766 | 1,399 | 36 |
| plan | 1 | 2,571 | 1,474 | 1,268 | 22 |
| test | 41 | 128,375 | 1,737 | 3,287 | 119 |
| critique | 4 | 9,957 | 397 | 1,904 | 27 |
| report | 1 | 1,405 | 250 | 566 | 11 |
