preference-audit
Audit an existing interface for respect of user preferences including motion, contrast, colour scheme, and text scaling. Chains: user-preference-respect, responsive-accessibility, colour-independence. Use when reviewing an existing product for adaptive behaviour.
- Installs
- 72
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill preference-audit- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads preference-audit automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
User Preference Audit
Test whether an existing interface correctly detects and responds to user preferences — the accessibility settings people have deliberately chosen.
Process
Step 1: Test Motion Preferences
Using user-preference-respect, enable prefers-reduced-motion and navigate the entire interface. Document:
- Animations that continue playing
- Transitions that still slide or fade
- Parallax effects that remain active
- Autoplay video or carousels that don't stop
- Any motion that serves no functional purpose
Step 2: Test Contrast and Colour Preferences
Enable prefers-contrast (more) and forced-colors mode. Using user-preference-respect and colour-independence, document:
- Elements that become invisible or indistinguishable
- Focus indicators that disappear
- Interactive elements that lose their borders
- Colour-only status indicators that become meaningless
- Charts or visualisations that become unreadable
Step 3: Test Colour Scheme
Switch between light and dark modes. Document:
- Content that becomes illegible in one mode
- Images or icons that don't adapt
- Hardcoded colours that clash with the theme
- Contrast failures specific to one mode
Step 4: Test Text Scaling and Zoom
Using responsive-accessibility, test at 200% browser zoom and with system font size at maximum. Document:
- Text that overflows or gets clipped
- Layouts that break or overlap
- Horizontal scrolling that appears
- Fixed-height containers that truncate content
- Interactive elements that become unreachable
Step 5: Test Combinations
Test realistic combinations:
- Dark mode + high contrast + reduced motion
- 200% zoom + large system font
- Forced colours + reduced motion
Document any failures that only appear in combination.
Output
Deliver an audit report:
- Summary — which preferences are respected, which are ignored
- Preference-by-preference findings — specific failures for each
- Combination failures — issues that appear only when multiple preferences are active
- Fix list — prioritised by severity and number of users affected
Severity definitions:
- Critical — preference is completely ignored, causing harm or blocking access
- Major — preference is partially respected, significant gaps remain
- Minor — preference is mostly respected, edge cases need fixing
FAQ
What does the preference-audit skill do?
Audit an existing interface for respect of user preferences including motion, contrast, colour scheme, and text scaling. Chains: user-preference-respect, responsive-accessibility, colour-independence. Use when reviewing an existing product for adaptive behaviour.
How do I install preference-audit?
Run npx skills add https://github.com/owl-listener/inclusive-design-skills --skill preference-audit in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/preference-audit/ (personal) or .claude/skills/preference-audit/ (project).
Which AI agents can use preference-audit?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is preference-audit safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains preference-audit?
It is published by owl-listener in owl-listener/inclusive-design-skills. It has 72 recorded installs.
More from owl-listener/inclusive-design-skills
plain-language-design
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
keyboard-navigation
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
cognitive-load-assessment
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
responsive-review
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
user-preference-respect
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
error-prevention-recovery
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.