OmniHub

A critical crash on the bridge feature and widespread keyboard accessibility barriers in the wallet connection modal impede navigation and core flows.

Testing focused on discovering and interacting with OmniHub features on the Arc testnet, including wallet connection dialogs, collection creation, faucet claims, navigation switches, and UI controls across 12 scenarios. Out of these, 4 passed, 3 failed, and 5 were blocked. One finding concerning dark mode toggle responsiveness was withdrawn during audit after verification showed a test harness actionability issue rather than an application defect.

The primary functional failure is a high-severity crash where clicking the sidebar 'Bridge & swap' button unmounts the entire application interface, rendering a blank page. In addition, the 'Connect to OmniHub' modal contains recurring accessibility flaws: wallet provider choices are rendered as non-interactive generic div elements without button semantics or keyboard focusability, and the modal dialog is missing a required accessible title.

Primary creation, minting, network rejection, and faucet verification flows were blocked because the wallet could never be chosen: the options in the connect dialog are plain div elements, so the test driver, like keyboard and assistive-technology users, could not activate them (see F1). A test wallet was injected in the browser throughout. For release readiness, resolving the bridge crash and standardizing modal accessibility semantics should be addressed prior to full on-chain deployment validation.

Target: https://omnihub.xyz/discover/arc-testnet · Testing level: deep_feature · Stack: unknown

Severity: high · Type: accessibility · Verdict: confirmed · Scenario: S1

Clicking 'Connect Wallet' opens a modal titled 'Connect to OmniHub'. The wallet options (MetaMask, Rabby Wallet, Coinbase Wallet, OKX Wallet, Zerion) are exposed in the accessibility tree as 'generic' elements rather than buttons or links, confirming the reported lack of interactive semantics. The page reported 2 console errors during the scenario.

Expected: Wallet selection options should be rendered as interactive button elements (or have role="button" and tabindex="0") so users can select and activate wallet connection.

Actual: Wallet selection options (MetaMask, Coinbase Wallet, Rabby Wallet, OKX Wallet, Zerion) inside the 'Connect to OmniHub' dialog are rendered as generic elements without button roles or tabindex, making them inaccessible to keyboard navigation and accessibility tools.

Steps to reproduce:

1. Navigate to https://omnihub.xyz/discover/arc-testnet
2. Click the 'Connect Wallet' button in the top banner
3. Observe that wallet options in the 'Connect to OmniHub' modal cannot be focused or triggered via keyboard or standard accessibility actions

Evidence: screenshots/S1-3.png, screenshots/S1-7.png

Severity: high · Type: functional · Verdict: confirmed · Scenario: S11

I navigated to the Arc Testnet discover page and clicked the 'Bridge & swap' button in the left sidebar. The UI completely unmounted, resulting in a blank page with zero elements rendered, verifying the reported crash. The page reported 1 console error during the scenario.

Expected: Clicking 'Bridge & swap' should open a bridge interface/modal within the app or navigate to a valid bridging page.

Actual: Clicking the 'Bridge & swap' button in the sidebar crashes/unmounts the application UI, leaving a completely blank page with 0 elements rendered.

Steps to reproduce:

1. Navigate to https://omnihub.xyz/discover/arc-testnet
2. Click the 'Bridge & swap' button in the left sidebar under the Tools section

Evidence: screenshots/S11-5.png, screenshots/S11-8.png

Review note (2026-09-16): Withdrawn in human review on 2026-09-16 as a duplicate of F1: the same wallet options in the same Connect to OmniHub dialog, reported again from another scenario.

Severity: medium · Type: accessibility · Verdict: withdrawn · Scenario: S3

The evidence supports the claim that the wallet selection options lack necessary attributes (role="button" and tabIndex) for keyboard navigation. The page reported 2 console errors during the scenario.

Expected: Each wallet provider option should be an interactive button (or have role="button" and tabIndex={0}) that can be navigated to via Tab and activated with Enter or Space.

Actual: Wallet options in the Connect to OmniHub modal are rendered as non-interactive generic elements without role="button" or tabIndex, preventing keyboard navigation and assistive technology users from focusing or selecting a wallet.

Steps to reproduce:

1. Navigate to https://omnihub.xyz/collection/arc-testnet/arc-omnihub
2. Click the 'Connect Wallet' button in the navigation header
3. Press the Tab key to navigate through the modal options

Evidence: screenshots/S3-5.png

Review note (2026-09-16): Withdrawn in human review on 2026-09-16 as a duplicate of F1: the same wallet options in the same Connect to OmniHub dialog, reported again from another scenario.

Severity: medium · Type: accessibility · Verdict: withdrawn · Scenario: S7

The tester verified the wallet provider options are plain div elements without roles or tabindexes, making them inaccessible to keyboard users. The page reported 2 console errors during the scenario.

Expected: Wallet provider selection items should be interactive buttons or have role="button" and tabindex="0" so keyboard users and assistive tools can focus and select them.

Actual: Wallet provider options in the Connect Wallet modal (MetaMask, Rabby Wallet, Coinbase Wallet, OKX Wallet, Zerion) are plain div elements without role="button" or tabindex="0", rendering them completely inaccessible to keyboard navigation and assistive technologies.

Steps to reproduce:

1. Navigate to https://omnihub.xyz/discover/arc-testnet
2. Click the 'Connect Wallet' button in the top navigation bar
3. Attempt to navigate to or activate MetaMask or other wallet options using keyboard (Tab / Enter)

Evidence: screenshots/S7-4.png

Severity: medium · Type: accessibility · Verdict: promoted · Scenario: S8

Surfaced by the audit of S8, which the Tester passed, and reproduced live: Clicked "Connect Wallet" to open the modal. Examined the accessibility tree and observed that the resulting dialog element does not have an accessible name associated with it (it appears as just dialog without a title), confirming the DialogTitle or visually hidden equivalent is missing. The page reported 2 console errors during the scenario.

Expected: The dialog should include a DialogTitle or visually hidden equivalent to ensure accessibility for screen reader users.

Actual: A console error indicates that DialogContent is missing the required DialogTitle component.

Steps to reproduce:

1. Navigate to the application.
2. Trigger an action that opens a dialog, such as the Connect Wallet modal.
3. Check the console and accessibility tree for the dialog implementation.

Evidence: screenshots/critic-M1-1.png

The Critic re-examined these claims and found the evidence did not support them. They are kept here rather than deleted.

• Dark mode toggle switch in sidebar cannot be clicked or activated (S10, medium): The evidence explicitly notes the failure was due to layout interception and an actionability check timeout, which is a test driver limitation rather than a defect in the application. The page reported 1 console error during the scenario.

The Critic reviewed 5 findings and re-verified 4 of them live in the browser, replaying the reported steps on a fresh page.

• Findings F1, F2, and F3 report the exact same accessibility defect regarding the Connect Wallet dialog across different scenarios.
• Multiple scenarios (S2, S3, S4, S6, S7) were blocked because the wallet options in the connect dialog are not semantic controls (F1), so no wallet could be chosen. Review note (2026-09-16): Human review on 2026-09-16: the injected test wallet was present in the browser for the whole run, so the blocked scenarios (S2, S3, S4, S6, S7) were not caused by a missing wallet extension. They trace back to F1: the wallet options are plain div elements without button semantics, so the test driver, which activates only semantic controls exactly as keyboard and assistive-technology users do, could not choose a wallet and no connection happened. F2 and F3 were withdrawn as duplicates of F1.
• The tester explicitly ran a scenario to verify React hydration (S12) but subsequently ignored the React #418 hydration mismatch error present in the console logs of that very scenario.
• The tester incorrectly classified a Playwright actionability timeout (due to element positioning/interception) as a functional application defect in F4.
• A possible defect in S12 ("React hydration mismatch error on initial page load") was not promoted: the live replay came back not-reproduced.

1. Fix the unhandled exception on the 'Bridge & swap' navigation action that unmounts the interface and leaves a blank screen (F5).
2. Convert wallet provider selection elements in the Connect to OmniHub modal to interactive button elements with proper keyboard focus and accessibility roles (F1, F2, F3).
3. Add the missing DialogTitle component to the wallet modal's DialogContent to satisfy screen reader accessibility requirements (F6).

In scope: Wallet connection and network management on Arc Testnet; Creating NFT collections via the studio form; Minting NFTs from existing Arc Testnet collections; Requesting tokens from the dedicated Arc Testnet Faucet; Form validation for required and constrained fields; Auxiliary interactive elements like Dark mode, Ask AI, and Bridge access.

Not covered: Quests feature (noted as 'Soon' and disabled in the AppMap); Non-Arc testnets (the injected test wallet explicitly refuses other chains); Mainnet deployments (out of scope for a testnet-focused environment).

• The test wallet is pre-configured to connect seamlessly and holds sufficient test USDC for gas.
• The wallet's strict rejection of non-Arc chains will be surfaced to the UI, allowing verification of the application's error handling.
• AI image generation relies on a third-party or internal API that is available in the test environment.
• S2 could not be executed: Execution could not complete the deployment step because no Web3 wallet provider is connected or available to sign the deployment transaction in the headless test environment..
• S3 could not be executed: Wallet connection and on-chain mint execution cannot be completed in this headless environment because an interactive Web3 wallet extension is not available to sign/authorize connections and transactions..
• S4 could not be executed: The network mode switch redirected back to the home page, and the tool-call budget was exhausted before completing the network selection and deploy validation step..
• S6 could not be executed: The faucet does not provide a plain text input for wallet addresses and instead requires connecting an external Web3 wallet extension and completing prerequisite verification tasks..
• S7 could not be executed: Cannot authorize wallet connection because wallet provider options in the Connect Wallet modal are non-interactive divs lacking keyboard focus and interactive accessibility roles..