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
While working on the project, I noticed some accessibility issues in the components features.tsx and section1.tsx during a Lighthouse audit: 1. Missing labels for form elements and 2. list structure that items are not contained within
or elements.
Although no formal issue had been previously assigned, I took a proactive approach to identify and test solutions to these accessibility concerns. My intention was to confirm that these changes would indeed improve accessibility before formally proposing them. After implementing the changes, the Lighthouse accessibility score improved from 88 to 96 (used chrome devTools)
I have applied aria-label to the JsonInput component in section1.tsx to ensure that form controls are announced properly and wrapped feature items in
and
elements.
Before:
After:
Since I haven't contributed frequently, I apologize if my approach to creating and testing this solution is not fully aligned with the expected process. My intention was to ensure the changes would be beneficial before formally proposing them through a pull request. I wanted to raise this issue to share the potential improvement and gather feedback from the team before formally creating a PR.
Alternative solutions or implementations
No response
Other context
No response
The text was updated successfully, but these errors were encountered:
@tkim602 — Note that your <html> elements are invisible, because they're not code fenced. Single backticks, like `<html>`, are good for inline things. Entire lines or paragraphs can be preceded and followed by lines of just 3 backticks, like
Feature
While working on the project, I noticed some accessibility issues in the components features.tsx and section1.tsx during a Lighthouse audit: 1. Missing labels for form elements and 2. list structure that items are not contained within
or
elements.
Although no formal issue had been previously assigned, I took a proactive approach to identify and test solutions to these accessibility concerns. My intention was to confirm that these changes would indeed improve accessibility before formally proposing them. After implementing the changes, the Lighthouse accessibility score improved from 88 to 96 (used chrome devTools)
I have applied aria-label to the JsonInput component in section1.tsx to ensure that form controls are announced properly and wrapped feature items in
and- elements.
Before:
After:
Since I haven't contributed frequently, I apologize if my approach to creating and testing this solution is not fully aligned with the expected process. My intention was to ensure the changes would be beneficial before formally proposing them through a pull request. I wanted to raise this issue to share the potential improvement and gather feedback from the team before formally creating a PR.
Alternative solutions or implementations
No response
Other context
No response
The text was updated successfully, but these errors were encountered: