Automated public first look
Run the free readiness check
Start from public, machine-detectable signals when you need a quick first look without admin access.
PathToProject Accessibility Readiness Check (opens in a new tab)
WordPress Accessibility Audit
Turn accessibility uncertainty into evidence, priorities and an actionable remediation backlog.
A manual WordPress Accessibility Audit examines an agreed sample of pages, templates and customer journeys using human judgment, keyboard testing, assistive technologies and authorized technical evidence.
Choose the smallest useful accessibility step
The free Check can surface public signals. The manual Audit tests agreed experiences and explains what to do next.
Paid Technical Audit module
Request the manual Audit
Use human testing when representative journeys, context, severity and remediation priorities must be understood.
When a manual Audit is the better fit
Keyboard or focus problems
Menus, dialogs, forms, skip links, focus order or visible focus do not work predictably without a mouse.
Screen-reader uncertainty
Page structure, labels, names, roles, status messages or dynamic changes need human verification.
Forms and critical journeys
Errors, instructions, validation, checkout, booking, enquiry or account journeys need representative testing.
Content and editor governance
Teams need reusable rules for headings, links, images, tables, documents, blocks and page-builder components.
Procurement or stakeholder evidence
A buyer, partner or internal team needs a bounded findings register and remediation plan—not an unsupported compliance claim.
WordPress implementation questions
The team needs to separate content, theme, plugin, block, page-builder, custom-code and third-party responsibilities.
Agreed Audit scope
The proposal names what is included, what remains outside scope and which evidence requires access.
Representative sample
Name the pages, templates, journeys, devices and browsers that matter instead of implying every state is covered.
Human interaction testing
Keyboard, focus, screen-reader and other assistive-technology checks appropriate to the agreed sample.
Manual criteria review
Selected Web Content Accessibility Guidelines (WCAG) criteria interpreted in the context of real content and journeys.
WordPress evidence
Theme, plugins, blocks, page builders and custom code can be reviewed when access is separately approved and necessary.
How the evidence is developed
- Confirm the question and sample. Identify critical journeys, representative templates, users and decision needs.
- Collect automated and manual evidence. Use automation as supporting evidence, then verify context through human testing.
- Trace ownership and likely cause. Separate content, design-system, theme, plugin, custom-code and third-party responsibilities where evidence allows.
- Prioritize remediation. Balance user impact, journey criticality, recurrence, implementation risk and dependency order.
- Agree the next gate. Fix with the client team, scope Delivery, run user testing or retest an approved remediation sample.
What the client receives
Finding register
Affected journey, evidence, relevant WCAG mapping, severity, priority and known limitations.
Ownership map
The most likely content, design, WordPress, vendor or governance owner for each remediation decision.
Remediation options
Practical fixes, dependencies, acceptance evidence and where deeper technical investigation remains necessary.
Prioritized backlog
A sequence that distinguishes immediate barriers, repeated component issues, content operations and longer-term improvements.
Stakeholder summary
A business-readable explanation of affected journeys, risk, limitations and the recommended next investment.
Optional retest
A separately agreed review of the remediated sample, with residual findings and evidence recorded.
Illustrative finding structure
This example shows the structure of a finding and is not taken from a client website.
Example finding
Checkout error message is not announced
- Affected journey
- Submit an incomplete checkout form and recover from the validation error.
- Evidence
- The visual error appears, but focus does not move and the status is not announced in the example state.
- User impact
- A screen-reader or keyboard user may not know why the transaction did not continue.
- Likely owners
- Form component, theme or checkout integration owner; final ownership requires technical evidence.
- Remediation direction
- Provide a programmatic error summary, associate field errors, manage focus and retest the complete journey.
Price range and scope factors
Prices are in USD. The final quote reflects the agreed pages, journeys, devices, browsers, access and evidence requirements.
Typical price range
Manual WordPress Accessibility Audit
From $1,250 USD
$1,250–2,750 USD
Manual Technical Audit module
Human review of an agreed page, template and workflow sample.
What changes the quote
Number and variety of journeys, templates, interactive states, devices, browsers, access, technical depth, stakeholder evidence and retest needs.
Remediation, user testing, formal conformance documentation and legal or regulatory advice are separate. Combined, multisite or portfolio scope may move into the Full or Complex Technical Audit range.
Compare all pricingImportant boundary
The Audit does not guarantee compliance, certify the website, test every assistive technology or cover every private and third-party state. It provides evidence and engineering priorities inside the explicitly agreed sample.
Request the shared Technical Audit intake
The Accessibility module is preselected when this link opens the shared Technical Audit intake. Do not place passwords, access keys or other credentials in the public form.
Transferable delivery experience
These projects demonstrate relevant delivery and governance disciplines. They are not presented as direct evidence of a formal Accessibility Audit.
Cross-platform experience
Organogenesis
A mixed-generation healthcare web portfolio modernized in phases through shared delivery, controlled releases, measurement integration and ongoing governance.
Frequently asked questions
What is the difference between the free Check and the manual Audit?
The free Check is an automated public first look. The manual Audit reviews an agreed sample of pages, templates and journeys using human judgment, keyboard testing, assistive technologies and additional evidence where authorized.
Does the Audit certify legal compliance?
No. It is an engineering and accessibility assessment, not legal advice, a universal certification or a guarantee of compliance. Any formal conformance document or legal review must be agreed separately.
What does the manual WordPress Accessibility Audit cost?
Accessibility Audit pricing starts at $1,250 USD, with a typical price range of $1,250–2,750 USD. Representative pages, journeys, devices, browsers, access and evidence requirements determine the final quote.
Does the Audit include remediation?
No by default. The deliverable explains evidence, impact, priority, ownership and remediation options. Production fixes, user testing, formal conformance documentation and retesting are separately scoped unless explicitly included.
What access is required?
Public evidence may be enough for some findings. Theme, plugin, block, page-builder, custom-code or private-workflow analysis uses only the access agreed after scope and authorization. Never place credentials in the public form.