Accessible & Ethical

Historical Context

Accessibility on the web started as a whisper. Section 508 in 1998 forced US federal agencies to make their digital stuff usable by people with disabilities, but the private sector mostly shrugged. Then WCAG 1.0 dropped in 1999 — a noble attempt, honestly kind of unreadable, and largely ignored by anyone shipping product. For years, accessibility lived in a sad little checkbox at the bottom of a QA spreadsheet. Nobody designed for it. They retrofitted for it, badly, at the last minute. Everything changed when the lawsuits started. Domino's Pizza. Beyoncé's website. Target. Suddenly 'we'll fix it later' became 'our legal team says fix it now.' The ADA, written decades before the web existed, got interpreted to cover digital experiences. Companies started paying six-figure settlements over missing alt text and inaccessible forms. That woke people up fast. Now we're somewhere more interesting. The best teams don't treat accessibility as compliance — they treat it as a design constraint that makes everything better. Like responsive design before it, accessibility is shifting from 'extra work' to 'this is just how we build things.' WCAG 2.2 and the push toward AAA aren't aspirational anymore. They're the baseline smart teams aim for.

When to Use

Here's the honest answer: AA is the legal floor and it's enough for most products. Hit AA, sleep at night. But if you're building for government, healthcare, or education — go AAA. Those users aren't edge cases, they're your primary audience. The cost difference between AA and AAA is real but overstated. Most of it is color contrast and text sizing decisions you should be making anyway. Where it gets expensive is retroactively fixing a codebase that never considered accessibility. Build it in from day one and the marginal cost of AAA over AA is maybe 10-15% more design time. Worth it.

Design Principles

• Focus states are UI, not decoration — Design your focus rings intentionally. A 3px solid outline with 2px offset in your brand color tells keyboard users exactly where they are. If your focus states look like an afterthought, they are.
• Content hierarchy must survive without color — Remove all color from your interface. Can you still understand the hierarchy? If not, you're relying on a channel that 8% of men literally cannot perceive. Use size, weight, spacing, and position first. Color reinforces, it never carries meaning alone.
• Interactive targets need generous geometry — 44×44px minimum touch targets aren't just a mobile concern. People with motor impairments use mice too. Padding is cheap. Frustration is expensive. Make buttons and links physically easy to hit.
• Reading flow must be logical when linearized — Your screen reader users experience your layout as a single stream. If your visual design uses CSS Grid to reorder content, the DOM order still needs to make narrative sense. Design the reading order first, then arrange it visually.
• Provide multiple paths to every action — Some users can't hover. Some can't click precisely. Some can't see your icon-only buttons. Every critical action needs at least two ways in: keyboard shortcut and click, visible label and ARIA label, gesture and button. Redundancy is a feature.

Technical Specs

Related

Minimalismo & Swiss

Minimalism & Swiss Style

Flat & Soft UI

Neumorphism

Flat & Soft UI

Glassmorphism

Brutalismo

Brutalism

Futurista & Tech

3D & Hyperrealism