Feat(accessibility): add accessibility analysis and WCAG checklist to section workflow #12
Conversation
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
…hecklist generation. Updated documentation to include new command and accessibility section. Introduced AccessibilityCard component for displaying analysis results.
cabana8471-arch
added a commit
to cabana8471-arch/design-os
that referenced
this pull request
Dec 26, 2025
RESPONSIVE DESIGN (buildermethods#12): - AppLayout.tsx: Add responsive padding to main content (px-4 sm:px-6 py-8 sm:py-12) - SectionPage.tsx: Make screenshots grid responsive (grid-cols-1 sm:grid-cols-2) - DesignPage.tsx: Make color/typography grids responsive (grid-cols-1 sm:grid-cols-3) BARREL FILES (buildermethods#13): - Create src/components/index.ts with 32 exports (pages, cards, layout, navigation) - Create src/components/ui/index.ts with 14 exports (all UI primitives) Benefits: - Mobile layouts now adapt properly with stacking grids - Components can be imported from single entry points - Better tree-shaking support for production builds 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
cabana8471-arch
added a commit
to cabana8471-arch/design-os
that referenced
this pull request
Dec 29, 2025
…ons (6 fixes) FIXES: - export-product.md: Added Rule 4 abbreviation note in example prompts - agents.md: Added INCLUDE_SHELL note to Foundation Milestone Definition - agents.md: Added hookify/README.md reference in Full Documentation - agents.md: Documented SKILL.md custom format (non-standard frontmatter) - section/clarifying-questions.md: Renamed to "Section-Specific Backend Logic" - data-model.md: Added cross-reference to agents.md Four Pillars FALSE POSITIVES IDENTIFIED (11): - Issues buildermethods#1, buildermethods#2, buildermethods#4-7, buildermethods#10, buildermethods#12, buildermethods#14, buildermethods#15, #17 already properly implemented MODIFIED FILES: - .claude/commands/design-os/export-product.md - .claude/commands/design-os/data-model.md - .claude/templates/design-os/section/clarifying-questions.md - agents.md - FORK_CHANGELOG.md 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Adds a new optional accessibility analysis step to the section design workflow, positioned after screen designs and before screenshots. This feature enables users to analyse their screen designs for WCAG compliance and generate actionable accessibility reports.
Changes
New Features
/add-accessibility): Analyses screen design components and generates WCAG-based accessibility reportsproduct/sections/[section-id]/accessibility.mdUI Updates
Type System
AccessibilityInfoandAccessibilityChecklistIteminterfacesSectionDatato include accessibility informationDocumentation
accessibility.mdWorkflow Integration
The accessibility step fits into the existing section design workflow:
Technical Details
product/sections/[section-id]/accessibility.mdUsage
Users can run
/add-accessibilityafter creating screen designs to:The accessibility analysis is optional and does not block progression to other steps.