Why it matters
Over 1 billion people worldwide live with some form of disability. Inaccessible websites exclude them from information, services, and opportunities — often illegally under international frameworks.
Resource Hub
Everything you need to
Everything you need to
understand accessibility
From foundational concepts to WCAG 2.1 AA checklists and expert answers — everything you need to understand digital accessibility, all in one place.
Accessibility Explained
What is digital accessibility?
Digital accessibility means building websites, apps, and content that everyone can use — including people with visual, auditory, motor, or cognitive disabilities.
"Accessibility is not a feature — it is the baseline of good design."
— Samatva Solutions
Who benefits
People using screen readers, keyboard-only navigation, switch access devices, voice recognition software, and those with low vision, colour blindness, deafness, or cognitive differences all rely on accessible design.
The four POUR principles
WCAG is built on four core principles: content must be Perceivable, Operable, Understandable, and Robust (POUR) — for all users across all assistive technologies.
Legal landscape
Accessibility is law in many countries — ADA (USA), EN 301 549 (EU), Accessibility for Ontarians with Disabilities Act (Canada), and India's RPWD Act 2016. Non-compliance carries real legal and reputational risks.
Business value
Accessible products reach wider audiences, improve SEO, reduce legal risk, and build brand trust. Studies show accessible sites often convert better and serve all users more effectively.
Web vs. native apps
Accessibility spans websites, web apps, mobile apps, PDF documents, email, and video content. Each medium has its own standards — but the POUR principles apply universally.
The POUR Principles — in depth
P
Perceivable
All information and UI components must be presentable in ways users can perceive. This means alt text for images, captions for video, sufficient colour contrast, and content that doesn't rely solely on one sense.
O
Operable
All UI components and navigation must be operable. Users must be able to navigate with a keyboard alone, avoid seizure-inducing flashes, and have enough time to complete tasks.
U
Understandable
Information and operation of the UI must be understandable. Language must be clear, layout consistent, errors descriptive, and instructions helpful for all cognitive abilities.
R
Robust
Content must be robust enough to be interpreted by a wide variety of assistive technologies — screen readers, magnifiers, voice control — now and in the future.
WCAG 2.1 Guide
Understanding WCAG 2.1 AA
The Web Content Accessibility Guidelines (WCAG) 2.1 are the international standard published by the W3C. Level AA is the most widely required compliance level.
Level A
Minimum
The bare minimum — removing the most severe barriers. Includes non-text content alternatives, captions, keyboard access, and no seizure-causing content.
- Text alternatives for images
- Captions for live video
- Keyboard accessible
- No keyboard traps
- Page language declared
Level AA ✓ Required
Industry Standard
The level required by most global laws and regulations. Removes significant barriers for users with visual, auditory, motor, and cognitive disabilities.
- 4.5:1 contrast ratio (normal text)
- 3:1 contrast ratio (large text)
- Resize text up to 200%
- Multiple navigation ways
- Error identification & suggestion
- Focus visible at all times
Level AAA
Enhanced
The highest level — not always achievable for all content. Provides enhanced support for users with the most severe accessibility needs.
- 7:1 contrast ratio
- Sign language for prerecorded audio
- Extended audio descriptions
- Reading level simplified
Key WCAG 2.1 AA success criteria
1.1.1
Non-text Content
All images, icons, and non-text elements must have text alternatives (alt text).
1.4.3
Contrast (Minimum)
Text must have a contrast ratio of at least 4.5:1 against its background.
2.1.1
Keyboard Access
All functionality must be accessible using a keyboard without requiring specific timing.
2.4.3
Focus Order
Focusable components must receive focus in a sequence that preserves meaning and operability.
2.4.7
Focus Visible
Keyboard focus indicator must be visible at all times on interactive elements.
3.3.1
Error Identification
Errors must be identified in text and described to the user clearly and specifically.
4.1.2
Name, Role, Value
All UI components must have accessible names, roles, and state information for assistive technology.
1.3.1
Info & Relationships
Structure, relationships, and meaning conveyed through presentation must be available via code (semantic HTML).
Frequently asked questions
Frequently asked
Frequently asked
questions
Common questions about accessibility audits, WCAG, and working with Samatva. No jargon — just clear, straightforward answers.
A WCAG audit is a systematic expert review of your website or application against the WCAG 2.1 AA success criteria. It combines automated scanning with manual testing using real screen readers and keyboard navigation — producing a detailed report of every accessibility barrier, its severity, the WCAG criterion violated, and developer-ready remediation guidance.
Typically 1–3 weeks depending on the size and complexity of your product. A small informational website may take 5–7 business days. A complex enterprise platform with multiple user journeys, dynamic content, and custom components can take 2–3 weeks. We always give you a clear timeline estimate after initial scoping.
Our reports include an executive summary for leadership, a full issue list with WCAG criterion references and severity ratings (critical / major / minor), screenshot evidence, step-by-step remediation guidance, and an overall conformance dashboard with a re-test schedule.
Yes. We produce Voluntary Product Accessibility Templates (VPAT) and Accessibility Conformance Reports (ACR) aligned to WCAG 2.1 and Section 508 — critical for enterprise procurement, government contracts, and US federal compliance.
Automated tools (axe, Lighthouse) flag clear code-level violations — but only catch ~30–40% of issues. The remaining 60–70% require manual expert testing: verifying alt text is meaningful, that screen reader announcements make sense in context, and that custom components are truly operable. Samatva always combines both approaches.
We are an independent audit firm — we deliberately do not perform remediation work to keep our findings fully unbiased. However, we provide developer-ready guidance with code examples, and support your team through Q&A sessions and a final re-test to verify fixes.