Why Accessible Design Matters for ADHD: Our WCAG 2.2 AA Commitment

Many digital health products are designed without accessibility in mind. Users with ADHD often face additional barriers:

• Inability to zoom: Fixed zoom restrictions prevent users with visual impairments from reading text comfortably

• Poor keyboard navigation: Users who can't use a mouse are locked out

• No screen reader support: Blind and low-vision users get no information about form fields or interactive elements

• Tiny touch targets: People with fine motor control challenges (common in ADHD) struggle to tap 16px buttons on mobile

• Confusing form validation: Users with cognitive load issues don't know why their form submission failed

Fix 1: Removed userScalable=false from viewport — Users can now pinch-to-zoom on any page (WCAG 2.2 SC 1.4.4)

Fix 2: Added dynamic aria-labels to buttons — Icon-only buttons now announce their function to screen readers

Fix 3: Notification bell improvements — Live announcements via aria-live regions; count updates without requiring focus

Fix 4: Accessible form structure — <fieldset>/<legend> for grouped questions; aria-required and aria-describedby for clarity

Fix 5: Form validation regions — aria-live regions announce validation errors in real-time to screen readers

Fix 6: 44px minimum touch targets — All interactive elements meet WCAG 2.5.5 mobile touch target sizes

Fix 7: Navigation landmarks — aria-current='page' shows which page you're on; aria-label on all nav sections

Fix 8: Focus visible rings — Every interactive element shows a clear amber focus ring for keyboard navigation

Fix 9: Smart button states — aria-disabled, aria-busy, and aria-pressed attributes communicate button state accurately

Fix 10: Screen reader optimization — aria-hidden on decorative elements; proper heading hierarchy; semantic HTML everywhere

These changes help far more people than you might expect:

✓ Blind and low-vision users — Screen readers now announce form fields, buttons, and live updates accurately

✓ Motor impairment (including ADHD) — 44px touch targets eliminate mis-taps; keyboard-only navigation works

✓ Cognitive overload — Clear focus indicators, plain-English validation messages, and live region announcements reduce confusion

✓ Deaf users — Captions and transcripts (upcoming) will be properly labeled

✓ Aging users — Zoom support and larger touch targets help with presbyopia and arthritis

✓ Everyone on slow connections — Accessible semantic HTML is lighter and faster to load

WCAG 2.2 is the Web Content Accessibility Guidelines maintained by the W3C. Level AA is the industry gold standard—it's what major tech companies aim for and what regulations (AODA in Canada, Section 508 in the US, EAA in Europe) require.

Key improvements in WCAG 2.2 over earlier versions:

• SC 1.4.4 (Resize Text): Users must be able to zoom up to 200% without losing content

• SC 2.4.3 (Focus Order): Keyboard focus must follow a logical, meaningful order

• SC 2.4.4 (Link Purpose): All links must have clear, descriptive text (not 'click here')

• SC 2.5.5 (Target Size): All clickable/tappable targets must be at least 44×44 CSS pixels

• SC 4.1.2 (Name, Role, Value): All UI components must announce their purpose, state, and changes to assistive tech

By achieving Level AA, Sheldon.health is ensuring that ADHD assessment and management tools work for everyone—not just people without disabilities.

Beyond compliance, accessibility is deeply human. For many users, the ability to access a health tool without frustration is the difference between getting help and giving up.

Consider someone with ADHD who also has visual impairment:

Without accessibility: Can't zoom in to read questions → Can't use a screen reader because buttons have no labels → Abandons the assessment

With accessibility: Can zoom 150% to read comfortably → Screen reader announces each form section and field clearly → Completes the assessment and gets the support they need

That's the power of true accessibility. It's not charity. It's recognition that neurodivergent, disabled, and aging users deserve the same seamless experience as everyone else.

We're not stopping at WCAG 2.2 AA. Our roadmap includes:

• Video captions and transcripts (for news and educational content)

• Focus visible enhancements (thicker rings, better contrast in different lighting)

• Dyslexia-friendly font support (OpenDyslexic and Lexie Readable options)

• High-contrast mode styling (beyond system defaults)

• Simplified view mode (reduced cognitive load for overwhelmed users)

• ARIA landmarks and skip links (for power keyboard users)