mcpField
P
preference-audit

preference-audit

github.com/owl-listenerTesting & quality10872 installsUpdated 20w ago
Repository

About preference-audit

A skill for testing whether an interface respects users' chosen accessibility preferences. It checks reduced motion, contrast and forced colors, color schemes, zoom, and system text size, then reports combined-setting failures and prioritized fixes.

Key features

  1. 01Test reduced-motion preferences
  2. 02Check high contrast and forced colors
  3. 03Verify light and dark color schemes
  4. 04Test 200% zoom and large text
  5. 05Find failures across preference combinations
  6. 06Prioritize fixes by severity

Use cases

  1. 01Audit response to system motion settings
  2. 02Check control visibility in high-contrast modes
  3. 03Verify readability in light and dark themes
  4. 04Test layout overflow at larger zoom and text sizes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/inclusive-design-skills --skill preference-audit

After installing, type/preference-auditin Claude Code to confirm it loaded.

Details

From the project README

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:

  1. Summary — which preferences are respected, which are ignored
  2. Preference-by-preference findings — specific failures for each
  3. Combination failures — issues that appear only when multiple preferences are active
  4. 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

Comments

Markdown supported