Skip to content

fix(web): fix Send recipient field accessibility semantics - #8074

Open
ninglinLiu wants to merge 1 commit into
Uniswap:mainfrom
ninglinLiu:fix/send-recipient-a11y-8063
Open

ninglinLiu wants to merge 1 commit into
Uniswap:mainfrom
ninglinLiu:fix/send-recipient-a11y-8063

Conversation

@ninglinLiu

Copy link
Copy Markdown

Summary

  • Replace the Send recipient TouchableArea wrapper with Flex so the editable input is not nested inside a web role="button" control
  • Give the recipient input an accessible name matching the visible "To" label
  • Name the clear-recipient control (aria-label / accessibilityLabel: Clear recipient)

Fixes #8063

Test plan

  • Open Send flow, tab to recipient field — input should not be inside a button
  • Screen reader announces a name for the recipient field and the clear control
  • Existing SendRecipientForm unit/snapshot tests

This PR was prepared with AI assistance and reviewed/tested by the author.

Avoid nesting the editable recipient input inside a TouchableArea
role=button wrapper, name the input with the visible To label, and give
the clear control an accessible name.

Fixes Uniswap#8063

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Send recipient field has nested button semantics and unnamed controls

1 participant