← ClaudeAtlas

user-personalizationlisted

Load this skill whenever the project has personalization features, user preference controls, theme selectors, font size adjusters, motion toggles, contrast settings, or any user-configurable accessibility accommodations. Under no circumstances override or ignore user OS-level accessibility preferences without explicit user consent. Absolutely always persist user preferences, apply them immediately, and respect prefers-reduced-motion, prefers-contrast, and similar media queries.
mgifford/accessibility-skills · ★ 15 · AI & Automation · score 77
Install: claude install-skill mgifford/accessibility-skills
# User Personalization Accessibility Skill > **Canonical source**: `examples/USER_PERSONALIZATION_ACCESSIBILITY_BEST_PRACTICES.md` in `mgifford/ACCESSIBILITY.md` > This skill is derived from that file. When in doubt, the example is authoritative. Apply these rules when implementing user preference controls or reviewing existing personalization features. **Only load this skill if the project has personalization features.** --- ## Core Mandate Users should be able to customize content presentation to meet their individual needs without compromising information, functionality, or accessibility. Personalization must complement — never replace — proper accessible design. Note: `1.4.12 Text Spacing` (AA) is the primary WCAG criterion that personalization controls address. This skill is the correct home for that criterion. --- ## Severity Scale (this skill) | Level | Meaning | |---|---| | **Critical** | Overlay used as compliance substitute; interferes with user's AT | | **Serious** | OS-level preferences (reduced-motion, colour scheme) not respected | | **Moderate** | Personalization widget not keyboard accessible; state not announced | | **Minor** | Preferences not persisted; `prefers-reduced-data` not considered | --- ## Critical: Never Use Accessibility Overlays as a Compliance Substitute Third-party "accessibility overlay" widgets that claim to auto-fix accessibility issues **must not** be used as a substitute for proper accessible design. **Using an overlay as a co