Repository navigation
Conversation
…related-issues-1505-1510-1550-1551
boluxx123
force-pushed
the
fix/issue-632-frontend-dashboard-settings-tab-form-bare
branch
from
October 1, 2026 11:43
6c4b696 to
f4a8698
Compare
boluxx123
force-pushed
the
fix/issue-632-frontend-dashboard-settings-tab-form-bare
branch
from
October 21, 2026 21:00
f4a8698 to
1539caa
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR fixes an accessibility issue in the dashboard settings tab stream-creation form, where inputs were wrapped in
<label>tags withoutid/htmlForassociations. Every control now has a stableid, and labels are consistently associated so assistive tech can reliably connect them. No visual changes.Related Issue
Changes
♿ Form Label Association
frontend/src/components/dashboard/dashboard-view.tsxidattributes to every input/textarea/select in the stream-creation form (Template name, Recipient Address, Token, Total Amount, Starts At, Ends At, Cadence (seconds), and Note).<label>pattern already used in the form, so each label is programmatically tied to its control viahtmlFor+ matchingid.aria-label="Template name"input with a properly associated visible label, keeping the same markup structure and styling.Verification Results
id<label>pattern applied uniformly withhtmlFormatching each control idCloses #632