Paper Boat Media / Website accessibility consulting

01 / 05

Make the next
step possible.

Website accessibility reviews, practical repairs and clear responsibility for the work.

01Define the task
02Find the barrier
03Repair the source
04Verify the result

01

Start with the task someone cannot finish.

A customer has chosen your business. They have read enough to trust you, found the service they need and decided to take the next step. Then the calendar will not work with their keyboard. The form reports an error without saying where it is. The menu is a photograph of tiny print. The appointment portal opens, but the person cannot get through it.

That is where I would start an accessibility project. The website has a job to do for a person, and something in the experience is preventing it.

Website accessibility consulting connects assessment, practical repairs, testing and ongoing responsibility so people with disabilities can use the information and services your website provides. The assignment might involve a small business website, a restaurant booking journey, a healthcare intake process or a much larger collection of pages and vendors. The useful scope follows those tasks.

I help owners understand what needs attention, which changes belong in their website, which require a vendor and how the work should be checked. Where a project requires specialist evaluation, formal procurement documentation or legal interpretation, that expertise belongs in the plan from the beginning. A consultant should be clear about the work they can own and the work that calls for another discipline.

The first conversation can be straightforward. Show me the site, tell me what people need to accomplish and share any audit, complaint, deadline or contractual requirement you already have. We can build a scope around the actual situation.

02

What an accessibility engagement should include

“Make the website compliant” can describe very different assignments. One owner needs a review of a dozen pages and a booking form. Another has thousands of documents, several domains, an online store and a customer portal maintained by a separate company. Both deserve a clear proposal, but they should not receive the same package with a different logo on it.

I would separate the work into deliverables you can recognize and evaluate.

Part of the engagement What you should receive What makes it useful
Scope and inventory Named pages, templates, documents, tools and user journeys You know what is included and what remains outside the review.
Assessment Reproducible findings with context and impact A developer can understand the failure and work on it.
Remediation Agreed changes to content, design, code or configuration The underlying barrier is addressed where the team has control.
Vendor coordination Specific issues, owners and requested fixes Problems inside another platform have an accountable route forward.
Verification Retest results and remaining limitations “Updated” has a more meaningful definition than a closed ticket.
Maintenance Publishing guidance and review responsibilities The next campaign or software update is less likely to undo the work.

An automated scan may be one input to that assessment. It is not the whole deliverable. I want the report to tell us whether somebody can complete the important journey, including the inconvenient parts such as an invalid entry, an unavailable appointment or an expired session.

03

Define the standard and the scope together.

WCAG is the technical reference most owners encounter. Its versions and conformance levels describe requirements for accessible content and interaction. They do not, by themselves, decide every organization’s legal obligations. My existing WCAG 2.2 versus 2.1 guide explains the technical differences.

For new work, I generally consider WCAG 2.2 Level AA a sensible practical target. The W3C Recommendation recommends adopting 2.2 even when formal obligations mention earlier versions. A contract, settlement or regulation still needs to be read on its own terms. “We used the latest version” is not a substitute for checking what the assignment actually requires.

A useful scope identifies the target version and level, the pages and processes being evaluated, the test environment, the treatment of third-party content and the evidence expected at completion. It also distinguishes a targeted review from a comprehensive conformance evaluation. Reviewing representative pages can help find shared defects; it does not justify an unsupported claim about everything on the domain.

For government and healthcare work, the applicability decision should involve the organization’s legal or compliance lead. I can translate the confirmed requirements into a practical website work plan. I do not offer legal opinions or promise that a particular product prevents a lawsuit.

04

Review the whole customer journey.

The homepage is often the most polished part of a website. It can also be the least revealing place to test whether the site works.

I would map what happens after a person arrives. For a restaurant, that could mean reading a menu, choosing a date, booking a table and finding the confirmation. For a professional firm, it could mean comparing services, attaching a document and submitting an inquiry. A patient may need to select a location, enter personal information and correct an insurance detail before requesting care.

Each transition matters. A beautifully accessible page can hand someone to an unusable tool. A form can work until an error message appears. A mobile menu can open successfully and then leave keyboard focus behind it.

The review should include ordinary content as well as interaction. Are headings meaningful? Do link names make sense? Does an image need a description, or is it purely decorative? Is important information available as text? Can a person increase text size without losing a control or its instructions?

My guide to testing websites with screen readers and other assistive technology explains the tools, the device and browser combinations, and the evidence a useful test record should contain.

I would also look at what happens when a visitor needs help. An accessibility statement should lead to a monitored contact route. The staff member receiving the request needs a practical way to help and a way to send the defect to whoever can repair it. A mailbox nobody checks creates another dead end.

05

Repairs should fit the website you have.

An accessibility assignment does not automatically require a rebuild. Sometimes the largest gains come from a shared navigation component, a form template or a publishing habit repeated across the site.

On WordPress, the barrier may originate in the theme, page builder, custom code or a plug-in. On Squarespace, some changes belong in native settings and content, while others may require carefully scoped code or a discussion about platform limitations. The platform name alone does not establish accessibility.

I prefer to understand the existing architecture before adding another layer. If a field label can be corrected in the form itself, that is a clearer maintenance arrangement than having a separate script guess its meaning on every page load. If a shared component needs replacement, the proposal should explain where it appears and what else depends on it.

The release process matters too. Back up the relevant work, use a suitable staging or preview environment, record the original behavior and check the changes before deployment. After release, test the live journey again. Caching, production settings and vendor scripts can create differences that a preview did not reveal.

If an internal designer or developer already knows the site, I can work with that person. If I handle the agreed work directly, you have one lead responsible for coordinating it. Either arrangement should make responsibility easier to understand.

06

Where accessibility software fits

An accessibility widget, scanner and manual audit are different purchases. A widget may offer visitor adjustments or attempt certain automated repairs. A scanner may identify potential problems and track changes. A manual evaluation investigates behavior and context that automation cannot fully determine.

The purchasing question is what each tool contributes to the work. I would want to know what it changes, which pages it covers, how it interacts with the site’s existing components and what remains unresolved. A badge or subscription invoice does not tell us that.

For products such as UserWay, the software fee should be visible in the proposal. So should the configuration, integration and testing effort. Traffic tiers, additional domains and optional services can affect the subscription. The account should have a clear owner and a renewal arrangement that the business understands.

I would test the site with the software enabled and compare it with the underlying experience. That helps identify both improvements and conflicts. Controls should remain usable, dialogs should behave predictably and the interface should not depend on a visitor discovering a particular widget before they can reach essential information.

The accessibility plug-in guide explains the buying decision in more detail, including the questions I would ask before making a product part of an engagement.

07

A repair plan you can actually manage

Here is an illustrative situation. A business has forty pages, but most use three templates. Its navigation has a keyboard problem, a shared form has unclear errors and a library contains several years of brochures.

Counting URLs might make this look like forty separate repair jobs. Looking at the architecture gives us a better plan. The navigation fix may improve the entire site. The form fix may address several inquiry pages. The brochures need their own inventory because a current application document and an old promotional flyer serve different purposes.

I would first identify the blocked tasks, then the shared causes, dependencies and repair owners. The documents would be assessed separately rather than quietly included in a vague promise to fix “the website.”

Finding First question Useful completion evidence
Navigation cannot be operated by keyboard Which shared component controls it? The relevant menu paths work without a mouse.
A submission error is unclear Can the visitor locate and correct the field? Invalid input is identified and can be corrected successfully.
An active brochure is difficult to read with assistive technology Is HTML or an accessible document the better delivery format? The information is available in a tested format.
A vendor tool blocks a task Who can change the component? A documented vendor repair, retest or workable replacement.

My guide to prioritizing accessibility repairs goes deeper into severity, shared reach and acceptance evidence. The goal is a work queue that helps the team make decisions, not a long spreadsheet that becomes more intimidating each time someone opens it.

08

What determines the price?

The cost follows complexity, access and responsibility. Page count is useful, but it is not enough. Ten pages with custom scheduling and payment can require more work than fifty straightforward editorial pages sharing a sound template.

I would consider the number of unique layouts, forms and interactive components; the document and media inventory; the platforms involved; the quality of the existing code; the required depth of evaluation; and whether your team or mine will implement the changes. Specialist testing, formal conformance reporting and complex application work should be identified explicitly.

A clear proposal separates the initial review and agreed implementation from recurring software and ongoing maintenance. It states how additional findings will be handled. Discovering a major issue should lead to an explanation and a decision before additional work is charged.

Be careful comparing a software-only price with a project that includes repairs. They may both contain the word accessibility, but they purchase different things. Equally, a higher price is not proof of a thorough review. Ask what is tested, who repairs it and what you receive when the work is finished.

I do not publish a universal “complete compliance” price because I cannot responsibly promise the same outcome for every website before seeing its moving parts. I can give a useful budget range after an initial look and confirm the agreed work before beginning.

09

What you should have when the project is finished

You should understand what was reviewed, what changed, how it was tested and what remains open. The work should leave you with more than a new icon in the corner of the screen.

I would expect a concise record of the evaluation scope, a repair log, verification notes, third-party dependencies and any maintenance instructions needed by your team. Where a formal conformance claim or procurement report is required, define that deliverable and its qualified evaluator separately.

The handover should be usable by the next person who updates the site. Explain how to add headings, label links, publish menu changes, manage images and check a form. Give staff a short release checklist tied to the things they actually change. A twenty-page policy that nobody uses is less helpful than a few clear responsibilities that survive a busy week.

Schedule the next review around meaningful changes. A new reservation provider, redesigned navigation or replacement page builder deserves testing. So does a newly introduced document workflow. Continuous attention does not have to mean constant disruption; it means knowing which changes could introduce a barrier and who checks them.

10

Accessibility, search and the rest of the business

Clear headings, useful text, understandable links and consistent business information can help people and machine systems interpret a page. That makes accessibility work a useful opportunity to notice related content problems.

I would still separate the claims. An accessibility widget is not an SEO strategy. Structured data does not make a website accessible. Neither purchase guarantees search rankings or inclusion in an AI answer. Google’s guidance for AI search features points back to familiar search fundamentals and says no special AI schema is required.

If a small, relevant improvement fits the agreed scope, such as making a menu easier to find or correcting incomplete business details, it can be included transparently. Larger changes belong in a separate discussion. An owner who asks for accessibility help should receive a clear answer to that need, without having to buy an unrelated marketing program.

Questions & answers

Questions owners ask

Can you guarantee that my website will never receive an ADA complaint?

No. I can define the work, document the assessment, implement agreed repairs and verify the results within scope. Legal exposure depends on facts beyond any single technical engagement. A promise that no one can bring a claim would be misleading.

Is installing UserWay enough?

Installation alone does not establish that people can use every relevant page or complete every task. The product needs evaluation in context, and the site may need direct repairs, document work or vendor changes. Start with the barriers and choose tools that contribute to addressing them.

Can you work with my current developer?

Yes. The proposal should assign assessment, implementation, vendor communication and approval responsibilities clearly. I can coordinate with an existing team or handle the agreed website work directly where access and the platform allow it.

Do all pages need to be checked individually?

The evaluation method depends on the scope. Shared templates and representative sampling can support an assessment, but unique content and complete processes still need attention. A limited review should be described as limited. W3C’s WCAG-EM methodology is a useful reference for structuring conformance evaluations.

Can accessibility work preserve the current design?

Often, much of it can. Some visual or interaction changes may still be necessary, such as improving contrast, providing visible focus or replacing a difficult control. The aim is an experience that remains recognizable while becoming more usable.

Are PDFs and third-party booking systems included?

Only when the scope says so. They should be inventoried early because they can be essential to the user journey. Vendor-controlled systems may require escalation or replacement, and extensive document remediation can be a substantial assignment of its own.

What should I send you first?

The website address, the important tasks visitors perform, any existing audit and any deadline are enough to start. If you know the platform and who maintains it, include those details. Administrative access can follow through an appropriate invitation when it is needed.

Sources & scope

Sources and further reading

This page describes a consulting approach, not legal advice or a certification of any website. Standards and sources checked October 20, 2026.

Choose the guide that fits your situation

Work with Rob

Tell me what your visitors need to do.

Bring the website, the concern and any deadline you are working toward. I will help identify a practical starting point, the people who need to be involved and a scope that makes the cost and responsibilities clear.

I am Rob Urban, founder of Paper Boat Media in DeLand, Florida. I work with organizations locally and remotely, connecting website decisions to the experience people have with the business.

I usually prefer our first conversation to be about an opportunity: attracting better customers, becoming more profitable, opening a location or building a stronger business. Sometimes a demand letter or another difficult challenge brings us together instead. I help with those situations too, including website issues that need to be addressed alongside legal counsel.

Accessibility remediation is one part of my work as a strategic growth advisor. My commercial strategy work also considers positioning, demand, customer experience and profitability. We can handle the immediate website problem with a clear scope, then discuss broader opportunities when they are useful to your business. Your attorney remains responsible for legal advice and the response to any claim.

Discuss your website with Rob or call or text 407-227-0741.

Work with a Florida website accessibility expert

Explore my Florida expert profile for qualifications, counsel-facing technical work and engagement roles. Family entertainment centers also have a dedicated guide.

Dr. Robert Urban: Florida ADA website expert and litigation consultant

Family entertainment center ADA website demand letters: party booking, waivers and remediation

Discuss an accessibility audit or remediation project

Share your website address, the tasks people need to complete, and any known accessibility barriers. Include an existing audit or deadline in your description, but leave confidential documents for a later conversation.

Name, email, and message are required. Organization or website is optional. Your information is used to respond to your inquiry. Privacy policy.

Paper Boat Media Contact

Prefer to talk? Call Rob: 407-227-0741 · Text Rob

I generally aim to respond within 24 hours. If I am traveling or deep in a project, I will get back to you as soon as I can.

Scroll to Top