views

Generate accessible Rails views with WCAG 2.1 AA compliant partials, helpers, and forms.

Updated Dec 13, 2024

Search Tags:#accessibility #tailwind #erb #rails #stimulus #wcag-2.1 #nested-forms

Ready to run

npx skills add https://github.com/apdarr/lace --skill views-apdarr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: views
Source: https://github.com/apdarr/lace/tree/main/.github/skills/views
Command: npx skills add https://github.com/apdarr/lace --skill views-apdarr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers create accessible, maintainable Rails views by providing standardized patterns, guidance, and examples that align with WCAG 2.1 AA.

Core Features & Use Cases

Guided structure for Rails views using partials, helpers, and forms
Accessible patterns including semantic HTML, ARIA usage, and keyboard navigation
Real-world examples demonstrating nested forms, layouts, and Hotwire/Stimulus integration

Quick Start

Use this skill to inspect an existing Rails app and apply WCAG 2.1 AA compliant view patterns across partials, helpers, and forms.

Frequently Asked Questions about views

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I build accessible Rails views that meet WCAG 2.1 AA standards?▼

To build accessible Rails views meeting WCAG 2.1 AA standards, apply standardized patterns for partials, helpers, and forms that ensure semantic HTML, keyboard navigation, and proper ARIA usage across your project.

What is the best way to structure nested forms in Rails using Stimulus and Hotwire?▼

The best way to structure nested forms in Rails with Stimulus is by using standardized view patterns that integrate Hotwire and ensure accessible, maintainable code with proper semantic HTML and ARIA attributes.

How do I add ARIA attributes and keyboard navigation to Rails view partials?▼

You add ARIA attributes and keyboard navigation to Rails view partials by applying standardized accessibility patterns that align with WCAG 2.1 AA, ensuring proper semantics and interactive control across your application.

Can I use Tailwind CSS with Rails ERB templates while maintaining accessibility?▼

Yes, you can use Tailwind CSS with Rails ERB templates while maintaining accessibility by following standardized view patterns that enforce WCAG 2.1 AA compliant semantics and keyboard navigation.

How do I test Rails views for WCAG 2.1 AA compliance?▼

You test Rails views for WCAG 2.1 AA compliance by applying standardized testing patterns that validate accessible semantics, keyboard navigation, and ARIA usage within your partials, helpers, and forms.

When do I need to use ARIA in Rails forms versus standard HTML elements?▼

You need to use ARIA in Rails forms when standard HTML elements cannot convey the necessary semantics, applying standardized patterns to ensure WCAG 2.1 AA compliance and proper keyboard navigation.