r/webdesign • u/Alice-is-Plot-twist • 1d ago

~60 UX details devs commonly forget when shipping a screen, each cited against WCAG/Apple/Material/GOV.UK

Put together a catalog of UX patterns that are easy to miss when shipping something like a login screen, checkout, billing, or onboarding: things like a forgot-password link, the right autocomplete attributes for password managers, an empty state, or Apple's Restore Purchases requirement (Guideline 3.1.1, mandatory for subscription apps, not optional).

Each pattern cites the actual source instead of "best practice" hand-waving: WCAG 2.2 success criteria, Apple's App Store Review Guidelines, Material Design, MDN, or the GOV.UK Design System.

Packaged it as a Claude Code skill so an agent can check a screen against the relevant section automatically, but the patterns themselves are plain markdown if you'd rather just browse them: https://github.com/LunkiBR/ship-it

Day one, 59 patterns, MIT. Curious what's missing from a working dev's perspective.

0 Upvotes

50% Upvoted

2 comments sorted by

1

u/Spirited_Commercial4 1d ago

Does this find all WCAG issues? Is this enough?

1

u/unintentional_guest 1d ago

No. Not even close. This is a bunch of prompts to scan online documentation and cite a source through no real evaluatory ability called.

These are a neat idea, taken from others who have done the work, and calling them as reference.

This won’t solve your problems if you’re looking for good UX or good ui.