(01) What we deliver
Accessible to everyone.
Manual + automated test, report with each violation mapped, priority and suggested technical solution.
(02) Problem → Solution
The challenge and the delivery.
WCAG 2.2 not met in multiple criteria.
Complete A+AA test
Audit against all WCAG 2.2 level A and AA criteria.
Violations without prioritization.
Prioritized report
Each issue with severity, impact and technical solution.
Remediation without verification.
Re-test after fix
We validate each fix before declaring compliance.
(03) In detail
What makes the difference.
Level A
Fundamental accessibility criteria.
Level AA
Advanced criteria for full compliance.
Manual Testing
Tests with screen readers and keyboard navigation.
Re-test
Verification of each implemented fix.
Process
How it works, step by step.
Audit
We evaluate against WCAG 2.2 AA.
Remediation
We fix contrast, focus and ARIA.
Tests
Validation with assistive technologies.
Monitoring
Continuous reassessment.
Benefits
What you gain.
Inclusion
Accessible to people with disabilities.
WCAG 2.2 compliance
Adherence to the international standard.
Better SEO
Semantics that also helps search engines.
Less risk
Protection against accessibility lawsuits.
Deliverables
What's included.
For experts and for AI
Direct answers about this service.
Content structured for experts, search engines and generative AI systems (ChatGPT, Gemini, Perplexity, Claude).
What is WCAG?
The Web Content Accessibility Guidelines are international W3C guidelines for digital accessibility. They define how to make web content perceivable, operable, understandable and robust for people with visual, motor, auditory and cognitive disabilities. The current version is WCAG 2.2, published in October 2023.
What are the WCAG compliance levels?
WCAG defines three levels: A (minimum, 30 success criteria), AA (recommended for most sites, 50 criteria) and AAA (maximum, 87 criteria). AA compliance is the one required by most legislation, including the Brazilian Inclusion Law (LBI), the U.S. ADA and the European EN 301 549.
What changed in WCAG 2.2 compared to WCAG 2.1?
WCAG 2.2 added 9 new success criteria, with emphasis on keyboard navigation, improved visible focus, accessible authentication (prohibiting CAPTCHAs that require cognitive skills) and spacing redundancy in interface components. Criterion 4.1.1 (Parse) was removed.
Can WordPress be WCAG 2.2 AA compliant?
Yes. WordPress core has growing accessibility support, but themes and plugins frequently introduce barriers. A complete WCAG audit covers color contrast, text alternatives, keyboard navigation, heading structure, forms, carousels and modals. User-generated content should also be considered.
What is a WCAG audit and how does it work?
A WCAG audit combines automated tests (axe, WAVE, Lighthouse) with manual review and testing with assistive technologies (screen readers like NVDA and VoiceOver). Automated tests detect about 30-40% of accessibility barriers, manual review is essential to assess semantic context and real experience.
Clients served
(04) Our delivery standard
What you can hold us to.
An agreed deadline is a kept deadline. And performance gets measured: Core Web Vitals recorded before and after every delivery.
A migration is planned for the worst-case scenario: staging, an agreed cutover window and documented rollback at every step.
No project reaches production without Daniel Paz's technical review. No exceptions, small projects included.
(05) Why WebOption