Request a Website Remediation Quote: A Step-by-Step Guide

Table of Contents

• What You Need to Know Before Requesting a Website Remediation Quote
• Website Accessibility Audit Requirements and Pre-Quote Assessment
• Building Your Website Remediation Project Scope Template
• How to Request Your Website Remediation Project Quote
• Understanding Accessibility Remediation Timeline and Project Phases
• Evaluating Your Quote and What Comes After
• Common Mistakes to Avoid When Requesting a Remediation Quote
• Frequently Asked Questions

Last Updated: August 26, 2026

What You Need to Know Before Requesting a Website Remediation Quote

Before contacting a remediation provider, clarify three critical questions: What exactly is broken? Does your site need fixing or rebuilding? What will the actual scope of work look like?

Most organizations approach this backwards, contacting vendors with vague descriptions and receiving quotes that either shock them or seem too good to be true. A defensible remediation quote starts with you understanding your own situation.

Understanding website remediation scope

Website remediation identifies and fixes accessibility barriers, compliance gaps, and technical debt. This includes fixing broken navigation for screen reader users, correcting colour contrast ratios, adding missing alt text to images, and ensuring keyboard navigation works throughout your site.

Remediation scope varies dramatically by site size and complexity. A 50-page site with a handful of accessibility issues differs significantly from a 500-page site with embedded videos, PDFs, and complex interactive components. Custom-coded sites require different work than WordPress sites with third-party plugins.

Organizations often conflate "remediation" with "rebuild." They're not the same thing, and understanding the difference saves thousands in unnecessary work.

Remediation versus rebuild: Which path fits your needs

Remediation fixes specific, identifiable problems within your existing site structure without changing the underlying architecture. A rebuild means replacing the site entirely with new code, structure, and infrastructure.

Remediation is appropriate when your site works but has accessibility and compliance issues. Rebuild makes sense when your site's underlying code is so outdated it's becoming a liability, or when your business model has changed and the site can't support it.

The practical difference: remediation typically takes weeks to a few months; a rebuild takes months to over a year. Remediation costs a fraction of a rebuild but doesn't provide a clean slate. Choose based on your actual situation, not which is "better."

Website Accessibility Audit Requirements and Pre-Quote Assessment

You cannot request an accurate remediation quote without understanding what's actually wrong with your site. That requires an audit, conducted internally or by a professional, before contacting a vendor.

Conducting your internal audit

Start with a structured walkthrough. Interact with your site the way different users would.

Use a screen reader to navigate. NVDA (free, Windows) and JAWS (paid, Windows) are common; on Mac, use VoiceOver (built-in). Listen to how your site sounds when read aloud. You'll quickly discover missing alt text, broken heading structure, and navigation that fails without visual context.

Test keyboard navigation using only your keyboard. Can you reach every interactive element? Can you see focus? Does tab order make sense? Many sites work fine with a mouse but become unusable with keyboard-only navigation.

Check colour contrast using a free tool like WebAIM's contrast checker. WCAG 2.1 Level AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (w3.org).

Document every issue in a spreadsheet with the page URL, specific problem, and which accessibility standard it violates. This becomes your remediation roadmap.

WCAG compliance standards and Section 508 considerations

The Web Content Accessibility Guidelines (WCAG) 2.1 are the international standard for web accessibility (w3.org). They define four principles: perceivable (users can see or hear content), operable (users can navigate and interact), understandable (content is clear), and robust (it works with assistive technology).

WCAG has three compliance levels: A (minimum), AA (recommended), and AAA (enhanced) (w3.org). Most organizations target AA compliance, which regulators typically expect and covers the vast majority of accessibility issues.

In Canada, accessibility requirements vary by jurisdiction. Some provinces have specific legislation around digital accessibility. Regulated industries (finance, healthcare, public sector) face stricter requirements. Document which standard your organization must meet, this directly affects your remediation scope.

Building Your Website Remediation Project Scope Template

A strong scope document prevents quotes from ballooning mid-project. Document what you're asking the vendor to fix and what you're not.

Essential elements to document

Your scope document should include:

• Site inventory: How many pages need remediation?
• Content types: Does your site include videos, PDFs, interactive tools, embedded third-party content, or custom applications?
• Current issues: List the accessibility and compliance problems you've identified.
• Compliance target: Which standard are you targeting? WCAG 2.1 AA? A specific provincial requirement?
• Timeline: When do you need this complete?
• Team availability: How much can your internal team contribute?
• Post-launch support: Do you want ongoing compliance monitoring?

Vendors use this document to estimate actual work. Vague scope documents lead to vague quotes. Detailed scope documents lead to defensible quotes.

Defining document remediation versus web remediation

PDFs on your website that aren't accessible create barriers for users with disabilities. Document remediation involves fixing the PDF itself through tagging, metadata, and proper structure. Web remediation involves fixing HTML, CSS, JavaScript, and site structure.

Some vendors handle both; some specialise in one. If your site includes significant PDF content, clarify whether document remediation is included in the quote or a separate line item.

How to Request Your Website Remediation Project Quote

Once you have your scope document and audit findings, you're ready to request a quote.

Step 1: Gather your website inventory and technical details

Compile:

• Your site's URL and any subdomains
• The platform your site is built on (WordPress, custom code, Drupal, Shopify, etc.)
• The number of pages that need remediation
• Any third-party integrations or plugins
• Hosting details and server access information
• Content management system details and update access

Vendors need this information to understand technical complexity. A WordPress site with standard plugins differs significantly from a custom-coded application with dozens of integrations.

Step 2: Prepare your accessibility audit findings

Share your completed audit, including:

• Screenshots of accessibility issues
• A spreadsheet listing each problem, the page, and the standard it violates
• Screen reader recordings showing how your site sounds to users with visual disabilities
• Notes on keyboard navigation problems

This gives vendors concrete data instead of forcing them to audit your entire site. It also demonstrates you're serious and organised, typically resulting in more accurate quotes.

Step 3: Document your business requirements and timeline

Be explicit about:

Get Started Today →

• When you need remediation complete
• Which pages are highest priority
• Your compliance target standard
• Budget constraints, if any
• Whether you want ongoing compliance monitoring after launch

Step 4: Submit your request and ask the right questions

When submitting, ask:

• What's included in the quote and what's not?
• How will they test for compliance? (Automated testing alone is insufficient; you need manual testing.)
• What's the timeline for each project phase?
• How will they handle content updates during remediation?
• What happens after launch? Do they provide a compliance roadmap?
• Will they provide documentation of completed work?
• Do they offer a service level agreement or guarantee around compliance?

These questions separate vendors who understand remediation from those running automated tools only.

Understanding Accessibility Remediation Timeline and Project Phases

Remediation doesn't happen overnight. Understanding typical timelines and phases helps you plan internally and set realistic expectations.

Typical project phases and turnaround expectations

Most remediation projects follow this structure:

• Discovery and planning (1-2 weeks): The vendor reviews your site, confirms scope, and creates a detailed plan.
• Remediation work (4-12 weeks depending on site size): The vendor fixes accessibility issues, tests thoroughly, and documents changes.
• Testing and refinement (2-4 weeks): Independent testing with assistive technology users validates fixes work in the real world.
• Launch and monitoring (ongoing): The site goes live, and the vendor monitors for emerging issues.

A small site with limited issues might complete in 6-8 weeks. A large, complex site might take 4-6 months or longer.

Factors that affect remediation speed

Several variables change the timeline:

• Site complexity: Simple brochure sites are faster than complex applications with custom code.
• Content volume: More pages mean more work.
• Your team's availability: Quick approvals and content updates accelerate the project; slow approvals extend timelines.
• Testing requirements: Thorough testing with real users takes time but produces better results.
• Third-party dependencies: Waiting for third-party vendors to provide accessible versions slows the project.

Be realistic about your timeline. Aggressive deadlines compress the testing phase, where most problems surface.

Evaluating Your Quote and What Comes After

A good remediation quote tells you exactly what you're paying for. A vague quote is a red flag.

What a defensible quote includes

A strong quote specifies:

• The exact scope of work (which pages, which issues, which standards)
• The timeline for each phase
• The deliverables (remediated site, documentation, testing reports)
• What's included and what costs extra
• The cost structure
• Any assumptions the vendor made
• Post-launch support terms

A quote that says "website remediation: $X" without detail lacks clarity. A quote breaking down work by phase, page count, and issue type gives you defensible information.

Post-remediation maintenance and compliance roadmap

Remediation isn't the end. Your site will continue to evolve. New content, plugin updates, and third-party integrations can introduce new accessibility issues.

A good vendor provides a compliance roadmap: guidance on maintaining accessibility as your site evolves. This might include training for your team on accessible content creation, guidelines for testing new features, a schedule for periodic audits, and documentation of accessibility decisions.

Ask whether post-launch support is included in the quote or a separate service.

Common Mistakes to Avoid When Requesting a Remediation Quote

Don't request a quote without an audit. Vendors who quote without understanding your actual issues are guessing.

Don't assume all vendors approach remediation identically. Some rely heavily on automated tools; others use manual testing with real users. The quality and cost difference is substantial. Ask how they test.

Don't confuse a low quote with a good deal. Remediation is complex work. Quotes that seem too cheap often mean cutting corners on testing or planning change orders.

Don't ignore the timeline question. If a vendor promises to remediate a large site in three weeks, they're either not being thorough or overextending their team.

Don't forget to ask about post-launch support. Many organisations discover issues after launch that should have been caught during testing. Knowing whether your vendor will fix these at no cost prevents disputes later.

Don't assume your internal team understands how to maintain accessibility after the project ends. Ongoing maintenance requires training and processes.

Requesting a remediation quote is straightforward when you have the right information. Start with an audit. Document your scope clearly. Ask vendors the right questions. Evaluate quotes based on what's included, not just price.

The goal isn't finding the cheapest vendor. It's finding a vendor who understands your situation, delivers defensible work, and supports you after launch. That clarity comes from asking the right questions before you sign anything.

Concierge Brokers specialises in helping organisations move from vague remediation needs to clear, defensible projects. Our approach focuses on rigorous assessment, transparent scoping, and measurable outcomes. If you're ready to move forward with remediation, we can help you understand your options and create a roadmap that works for your organisation.

=== FAQ ANSWERS (audit these too, same rules) ===

[1] Q: What information should I include when I request a website remediation quote? A: Provide your website URL, current CMS platform, approximate page count, existing accessibility audit findings (if available), your target compliance standard (WCAG 2.1 AA or Section 508), and your desired timeline. Include details about any third-party integrations, forms, or dynamic content. The more specific your scope documentation, the more accurate your quote will be.

[2] Q: How do I determine the scope of a website remediation project before requesting a quote? A: Conduct a preliminary accessibility audit using both automated testing tools and manual review of critical user journeys. Document issues by category: alt text gaps, color contrast failures, keyboard navigation problems, and form accessibility. Note which pages are highest priority for your business. This pre-quote assessment helps providers give you a fixed price quote rather than an estimate, and clarifies whether you need full website remediation or targeted fixes.

[3] Q: What is the typical accessibility remediation timeline for a website project? A: Most remediation projects take 4-12 weeks depending on website size, complexity, and your compliance target. Small sites with straightforward fixes may complete in 4-6 weeks. Large sites with custom functionality, extensive PDF documents, or strict timelines for compliance certification may require 8-12 weeks or longer. Your provider should outline the project phases and service level agreement upfront when you request your quote.

[4] Q: Should I choose remediation or rebuild for my website accessibility project? A: Remediation fixes accessibility barriers within your existing website structure and is typically faster and lower cost. Rebuild replaces your site entirely, which is appropriate only if your current platform cannot meet compliance standards or your technical debt is too severe. Most organizations benefit from remediation first, then plan a rebuild during your next major redesign cycle. Your quote should clarify which approach the provider recommends and why.