Accessibility by design
Designing digital experiences that are usable, understandable, and accessible to as many people as possible.
Keyboard navigation
Accessible interfaces should not require a mouse or touchscreen. Every interactive element should have a logical keyboard order, a visible focus state, and an interaction that can be completed without a pointer.
Use Tab to move between controls.
What I consider
- Logical tab order
- Visible keyboard focus
- Keyboard-operable controls
- No keyboard traps
- Skip navigation where appropriate
Color & contrast
Color should support an interface, not be the only way information is communicated. I consider contrast, hierarchy, states, and non-color indicators when designing accessible interfaces.
Dark blue provides strong contrast for headings, navigation, and primary interface elements.
Light blue is used primarily as an accent for borders, highlights, decorative elements, and supporting UI.
Semantic HTML
Good accessibility starts with good structure. Semantic HTML provides meaningful information about the purpose and hierarchy of content to browsers, assistive technologies, search engines, and developers.
<header>
<nav>
...
</nav>
</header>
<main>
<section>
<h1>Page heading</h1>
...
</section>
<section>
<h2>Section heading</h2>
...
</section>
</main>
<footer>
...
</footer>
Why it matters
- Creates meaningful document structure
- Improves screen reader navigation
- Provides predictable heading hierarchy
- Reduces unnecessary ARIA usage
- Makes interfaces easier to maintain
Forms & error handling
Forms should clearly communicate what information is required, how to complete each field, and what went wrong when validation fails.
!Please enter a valid email address.
Accessible form patterns
- Visible labels for every input
- Programmatically associated instructions
- Clear validation messages
- Error states that don't rely on color alone
- Logical focus management
Accessible components
Accessibility should be built into components rather than treated as an afterthought. Buttons, cards, navigation, controls, and interactive states should all behave consistently.
Clear labels, sufficient contrast, and visible focus states.
The entire card can be interactive while maintaining a clear keyboard focus state.
Current-page state and focus should be visually distinguishable.
Controls should have accessible names and keyboard-visible focus states.
Motion & interaction
Motion can provide useful feedback, but it should never be required to understand or operate an interface. Animations should respect user preferences for reduced motion.
Subtle movement can communicate interaction and reinforce an element's clickability.
Users who prefer reduced motion should receive the same information without unnecessary animation.
@media (prefers-reduced-motion: reduce) {
*,
*::before,
*::after {
animation-duration: 0.01ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.01ms !important;
scroll-behavior: auto !important;
}
}
Accessibility isn't a checklist
Accessibility is most effective when it is considered throughout the design and development process rather than added after the interface is complete.
Design experiences that work for everyone.
Accessibility is part of how I approach UX, UI, and front-end development from the beginning.