Add enterprise dashboard accessibility guard#411
Open
KoiosSG wants to merge 2 commits into
Open
Conversation
Author
|
Hardening update pushed in 5047577: noncritical low-contrast dashboard content now produces a warning, keeps scheduled exports blocked, and marks WCAG perceivable readiness false instead of releasing as clean. I added a regression that failed before the fix with release_with_accessibility_monitoring == remediate_before_public_release and now passes. Validation refreshed locally: npm run check, npm test (4 tests), npm run demo, npm run demo:video, ffprobe on demo.mp4, git diff --check, and credential-like sensitive-term scan returned no matches. |
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.
/claim #19
Summary
enterprise-dashboard-accessibility-guard/slice for Enterprise Tooling issue Enterprise Tooling #19.Hardening Update
Scope
This focuses specifically on accessibility readiness for institutional admin dashboards and their downstream export/webhook release lanes.
It is distinct from the existing dashboard/export/webhook replay/compliance/identity/retention/data-residency/SLA/secret-rotation/quota/API-change/connector-certification/incident/funder/AI-model/dashboard-attribution/initiative-tag/policy-exception/IRB/data-export/SCIM/deposit-reconciliation/admin-notification/cost-allocation/LMS/payload-redaction/vendor-DPA/cohort-privacy/API-rate-limit slices.
Validation
npm testfailed withrelease_with_accessibility_monitoring == remediate_before_public_releasebefore warning on noncritical low contrastcd enterprise-dashboard-accessibility-guard && npm run check-> passedcd enterprise-dashboard-accessibility-guard && npm test-> enterprise-dashboard-accessibility-guard tests passed (4)cd enterprise-dashboard-accessibility-guard && npm run demo-> generated JSON/Markdown/SVG artifactscd enterprise-dashboard-accessibility-guard && npm run demo:video-> generatedreports/demo.mp4ffprobeconfirmedreports/demo.mp4is H.264, 1280x720, 7.5s, 24fps, 104,275 bytesgit diff --check-> passedgit diff --cached --check-> passedrg -n "(password|wallet|paypal|bank|passport|private key|api key)" enterprise-dashboard-accessibility-guard-> no matchesSafety
Synthetic data only. No credentials, private dashboard records, SSO calls, webhook calls, export delivery, payment processor calls, or private institutional systems are used.
AI-assisted with OpenAI Codex; I reviewed and locally verified the diff before submitting.