Web Accessibility Standards

Every person deserves equal access to web content, regardless of ability. We build WCAG 2.2 Level AA compliant websites using semantic HTML5, proper ARIA implementation, keyboard navigation, and comprehensive screen reader support. Accessibility isn't an add-on—it's foundational to everything we create.

Our Commitment

Accessibility drives better design for everyone

WCAG 2.2 Level AA

We meet or exceed Web Content Accessibility Guidelines 2.2 at Level AA, the internationally recognized standard for accessible web content. This addresses ADA Title III requirements for commercial websites.

🎯

Semantic Structure

Proper HTML5 semantic elements, logical heading hierarchies, and ARIA landmarks create clear page structure. Screen readers, search engines, and AI systems all benefit from this clarity.

⌨️

Keyboard Navigation

Every interactive element works without a mouse. Tab order follows visual layout, focus indicators are clear, and skip links let users jump to main content immediately.

👁️

Visual Clarity

4.5:1 minimum contrast ratios, text resizable to 200%, no information conveyed by color alone, and support for high contrast and dark mode preferences ensure readability for all.

🔊

Screen Reader Support

Descriptive alt text, proper ARIA labels, clear form instructions, and meaningful link text create excellent experiences with NVDA, JAWS, and VoiceOver.

🧠

Cognitive Accessibility

Clear language, consistent navigation, sufficient reading time, error prevention, and logical content flow support users with cognitive differences and learning disabilities.

How We Implement

Technical excellence meets inclusive design

Semantic HTML Foundation

We use HTML elements for their intended purpose: <nav> for navigation, <main> for primary content, <article> for self-contained content, and <aside> for complementary information. This creates clear document structure that assistive technologies can parse and present effectively.

ARIA Implementation

ARIA (Accessible Rich Internet Applications) attributes enhance native HTML semantics where necessary. We use aria-label for icons without text, aria-describedby for form field help text, aria-expanded for collapsible sections, and aria-live for dynamic content updates.

Keyboard Interaction Patterns

All interactive elements receive keyboard focus in logical order. Custom components follow established patterns: Tab to navigate, Enter/Space to activate, Escape to close modals, and Arrow keys for menus. Skip links appear on focus to bypass repetitive navigation.

Color & Contrast

Our ocean-inspired palette achieves WCAG AA contrast ratios throughout. Body text uses 7:1 contrast ratio (exceeding the 4.5:1 requirement), interactive elements maintain 3:1 against backgrounds, and we never rely solely on color to convey information or state.

Responsive & Flexible

Layouts remain functional at 320px viewport width and maintain readability when text is zoomed to 200%. Content reflows without horizontal scrolling, touch targets meet 44×44px minimum, and spacing scales proportionally using our 8px base unit system.

Forms & Error Handling

Every form field has a visible label (no placeholder-only patterns), required fields are clearly marked with both visual and semantic indicators, error messages appear adjacent to the relevant field, and success states are announced to screen readers.

Testing & Validation

Continuous verification, not one-time compliance

Automated Testing

  • axe DevTools for WCAG validation
  • WAVE browser extension for visual feedback
  • Lighthouse accessibility audits
  • Pa11y CI for continuous integration

Manual Testing

  • Keyboard-only navigation verification
  • Screen reader testing (NVDA, JAWS, VoiceOver)
  • Color contrast validation tools
  • Browser zoom and reflow testing

User Preferences

  • prefers-reduced-motion support
  • prefers-color-scheme (dark mode)
  • prefers-contrast (high contrast)
  • Browser default font size respect

Real Users

  • Feedback channels for accessibility barriers
  • User testing with assistive technology users
  • Quarterly accessibility reviews
  • Continuous improvement process

Why This Matters

1.3B

people worldwide experience significant disability (WHO, 2023)

26%

of US adults live with some type of disability (CDC, 2023)

100%

of users benefit from clear structure and intuitive navigation

Universal Benefits

Accessibility improvements help everyone. Captions assist users in loud environments or watching without sound. Clear navigation helps users in a hurry. Semantic structure improves SEO and AI discoverability. Keyboard shortcuts increase power user efficiency. Good contrast helps users on bright sunny days.

When you design for disability, you design for humanity in all its diversity. Accessibility isn't a separate requirement—it's foundational to excellent design.

Frequently Asked Questions

What accessibility standards does Saltwind Media follow?

We follow WCAG 2.2 Level AA standards as our baseline, implementing semantic HTML5, ARIA landmarks, keyboard navigation, proper color contrast ratios, and screen reader compatibility across all projects. This exceeds ADA Title III requirements for commercial websites.

How do you ensure websites work with assistive technologies?

We test with NVDA, JAWS, and VoiceOver screen readers during development, verify keyboard-only navigation patterns, implement proper ARIA labels and landmarks, and use automated tools like axe DevTools and WAVE for continuous validation throughout the build process.

Are your websites compliant with ADA requirements?

Yes. WCAG 2.2 Level AA compliance addresses ADA Title III requirements for commercial websites. We provide documentation demonstrating compliance efforts and maintain accessibility as an ongoing commitment, not a one-time checklist. For businesses in regulated industries, we can target WCAG 2.2 Level AAA where required.

Can users customize how they view your websites?

Absolutely. Our sites respect user preferences including prefers-reduced-motion for animations, prefers-color-scheme for dark mode, prefers-contrast for high contrast, and browser zoom up to 200% without breaking layouts. We build flexibility in from the foundation.

How do you handle color contrast for users with visual impairments?

All text meets WCAG 4.5:1 contrast ratio for normal text and 3:1 for large text (we typically exceed these minimums). We never rely solely on color to convey information, using patterns, labels, and icons alongside color coding. Interactive elements maintain 3:1 contrast against their backgrounds.

Are your contact forms accessible to everyone?

Yes. All forms include visible labels (never placeholder-only), clear error messages with specific guidance, keyboard accessibility, proper focus indicators, and descriptive instructions. Required fields are clearly marked and announced to screen readers using both visual and semantic indicators.

What about users who can't use a mouse?

Every interactive element is fully keyboard accessible. Users can navigate with Tab, activate with Enter or Space, and skip to main content using skip links. Focus indicators clearly show the current position with high contrast outlines, and logical tab order follows visual layout consistently.

How do you make images accessible?

All meaningful images include descriptive alt text that conveys the image's purpose and content. Decorative images use empty alt attributes (alt="") to prevent screen reader clutter. Complex diagrams include extended descriptions using aria-describedby or adjacent text when necessary.

Do you support users who need more time to read content?

Yes. We avoid auto-playing content, provide pause controls for animations (respecting prefers-reduced-motion), ensure sufficient time for form completion with no arbitrary timeouts, and design content with clear hierarchies that make scanning and comprehension easier for all cognitive abilities.

How can I report an accessibility barrier on your website?

Contact us at [email protected] with details about the barrier you encountered, including your operating system, browser, assistive technology (if applicable), and description of the issue. We respond within 2 business days and commit to resolving reported issues within 10 business days.

Does accessibility slow down website performance?

No. Proper accessibility actually improves performance. Semantic HTML, clear structure, and minimal JavaScript—the foundations of accessibility—are the same principles that create fast-loading websites. Our sites achieve both sub-1.5 second load times and WCAG compliance because these goals align perfectly.

Do you provide accessibility documentation for client websites?

Yes. Every project includes an accessibility compliance report documenting implemented features, testing results, WCAG conformance level, and ongoing maintenance recommendations. We also provide training for content editors on maintaining accessibility standards when adding new content.

Build Websites That Welcome Everyone

Accessibility isn't a feature—it's a fundamental aspect of excellent web design. Let's create digital experiences that work beautifully for all users, regardless of ability.

Standards & Resources

WCAG 2.2

Web Content Accessibility Guidelines

View Guidelines →

Section 508

US Federal Accessibility Standards

Learn More →

ADA Title III

Americans with Disabilities Act

Read Requirements →

ARIA Authoring

Best Practices for ARIA Implementation

View Patterns →