fix(input): expose native editable accessibility - #16
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe EditText touch wrapper is excluded from accessibility traversal. Tests verify direct input access, label preservation, and email keyboard forwarding. A Storybook story documents the accessible email-input configuration. ChangesEditText accessibility
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to EditText now exposes its native input directly to accessibility services while retaining border-tap focus behavior. The targeted regression coverage supports merge readiness with no active current-head risk identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Visit the preview URL for this PR (updated for commit 719ab9d): https://cpk-ui--pr16-bugfix-edit-text-nat-stuwult9.web.app (expires Sat, 12 Sep 2026 18:33:43 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 05244aa8e2a82af676f8a528c78a4bcd59756f99 |
## Summary - Add a public PageIndicator driven directly by continuous UI-thread pager progress, with reversal, bounds, accessible state and reduced-motion support. - Include colocated stories and regressions. This branch includes the existing EditText accessibility fix from #16. - Prepare 0.8.0-beta.3 for the separately approved prerelease; this PR does not itself publish it. ## Verification - Full test:all: 24 suites, 310 tests passed; package build passed. - All seven e2e-smoke checks and static Storybook build passed. - Live browser partial progress and reversal yielded 14px then 7px; reduced motion remained at the settled page. No page errors. - Physical Android consumer captures confirm the pill between dots during both forward and reverse swipes, not only after settling. - Consumer integration regressions cover rapid Next, resize and reduced motion. Physical iOS verification remains pending; no iOS acceptance claim. Publication remains gated on the exact-head checks. No app data, credentials or private consumer sources are included. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added a page indicator with animated progress, theming, customization, accessibility support, and reduced-motion behavior. * Added Storybook examples for continuous page transitions and reduced-motion settings. * **Accessibility** * Improved EditText accessibility by ensuring the editable field is directly discoverable while its touch wrapper remains excluded from accessibility navigation. * Added an accessible email input example with appropriate labeling and keyboard behavior. * **Tests** * Added coverage for page indicator behavior, accessibility, reduced motion, and EditText interactions. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Summary
Keep EditText discoverable as a native input instead of grouping it into the surrounding touch target. Border taps still focus the field. Add a regression test and an accessible email story.
Verification
Summary by CodeRabbit