WCAG 2.1 AA Helps Guide Our Accessibility Work
We use the Web Content Accessibility Guidelines, version 2.1 Level AA, as a reference when designing, testing, and improving digital experiences. We aim to reduce barriers for people who navigate with keyboards, screen readers, zoom, voice controls, or other assistive technologies.
Accessibility involves judgment, testing, content decisions, third-party tools, and continued maintenance. We do not promise that any website will satisfy every requirement in every situation. Our role is to help clients make informed, good-faith improvements and address as many identified barriers as reasonably possible.
Areas We Work to Support in Our Systems
- Keyboard use for menus, forms, dialogs, and primary actions
- Semantic structure to help clarify headings, landmarks, controls, and content relationships
- Contrast and scalable text reviewed across common devices and zoom levels
- Form guidance including labels, instructions, validation, and useful error feedback
- Responsive reflow intended to reduce unnecessary horizontal scrolling
- Motion and media settings considered alongside user preferences and known accessibility concerns
Accessibility Requires Ongoing Testing
A system can develop new barriers when content changes, integrations are added, or components are updated. We use automated checks and manual review to help identify issues. No testing method can find every possible barrier, and automated tools alone cannot evaluate every aspect of keyboard flow, reading order, labels, or interaction clarity.
Accessibility Audits for Other Businesses
We also review websites and digital systems built by other teams. An audit can help a business understand observed barriers and organize possible improvements without requiring an immediate rebuild.
Depending on the agreed scope, a review may examine representative pages, shared templates, navigation, forms, interactive components, color contrast, text alternatives, focus behavior, reflow, and common assistive-technology patterns. Findings can identify an affected page or component, describe the potential user impact, reference relevant WCAG 2.1 AA guidance, and suggest a next step.
A Practical Good-Faith Process
We help organizations follow a practical process: review the current system, document observed barriers, prioritize higher-impact concerns, support reasonable improvements, and revisit the website as it evolves. The work is collaborative and depends on the project scope, available access, content, technology, and continued participation from the organization.
The Electron Monkey Approach
We use WCAG 2.1 AA requirements to guide our efforts, not as a guarantee. Whether we are supporting a system we built or reviewing an existing business website, we work to identify barriers and help make essential information and actions more usable for more people wherever reasonably possible.