Skip to content

1.0.1 changes - #1

Merged
waysnx-tech merged 3 commits into
mainfrom
1.0.1
Sep 22, 2026
Merged

waysnx-tech merged 3 commits into
mainfrom
1.0.1

Conversation

@krantighatpande

Copy link
Copy Markdown
Collaborator

Summary

Type

  • Bug fix
  • Accessibility
  • Security
  • Documentation
  • Performance
  • API change
  • Feature

Validation

  • Unit tests
  • Storybook
  • Playwright
  • Accessibility
  • Package/build

Documentation

  • README updated if needed
  • WDG metadata regenerated if needed

@krantighatpande
krantighatpande requested a review from a team as a code owner September 22, 2026 06:52

@waysnx-tech waysnx-tech left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed for 1.0.1 release. CI checks and release configuration verified.

@waysnx-tech
waysnx-tech merged commit 6809c78 into main Sep 22, 2026
7 checks passed
krantighatpande added a commit that referenced this pull request Oct 30, 2026
…losure button only

- Remove redundant navigation landmarks in Sidebar and Navbar wrappers
- Sidebar: Changed outer nav wrapper to div, pass ariaLabel to Menu
- Navbar: Removed role='navigation' from mobile menu wrapper, pass ariaLabel to Menu
- MenuItem: Remove aria-expanded from anchor tag (items with href+children)
- aria-expanded now only on disclosure/chevron button as required
- Add regression tests for navigation landmarks and aria-expanded placement
- Update existing tests to check chevron button instead of anchor
- All 89 tests passing, TypeScript clean, build successful

Addresses final review feedback for Phase 3 P0 #1 Keyboard Accessibility
krantighatpande added a commit that referenced this pull request Oct 30, 2026
…losure button only

Final corrections for Phase 3 P0 #1 review feedback:
- Remove redundant nav landmarks in Sidebar and Navbar
- Keep aria-expanded only on disclosure button, not anchor
- Add regression tests for both corrections
- All 89 tests passing
krantighatpande added a commit that referenced this pull request Oct 30, 2026
Final review corrections for Phase 3 P0 #1 Keyboard Accessibility:

- Remove incomplete arrow key handlers (Arrow keys, Home, End) from Menu component
- MenuItem no longer uses focused state for tabIndex, so handlers prevented default without moving focus
- Native Tab/Shift+Tab navigation is sufficient per W3C Disclosure Navigation Pattern
- Add deprecated 'role' prop for backwards API compatibility (Menu always renders as <nav>)
- Add :focus-visible styles for disclosure buttons to ensure visible focus indicators
- Add regression tests for focus indicators on all interactive elements
- Update arrow key tests to reflect handler removal
- All 89 tests passing, TypeScript clean, build successful

Addresses final review feedback items 1, 2, and 3 for PR #10
krantighatpande added a commit that referenced this pull request Oct 30, 2026
Final corrections for Phase 3 P0 #1 Keyboard Accessibility:

- Align Menu forwardRef type with rendered <nav> element (HTMLElement not HTMLDivElement)
- Update menuRef type from HTMLDivElement to HTMLElement
- Remove @ts-expect-error from deprecated role prop test (TypeScript correctly accepts the prop)
- All 89 tests passing, TypeScript clean, build successful

Addresses final review feedback for PR #10
krantighatpande added a commit that referenced this pull request Oct 30, 2026
Consistency fix for Phase 3 P0 #1 Keyboard Accessibility:

- Navbar: Change forwardRef from HTMLDivElement to HTMLElement (renders <nav>)
- Sidebar: Change forwardRef from HTMLDivElement to HTMLElement (renders <aside>)
- Update useRef types to match forwardRef types
- Ensures all components in this PR have correctly aligned ref types
- All 89 tests passing, TypeScript clean, build successful

Maintains consistency with Menu component forwardRef type alignment
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.

2 participants