Repository navigation
Feat/storybook - #7
Merged
Merged
Conversation
…ification Adds a single monorepo Storybook instance (npm run storybook / build-storybook) documenting every component in @ca-webstack/ng-components and @ca-webstack/ng-components-extra, compiled from source and hosted from a new root angular.json application project. Every component gets co-located stories covering its main use cases, controls, and autodocs. The same stories back an automated accessibility test suite that runs in CI on every change: - Structural checks via axe-core at WCAG 2.2 AA across every story (npm run test:a11y). - Keyboard-interaction checks driving real key events (Tab, Enter, Space, Escape, Arrow keys) through representative interactive widgets and asserting the resulting accessible state (npm run test:keyboard). - An automated colour-contrast audit across every rendered foreground/background combination. - Static accessibility lint (@angular-eslint) enforced as a build error in both packages. Both new gates use a standalone Playwright-based script rather than @storybook/test-runner, avoiding a dependency conflict with the monorepo's existing jest-based unit tests. Publishes ACCESSIBILITY.md, a conformance statement against WCAG 2.2 AA / EN 301 549 covering both packages: target and regulatory context, a Definition of Done for interactive components, the verification methods and tooling above, a per-component conformance record, and known limitations. Also includes a number of accessibility refinements found and fixed while building out the automated coverage: colour-contrast adjustments to several default design tokens, accessible-name wiring for a few composed/dynamic controls, keyboard target-size and scrollable-region adjustments, and related component-level fixes across both packages.
… document known limitations
lgalluzzi2823
self-requested a review
July 16, 2026 16:30
lgalluzzi2823
approved these changes
Jul 16, 2026
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
2 participants
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.
Description
Related issue
Type of change
Affected package(s)
How has this been tested?
npm run buildnpm run lintnpm run testChecklist
dist/,.turbo/,.angular/, etc.).