You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1️⃣ No Feedback When Selecting a Non-Installed Wallet
If a user selects a wallet that is not installed as a Chrome extension, nothing happens.
Expected Behavior: Display an error message, warning, or redirect to install the specific wallet.
2️⃣ The frontend currently appears to work only with the Fuel blockchain.
Ethereum Wallets: MetaMask is not detected.
Solana Wallets: Backpack is not detected.
3️⃣ Accessibility & Semantic Issues in Wallet Selection
The wallet selection element is not implemented using the button tag, which is less semantically correct.
As a result, keyboard navigation is not possible.
Additional Issues:
The dialog close button and the "Create one" link are also not implemented using button and a tags, making keyboard navigation inaccessible.
Expected Behavior:
Use for selection elements.
Or the necessary attributes for accessibility.
Ensure proper keyboard navigation support.
4️⃣ Alt text is not used for icons and images, which reduces accessibility. For example, the close button (❌) could have aria-label="Close" and an alternative text inside the svg.
The text was updated successfully, but these errors were encountered:
annavilnid
changed the title
UX Improvement: Improve Wallet Selection in Dialog CONNECT WALLET
UX Improvement: Improve Wallet Selection in Dialog Connect Wallet
Mar 20, 2025
1️⃣ No Feedback When Selecting a Non-Installed Wallet
If a user selects a wallet that is not installed as a Chrome extension, nothing happens.
Expected Behavior: Display an error message, warning, or redirect to install the specific wallet.
2️⃣ The frontend currently appears to work only with the Fuel blockchain.
Ethereum Wallets: MetaMask is not detected.
Solana Wallets: Backpack is not detected.
3️⃣ Accessibility & Semantic Issues in Wallet Selection
The wallet selection element is not implemented using the button tag, which is less semantically correct.
As a result, keyboard navigation is not possible.
Additional Issues:
The dialog close button and the "Create one" link are also not implemented using button and a tags, making keyboard navigation inaccessible.
Expected Behavior:
Use for selection elements.
Or the necessary attributes for accessibility.
Ensure proper keyboard navigation support.
4️⃣ Alt text is not used for icons and images, which reduces accessibility. For example, the close button (❌) could have aria-label="Close" and an alternative text inside the svg.
The text was updated successfully, but these errors were encountered: