accessible-form-controls-error-validation
/accessible-form-controls-error-validation
Use this skill when authoring accessible form inputs with explicit labels, helper descriptions, and live assertive error announcements.
- Author
- nextboxis ↗
- Repository
- library-skill-agents ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use this skill when authoring accessible form inputs with explicit labels, helper descriptions, and live assertive error announcements.
Original author description
Use this skill when authoring accessible form inputs with explicit labels, helper descriptions, and live assertive error announcements.
How it works
- When to use
- Prerequisites
- Step-by-step workflow
- Commands / code examples
- Common mistakes & pitfalls
- Verification checklist
- Related skills
SKILL.md preview
--- name: accessible-form-controls-error-validation description: Use this skill when authoring accessible form inputs with explicit labels, helper descriptions, and live assertive error announcements. --- # Accessible Form Controls & Error Validation ## When to use Use this skill when you need to authoring accessible form inputs with explicit labels, helper descriptions, and live assertive error announcements. ## Prerequisites - Working knowledge of systems administration, site reliability engineering, or accessibility standards. - Appropriate administrative tooling, terminal shell, or screen reader testing environment. ## Step-by-step workflow 1. **Analyze operational context**: Inspect host system telemetry, access controls, or UI accessibility trees. 2. **Formulate implementation plan**: Draft declarative configurations, automation scripts, or remediation markup. 3. **Apply changes**: Execute modifications following standard operating procedures and least-privilege principles. 4. **Audit and verify outcomes**: Run diagnostics, automated audits (axe, Lighthouse, sar), or command assertions. 5. **Establish ongoing telemetry**: Configure monitoring rules, periodic health checks, or CI regression gates. ## Commands / code examples ```bash # Operational command and verification workflow for accessible-form-controls-error-validation echo "Executing verification check for accessible-form-controls-error-validation" ``` ## Common mistakes & pitfalls - Disabling security controls or bypassing accessibility standards to achieve rapid fixes. - Modifying production systems without automated verification checks or rollback scripts. - Relying on manual testing instead of embedding automated assertions into CI/CD pipelines. ## Verification checklist - [ ] Implementations satisfy security, accessibility, or observability standards. - [ ] Automated checks pass with zero high-severity warnings or failures. - [ ] Diagnostic logs and telemetry confirm expected operational state. - [ ] Operational runbooks and documentation are updated. ## Related skills - wcag-22-guidelines-conformance-levels - linux-permissions-chmod-chown-acls - distributed-tracing-opentelemetry-sdk - site-reliability-engineering-slo-sla-error-budgets
Versions
The database has no other skills named accessible-form-controls-error-validation.
Database snapshot: 13.11.2026 · package version 7355cf22b42f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90accessible-forms
Reviews and repairs accessible form labeling, instructions, autocomplete, grouping, validation, error summaries, announcements, redundant entry, and authentication. Use for form, field, label, validation, error-message, autocomplete, or login accessibility work. - 95forms
Load this skill whenever the project contains forms, inputs, selects, checkboxes, radio buttons, text areas, or any validation flow. Under no circumstances create a form without visible labels, error identification, and keyboard accessibility. Absolutely always associate every… - 100fe-a11y-forms
Builds and reviews accessible forms in any stack (HTML, React, Vue, Svelte, Angular, Astro) to WCAG 2.2 AA as a target - labels, autocomplete, required fields, grouping, error messages, focus after submit, sign-in without memory tests. Use when writing or changing a form, an… - 90form-ux-architecture
Use when designing or auditing form structure and validation UX: field grouping, required vs optional inputs, validation timing, client/server validation split, submission lifecycle, recovery, multi-step forms, and high-risk data entry. Do NOT use for labels and announcements… - 100form-labels
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Associate labels with form controls. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant. - 100building-accessible-interfaces
Use when building or auditing any web UI for accessibility — keyboard navigation, screen readers, focus management, ARIA, color contrast, form labels and error announcements, reduced motion, or touch target size. Triggers include "is this accessible", "WCAG", "a11y", "screen…