Expert agency inWeb Accessibilitywith WCAG 2.2 audit and end-to-end remediation.
We audit and remediate accessibility with professional judgment: WCAG 2.2 AA, EN 301 549 and Spain’s Royal Decree 1112/2018. No patchwork overlays. No accessibility statements that don’t survive a review. With documentation that stands up to the competent authority.
Accessibility “overlays” — those widgets that promise to automatically adapt any website — are being sued in courts around the world for deceptive practices. They don’t solve accessibility; they often make it worse. We do the opposite: honest audit, remediation with craft and documentation that stands up to external review.
Pieces of a serious accessibility program
We combine them based on starting point and regulatory urgency.
Technical audit
Manual (not just automated) review against WCAG 2.2 AA and EN 301 549. Report with prioritized issues, evidence and suggested remediation.
User audit
Tests with real users of assistive technology: screen readers, keyboard navigation, magnifiers. Insights heuristics don’t see.
Remediation
Implementation of prioritized fixes: semantic HTML, correct ARIA, contrast, visible focus, accessible forms, keyboard navigation.
Accessibility statement
Formal document required by RD 1112/2018 and the EU directive, with conformance level, non-conformities and contact. Ready for inspection.
Team training
Sessions for design, content and development. So new functionality ships accessible — not as new debt.
Continuous monitoring
Set up accessibility linters in CI/CD and automated pipeline tests. Accessibility is maintained, not frozen on audit day.
Five project phases
No magic phases. Everything verifiable.
- 01
Diagnosis
Technical audit + analysis of legal context (sector, type of organization, deadlines). Output: a report on the real state and regulatory exposure.
- 02
Prioritization
Non-conformities are ordered by user impact and legal criticality. Not everything is fixed at once — it’s fixed in order.
- 03
Remediation
Block-by-block implementation with continuous review. Fixed, verified, documented. No hidden debt.
- 04
Verification
Final audit (internal + tests with assistive-tech users) to certify real conformance. Outcome document.
- 05
Maintenance
Team training, linter integration in CI/CD, protocol for new development. Accessibility becomes a process, not a project.
Tools we work with
Automation + manual + real users. No single source of truth.
Automated audit
- axe DevTools
- WAVE
- Lighthouse a11y
- Pa11y
- IBM Equal Access
- Siteimprove
Assistive technology for testing
- NVDA
- JAWS
- VoiceOver
- TalkBack
- Dragon NaturallySpeaking
- ZoomText
CI/CD integration
- axe-core in Jest
- Cypress a11y
- Playwright a11y
- Storybook a11y addon
- ESLint jsx-a11y
- Pre-commit hooks
Documentation
- RD 1112 statement
- VPAT (US)
- ACR (US)
- WCAG-EM report
- Remediation roadmap
- Annual audits
Principles we apply on every project
Five commitments that define accessibility done with craft.
No patch overlays
We don’t install widgets that promise to “fix” accessibility. Evidence shows they worsen the experience and don’t prevent sanctions.
Semantic HTML first
Correct HTML comes before ARIA. “First rule of ARIA: don’t use ARIA if native HTML does the job.”
Tests with real users
No automated tool detects more than 30-40% of accessibility issues. Tests with assistive-tech users are irreplaceable.
Auditable documentation
Every conformance claim comes with evidence. Ready for Supervisory Authority inspection (Spain: OFISPE) without surprises.
Knowledge transferred
The internal team leaves understanding what to maintain. Accessibility must not depend on us being in perpetual support.
Honest questions before you hire
Is web accessibility mandatory in our case?
It depends. Public sector in Spain has been subject to RD 1112/2018 since 2018. Private sector falls under many categories with the European Accessibility Act (applicable from June 28, 2025). We start with an applicability analysis to know your exact exposure.
Isn’t installing an accessibility widget enough?
No. And it also exposes you. Multiple US court rulings and independent technical analyses have shown that overlays don’t solve accessibility and in many cases create new barriers. They are not defensible before a serious supervisory authority.
What happens if we’re reported for lack of accessibility?
It depends on jurisdiction and specific facts. In Spain there may be financial sanctions and remediation requirements from OFISPE. In the US there’s risk of an ADA lawsuit with high legal costs. In both cases, having an honest accessibility statement and an active remediation plan drastically reduces the risk.
Can an old website be made accessible, or does it need rebuilding?
It can almost always be remediated without rebuilding. It depends on the level of degradation. In some cases, certain modules (legacy widgets, old players) should be replaced — but this is not a general requirement.
Do you work with specialized partners if the case requires it?
Yes. We collaborate with assistive-technology user testers and with legal specialists when the case calls for it. No serious consultancy pretends to cover every front alone.
Does the European Accessibility Act apply to your sector?
Tell us your sector and digital product. We’ll look at applicability, exposure and what it would take to reach real conformance.
Let’s talk?Applicability analysis under NDA. No generic proposal.