Skip to content

rlaope/oh-my-hermes / .claude/agent-skills/omh-apple-design

omh-apple-design

Verified

[omh] Designing or reviewing an iOS, macOS or Apple UI.

references/materials-and-accessibility.md

View on GitHub
# Materials and Accessibility

## Source record

- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/materials
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/tutorials/data/design/human-interface-guidelines/materials.json
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/documentation/technologyoverviews/adopting-liquid-glass.md
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/accessibility
- Web standard, accessed 2026-09-05: https://www.w3.org/WAI/standards-guidelines/wcag/

## Materials

Liquid Glass belongs to the controls and navigation layer; standard materials
belong behind content. Use custom glass sparingly. Prefer regular material when
text legibility matters, and clear material only over rich-media backgrounds.
The explicit exception is transient interactive content controls, where the
current Apple guidance may justify the control-layer treatment. Native Liquid
Glass is not a CSS `backdrop-filter` recipe.

Apple's materials guidance includes a bright-content example that considers 35%
dark dimming. Carry that as conditional source-applicable guidance, never as a
universal CSS token or a fixed opacity recipe. Respect current API and version
availability, different appearances, Reduce Transparency, and Increase
Contrast. For web approximations, offer an opaque fallback rather than claiming
native material behavior.

## Access and input

For native work, identify system control semantics, VoiceOver labels, Full
Keyboard Access and keyboard paths, gesture alternatives, Reduce Motion, and
appearance/contrast behavior. Dynamic Type applies to iOS and iPadOS, while
macOS uses system styles, app text scaling, and adaptive layout. Verify with the
current platform APIs and the actual target state.

For Apple-inspired web, require semantic HTML, keyboard and focus behavior,
reflow/zoom, contrast, pointer targets, motion reduction, and WCAG
applicability. An accessibility plan is not WCAG PASS: hand observed proof to
`omh-accessibility-audit`; hand rendered state and motion evidence to `omh-visual-qa`.

## Boundary

Use the Apple records for Apple-platform applicability and the W3C record for
web-standard applicability. Neither source grants certification; unobserved
screens, assistive-tech behavior, and rendered states remain not_observed.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall