Hidden interaction barriers
Focus may move unpredictably or a menu may not work from the keyboard.
Manual website accessibility assessment
Website accessibility audit
Find barriers that automated tools miss. Webmedic tests selected pages, components and critical user tasks, then presents the results in a prioritised report.
The exact audit scope is agreed before testing, so the report records what was tested, how it was tested and in which environment.
Why a manual audit matters
An automated score is not an accessibility audit.
Tools can find some code failures, but cannot reliably determine whether a person can understand the interface and complete a real task.
Unclear form errors
A field may have a label while still lacking useful instructions or error recovery.
Repeated component failures
One defect in a shared menu, modal or form component can affect many pages.
False confidence
A high automated score can hide serious keyboard and screen reader barriers.
What you receive
A report suitable for decisions and implementation.
Findings are written for business, product and development teams.
Prioritised issue register
Severity, affected users, location, evidence and a clear explanation.
Developer recommendations
Practical semantic, CSS, JavaScript, content or component guidance.
User-journey findings
The effect on registration, purchase, booking or account management.
Executive summary
Major risks, recurring causes and the recommended sequence of work.
Typical coverage
Typical audit coverage
A representative sample based on templates, components and important tasks.
Structure and semantics
Headings, landmarks, names, roles, states and relationships.
Content and presentation
Instructions, alternatives, contrast, zoom and responsive reflow.
Keyboard and focus
Order, visibility, navigation, dialogs and custom interactions.
Forms and errors
Labels, required fields, validation, summaries and recovery.
Assistive technology
Screen reader output, announcements and dynamic changes.
Responsive states
Mobile layouts, orientation, reflow and touch targets.
Process
A clear process from scope to verified results.
The exact environments, roles, journeys and deliverables are agreed before testing.
- 01
Agree the scope
Confirm priority pages, components, roles and user journeys.
- 02
Prepare access
Set up safe environments, accounts, data and known constraints.
- 03
Assess the behaviour
Run the agreed automated, keyboard, responsive and assistive technology checks.
- 04
Document or implement
Record actionable findings or apply agreed changes in the responsible layer.
- 05
Verify the outcome
Retest the original behaviour and complete affected journeys.
Who it is for
Teams that need reliable evidence before planning remediation.
The scope is adapted to the product, platform, team and delivery stage.
Business websites and digital services
E-commerce and booking journeys
SaaS products and customer portals
Agencies supporting client projects
Product, development and QA teams
Organisations operating in European markets
Why Webmedic
Technical accessibility work connected to real implementation.
Findings are written for action and consider shared components, application state and delivery constraints.
Developer perspective
User impact is connected to the responsible code and component behaviour.
Clear evidence
Location, state, reproduction steps and expected behaviour are recorded.
Root causes first
Repeated defects are grouped so shared causes can be addressed first.
Verification included
Agreed fixes can be retested against the original acceptance criteria.
Technical and legal scope
An audit is a defined sample, not a continuing compliance guarantee.
The service applies to the agreed pages, components, roles, content and tested version. New releases can introduce new barriers.
Third-party widgets and closed components can be assessed, but remediation may depend on the supplier or available extension points.
Webmedic provides technical accessibility assessment and implementation support using WCAG 2.2 Level AA as the primary reference. This is not legal advice, legal certification or a guarantee of compliance.
Frequently asked questions
Questions before you begin.
Before work starts, we agree the scope, pages, user journeys, deliverables and responsibility for implementation.
Ask another questionDoes the audit include automated scanning?
Yes, but automated checks are only one part of the audit and are supplemented by manual testing.
How many pages need to be tested?
It depends on the templates, components and user journeys. A representative sample is usually more valuable than many similar pages.
Do you test with a screen reader?
Yes. Targeted testing can be included for agreed pages and tasks.
Is the report suitable for developers?
Yes. Each finding includes evidence, impact, priority and practical remediation direction.
Can you verify the fixes?
Yes. The original findings and affected journeys can be retested after implementation.
Start with a reliable baseline
Want to know what is actually blocking users?
Send the website URL, platform and most important user journey. Webmedic will propose a specific audit scope.