Repository navigation
fix(docs): address automated accessibility findings - #2464
Merged
Merged
Conversation
✅ Deploy Preview for stackoverflow-email ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for stacks ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for stacks-svelte ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
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.
Summary
Fix straightforward accessibility failures in the documentation while preserving intentional “what not to do” examples and existing visuals.
Companion scanner PR: https://github.com/StackEng/Accessibility/pull/578
Changes
Addresses missing-alternative and control-name findings associated with WCAG 1.1.1, 1.3.1, and 4.1.2. No published-package changes or changeset required.
How to test
npm ci, then run:npm run test -w packages/stacks-docsnpm run check -w packages/stacks-docsnpm exec -w packages/stacks-docs -- eslint .Observed: 24 tests pass; no type errors; five warnings in unchanged files; ESLint passes.
npm run dev -w packages/stacks-docs -- --host 127.0.0.1 --port 5174./brand/logo,/brand/color,/brand/typography,/brand/stack-system,/brand/motion,/system/forms/select,/system/components/toggle-switch,/system/accessibility/intro, and/system/components/editor. Check names and form interactions. Keyboard-select whitespace glyphs and confirm their pressed state updates.Preview: https://deploy-preview-2464--stacks.netlify.app — pending automatic Netlify build; not yet available.
A documentation-only merge requires a maintainer to run the “Deploy docs” workflow, or deployment with a later package release, before production audits see these fixes.