SKILL-001 SaaS UX and layout patterns Locked skill

Accessibility basics for SaaS UI

Reach for a native element first — semantic HTML gives you labels, focus, and keyboard behavior for free, and ARIA can only patch what's missing.

01

What this skill helps you build

Build SaaS interfaces everyone can use: inputs tied to labels, visible focus, full keyboard navigation, readable contrast, and ARIA used only where the platform falls short.

The production takeaway

Reach for a native element first — semantic HTML gives you labels, focus, and keyboard behavior for free, and ARIA can only patch what's missing.

02

Inside this skill

The full skill expands these implementation areas with decisions, edge cases, prompts, tests, and framework-specific code.

SaaS UX and layout patterns
What this helps you build

SaaS screens — forms, settings panels, menus, dialogs — that work for every user and every input device, not just a mouse and a 20/20 screen. Concretely: every field has a label a

🔒
SaaS UX and layout patterns
When to use this

Always — but treat it as non negotiable the moment your SaaS has: Public sign up or a checkout — accessibility is a legal exposure ADA, EU EN 301 549 the instant strangers can reac

🔒
SaaS UX and layout patterns
The core idea

Use the platform; reach for ARIA only when the platform has no answer. A native <button , <a href , <label , <input , or <select ships with a correct role, keyboard behavior, and f

🔒
03

Unlock the full implementation

Paid access includes the complete skill body, implementation prompt, common mistakes, production checklist, and code examples where this skill includes them.