Accessibility
Sitka is built with accessibility at its core. We adhere to WCAG 2.1 Level AA standards to ensure that our products are usable by everyone, regardless of ability.
Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
Contrast Ratio
Every text and interactive element in Sitka is designed to meet WCAG 2.1 AA as a minimum. Primary reading text targets AAA (7:1) where possible.
Learn more →Non-Text Content
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
Visual Hierarchy
Use layout, typography, and color to create a clear visual hierarchy that guides the user through the interface.
Operable
User interface components and navigation must be operable.
Keyboard Accessibility
All functionality must be available from a keyboard. Sitka components use standard focus indicators and logical tab orders.
Learn more →Focus States
Interactive elements must have a visible focus state. Sitka uses a high-contrast accent ring for all focused elements.
Navigable
Provide ways to help users navigate, find content, and determine where they are. This includes breadcrumbs, clear headings, and skip links.
Understandable
Information and the operation of the user interface must be understandable.
Predictable
Make Web pages appear and operate in predictable ways. Navigation should be consistent across the system.
Input Assistance
Help users avoid and correct mistakes. Use clear error messages and inline validation.
Learn more →Readability
Ensure text is readable and understandable. Use clear typography and avoid overly complex language.
Learn more →Robust
Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.
Semantic HTML
Use semantic HTML elements (like <nav>, <main>, <article>, <button>) to provide meaning to assistive technologies.
ARIA Roles & Attributes
Use ARIA (Accessible Rich Internet Applications) attributes where semantic HTML is not sufficient to describe complex components.
Our Commitment
Accessibility is not a checklist, but a continuous process. We regularly audit our components and patterns to ensure they meet the highest standards of inclusivity. If you encounter any accessibility issues, please report them through our feedback channels.