Accessibility check skill
Find and fix common barriers on the canvas. Check contrast, heading order, image descriptions, labels, and tap targets, and flag anything beyond the canvas.
# Accessibility Check Audit selected Framer pages or site areas using checks that are supported or inspectable in Framer. ## Instructions - Check heading order, semantic tags, and content structure. - Check image alt text and decorative image treatment. - Check accessible labels for links, buttons, icons, and form fields. - Check form labels, instructions, and visible error states. - Check color contrast and text readability. - Check responsive reflow across relevant breakpoints. - Check motion, autoplay, and reduced-motion settings. - Check whether meaning relies only on color, position, or animation. - Check page language settings where exposed. - Do not change anything unless explicitly requested. ## Report Mark each item as one of the following: - Passed - Issue found - Needs manual testing - Not applicable Never mark an item as passed when it could not be fully tested.
How to apply skills to your project
Keep new pages consistent with your project’s typography, colors, spacing, and components.
Skill copied
# Design system
Use this skill when you add pages or sections to a site that already has a look. You extend the system the team built. You don’t invent a new one.
## Before you start
- Open the home page and two pages close to the new one.1. Copy the skill
Use the Copy button above the skill to copy this skill’s instructions to your clipboard.
/skills
Turn these instructions into
a reusable skill:
GPT 6 Sol
2. Add it in agent chat
Type
/skillsin your agent chat and paste the skill, or add it in Settings / Skills.Use
/design-system
to build a new
Careers page. Include a couple job openings and a form.
GPT 6 Sol
3. Use it in chat
Type the skill’s command, such as
/design-system, in your agent to use it.Title
design-system
Description
Use components, styles, spacing, and layouts to create new
Content
Design system
Use dark color scheme. Reuse existing styles and components; never invent new colors or text styles.
Pages
Apply the Base layout template to every new page.
Set a meta title and meta description on every new page.
Sections fill the screen width (
1fr) and contain an inner wrapper withmaxWidth="1200px"that holds the content.
Colors
Container backgrounds: Color/Black.
Text:
Primary headings: Color/White
Secondary/body text: Color/White 60
Accent: Color/Red is the only accent. Use it very sparingly (one highlight per section at most).
Borders and dividers: Color/Border Solid or Color/Border Transparent.
Typography
Always use these text styles, never inline type styles:
Set Text Balance to Yes for text layers.
Use sentence case; do not use all caps.
Do not use eyebrow text (small text above a heading).
In heroes, use Text/Body L for supporting text.
For every paragraph, adjust its text-box width to produce 50–75 characters per line, targeting 65. Round the width up to the nearest 5 or 10 pixels. If that width is wider than the parent container, set the text box to Fill. Verify at every breakpoint before finishing.
Text/H0: jumbo headings and hero treatments
Text/H1: blog post titles and secondary page titles
Text/H2, Text/H3, Text/H4, Text/H5, Text/H6: all other headings, in hierarchy order
Text/Body L: sub heads
Text/Body: main body text
Text/Body M: small supporting text
Text/Button: button labels only
4. Edit your skill
Open Settings / Skills whenever you want to make changes.
Related skills
Tidy up
Auto-name layers and remove hidden or unused leftovers from selected areas.
CMS check
Review CMS content, references, and detail pages for launch issues.
Form audit
Check your form settings, field labels, and submission destinations before launch.
Launch checklist
Review page readiness and collect the fixes that need attention before publishing.
