How Publishers Can Clear Accessibility Backlogs Without Expanding Their Internal Team

How Publishers Can Clear Accessibility Backlogs Without Expanding Their Internal Team

Accessibility work rarely arrives as a single, predictable project.

A publisher may be producing new EPUBs and PDFs while simultaneously managing older titles that need accessibility remediation. Add complex tables, images requiring alternative text, footnotes, reading-order issues, document tagging, screen-reader testing, keyboard testing, and final quality assurance, and the workload can grow faster than an internal production team can absorb.

In many cases, the problem is not a lack of accessibility knowledge.

It is a capacity problem.

Production Directors and Accessibility Heads therefore face an important operational question:

How can we increase accessibility remediation capacity without continually expanding the internal team?

For many publishers, the answer is not to replace internal expertise. It is to build a production model in which internal specialists retain standards, governance, and final oversight while a qualified external accessibility partner provides additional remediation and QA capacity when volume increases.

Why Accessibility Backlogs Build Up in Publishing

Accessibility backlogs can develop even inside publishers with established accessibility processes.

The reason is simple: new production does not stop while legacy content is being remediated.

A production team may simultaneously need to manage:

• new EPUB and PDF releases;
• legacy-title remediation;
• accessibility corrections after QA;
• complex tables and document structures;
• alternative text requirements;
• screen-reader and keyboard testing;
• accessibility validation;
• vendor coordination;
• normal publishing-production deadlines.

When the same specialists are responsible for both current production and historical remediation, the backlog can continue increasing.

A small number of complicated files can also consume significantly more production time than expected. A document containing straightforward paragraphs and headings is very different from an academic publication containing nested tables, equations, figures, footnotes, references, and complex navigation.

That makes accessibility capacity difficult to forecast using title counts alone.

Accessibility Backlog Is Often a Production-Capacity Problem

Publishers sometimes approach accessibility backlog as if every problem can be solved through better tools.

Automated accessibility checking is valuable. It can identify many technical issues and support repeatable QA.

But automation does not eliminate the need for skilled remediation and human review.

For example, a tool may identify that an image has alternative text. It does not automatically prove that the description communicates the image's purpose effectively.

Similarly, automated validation may identify structural problems, but practical accessibility can also depend on whether:

• reading order makes sense;
• heading structure represents the content correctly;
• tables can be understood;
• links are meaningful;
• footnotes and endnotes work logically;
• keyboard navigation behaves correctly;
• assistive-technology users can understand the final content.

As the number and complexity of files increases, these activities create a production workload.

The commercial challenge therefore becomes:

Required accessibility volume > available specialist capacity

Once that happens consistently, publishers should evaluate whether additional external production capacity is more practical than allowing the backlog to continue growing.

When Should a Publisher Consider Accessibility Remediation Outsourcing?

Outsourcing should not automatically be the first solution.

If the internal team has sufficient expertise, predictable volume, and enough time to complete remediation without affecting other production, keeping the work internally may make sense.

External support becomes more valuable when there is a measurable capacity gap.

The Backlog Keeps Increasing

One of the clearest warning signs is when more inaccessible or partially accessible files enter the queue each month than the team can complete.

For example:

250 titles enter the remediation queue

but

150 titles are completed

The publisher has added another 100 titles to the backlog.

If this continues month after month, process improvements alone may not close the gap.

Additional production capacity may be required.

Current Titles Are Competing With Backlist Remediation

Current-title production usually has fixed publication schedules.

Backlist accessibility programmes may therefore receive lower priority whenever new titles require immediate attention.

This creates a cycle:

Current production takes priority → Backlist remediation slows → Backlog increases → Future remediation requirement becomes larger

A dedicated external remediation stream can help separate these workloads.

Complex Content Is Creating Bottlenecks

Not all titles require the same effort.

A publisher may process ordinary text-heavy content efficiently but encounter bottlenecks when files contain:

• complex tables;
• charts and diagrams;
• STEM content;
• equations;
• multi-level lists;
• footnotes and endnotes;
• complicated reading sequences;
• large numbers of images;
• unusual document structures.

Instead of expanding the entire internal team to handle occasional complexity peaks, publishers can use specialist external support for the files requiring additional production effort.

Accessibility QA Is Slowing Delivery

Sometimes remediation is not the bottleneck.

QA is.

A production team may be able to correct files quickly but still need sufficient capacity to verify the output through manual inspection, assistive-technology testing, keyboard testing, and final validation.

Increasing remediation throughput without increasing QA capacity simply moves the bottleneck to another stage.

Capacity planning should therefore consider the complete workflow.

Assessment → Remediation → Validation → Human QA → Corrections → Retest → Delivery

Outsourcing Does Not Mean Replacing the Internal Accessibility Team

This distinction is important.

A strong accessibility outsourcing model can preserve internal ownership.

The publisher's internal accessibility or production team can continue to control:

• accessibility policy;
• standards;
• acceptance criteria;
• vendor guidelines;
• escalation decisions;
• final governance.

The external production partner can provide:

• remediation capacity;
• backlist processing;
• accessibility QA;
• screen-reader testing;
• keyboard testing;
• alternative-text support;
• production support during volume peaks.

The model becomes:

Internal Team — Governance + Standards + Oversight

↓

External Accessibility Partner — Production + Remediation + QA Capacity

↓

Publisher — Acceptance + Release

This approach can be particularly useful when workload fluctuates.

Instead of maintaining permanent headcount for the highest possible production volume, publishers can increase external capacity when demand rises.

Three Accessibility Outsourcing Models Publishers Can Consider

There is no single outsourcing structure that works for every publisher.

The right model depends on volume, internal capability, deadlines, content complexity, and how much control the publisher wants to retain.

Overflow Accessibility Support

Overflow support is useful when the internal team can manage normal production volume but periodically reaches capacity.

For example, additional support may be required because of:

• a large release schedule;
• temporary staff shortages;
• accessibility deadlines;
• acquisitions;
• seasonal production peaks;
• unusually complex titles.

The external team handles defined overflow while the publisher retains its normal internal workflow.

This can be an effective first step because it allows the publisher to evaluate an accessibility partner without immediately transferring an entire programme.

Backlist Accessibility Remediation

Publishers with hundreds or thousands of legacy titles face a different problem.

The workload is not temporary.

There is a defined collection requiring systematic remediation.

A scalable backlist programme may therefore use a structured workflow:

Inventory

↓

Complexity Assessment

↓

Prioritization

↓

Remediation

↓

Accessibility QA

↓

Correction

↓

Retesting

↓

Approved Delivery

Prioritization is especially important.

Rather than treating every title identically, publishers can group files by factors such as format, complexity, commercial importance, usage, publication date, or remediation effort.

This makes capacity planning more realistic.

White-Label Accessibility Production

Accessibility companies and publishing service providers can face the same capacity problem as publishers.

They may win a large remediation programme but not want to permanently increase their production team.

A confidential white-label model allows an external specialist to provide production or QA capacity behind the primary provider's existing client relationship.

This can support:

• overflow remediation;
• accessible PDF production;
• accessible EPUB production;
• human accessibility QA;
• assistive-technology testing;
• backlist programmes.

For service companies, the commercial benefit is the ability to accept larger or more complex projects without building all production capacity internally.

File Complexity Should Determine Accessibility Capacity Planning

Counting files alone can produce misleading estimates.

Consider two 100-page PDFs.

The first contains:

• paragraphs;
• basic headings;
• simple images.

The second contains:

• complex tables;
• diagrams;
• equations;
• footnotes;
• multi-column content;
• intricate reading order.

Both are technically “100-page documents,” but their remediation requirements may be very different.

A useful accessibility programme therefore categorizes content by complexity before committing to production volume.

For example:

Low Complexity — primarily text, predictable structure, limited images.

Medium Complexity — tables, lists, figures, footnotes, or more complicated navigation.

High Complexity — STEM material, complex tables, charts, diagrams, equations, dense academic structures, or extensive alternative-text requirements.

This allows Production Directors to estimate capacity using actual production effort rather than simply counting titles or pages.

Human Accessibility QA Should Be Part of the Production Model

Automated accessibility tools are important because they can identify technical problems efficiently and consistently.

They should not be treated as the complete QA process.

A technically valid file can still create practical usability problems.

Human review can help evaluate questions such as:

Does the reading sequence make sense?

Can a screen-reader user understand the structure?

Are alternative descriptions meaningful?

Can interactive elements be reached and operated with a keyboard?

Does a complex table communicate its relationships clearly?

Do links and navigation behave as expected?

This is especially important for complex publishing content.

Gentize supports this stage with 50+ A11Y-certified testers with visual impairments, providing a human-led accessibility QA layer alongside production and technical validation.

The objective is not to replace automated testing.

It is to combine:

Automated Checks + Technical Review + Human Accessibility QA

so different types of accessibility problems can be identified before final delivery.

How to Pilot an Accessibility Partner Before Scaling

A publisher does not need to outsource thousands of files immediately.

A representative pilot can reduce risk.

The key word is representative.

Sending only the easiest files may prove that the vendor can process easy content, but it tells the publisher very little about how the provider will perform against the actual backlog.

A stronger pilot might include:

• two straightforward files;
• several medium-complexity files;
• a complex table-heavy document;
• an image-heavy title;
• a STEM or academic title where applicable;
• EPUB and PDF examples if both formats are in scope.

Then define the expected output and acceptance criteria before production begins.

A practical pilot workflow is:

Representative Files → Requirements → Remediation → Validation → Human QA → Corrections → Retest → Publisher Review

The publisher can then evaluate the actual results before increasing volume.

What Should Production Directors Measure During the Pilot?

A pilot should answer commercial and operational questions—not merely determine whether the vendor can return a file.

Remediation Quality

Are the accessibility issues actually corrected?

First-Pass Acceptance

How much of the delivered work meets requirements without additional correction?

A low first-pass acceptance rate can create hidden work for the publisher's internal team.

Rework

How frequently must files return for correction?

Complex-Content Capability

Can the provider handle difficult tables, images, navigation, STEM content, and unusual structures?

QA Quality

Is accessibility QA sufficiently thorough before files are delivered?

Turnaround

Can the provider meet realistic production schedules without sacrificing quality?

Communication

Are questions, exceptions, and ambiguous content escalated clearly?

Scalability

Can the quality demonstrated in a small sample be maintained when the programme expands?

This final question is critical.

Sample quality and production-scale quality are not automatically the same thing.

How to Scale From a Pilot to a Backlog Programme

Once a representative pilot has passed acceptance, the next step should not necessarily be moving the entire archive at once.

A controlled ramp-up can reduce risk.

For example:

10 files

↓

50 files

↓

100 files

↓

Larger production batches

At each stage, the publisher can monitor:

• acceptance rate;
• turnaround;
• recurring defects;
• communication;
• QA findings;
• capacity.

If performance remains stable as volume increases, the production relationship becomes easier to scale confidently.

What Should Remain Under Publisher Control?

Even when remediation is outsourced, publishers should maintain visibility over the programme.

Define:

• accessibility requirements;
• accepted standards;
• file specifications;
• naming conventions;
• QA expectations;
• escalation procedures;
• reporting requirements;
• acceptance process.

Outsourcing works best when responsibility is clear.

The external partner should not have to guess what “accessible” means for a particular publishing programme.

Likewise, the publisher should not have to inspect every production decision manually.

Clear requirements create a repeatable workflow.

How Gentize Can Support Accessibility Production Capacity

Gentize can support publishers, accessibility companies, and publishing service providers that require additional accessibility production or QA capacity.

Relevant support includes:

• accessible PDF remediation;
• accessible EPUB and EPUB3 production;
• backlist accessibility remediation;
• document structure and reading-order correction;
• alternative text support, including complex content;
• table accessibility;
• screen-reader testing;
• keyboard testing;
• accessibility validation;
• human-led accessibility QA.

For publishers with established internal teams, Gentize can function as additional production capacity rather than replacing internal accessibility ownership.

For accessibility companies and publishing service providers, the same production capabilities can support confidential white-label or overflow delivery.

Gentize's 50+ A11Y-certified testers with visual impairments provide an additional human QA capability for projects where practical assistive-technology experience is important.

The commercial model can therefore be adapted around the actual problem:

Temporary capacity shortage → Overflow support

Large legacy collection → Backlist remediation programme

Ongoing production demand → Dedicated external capacity

Service-provider volume → White-label production and QA

Accessibility Capacity Should Be Planned Before the Backlog Becomes Critical

A growing backlog becomes harder to solve the longer it is allowed to accumulate.

If a publisher is completing 200 files each month while 300 new files require attention, the problem is not going to disappear through prioritization alone.

At some point, additional capacity is required.

The objective should not simply be to outsource as much work as possible.

It should be to create the right balance between:

Internal expertise + External capacity + Repeatable QA

That gives publishers greater flexibility to address accessibility requirements without forcing current-title production and legacy remediation to compete continuously for the same internal resources.

Is Your Accessibility Backlog Growing Faster Than Your Team Can Clear It?

Instead of starting with a large outsourcing commitment, begin with a representative sample.

Share 5–10 PDF or EPUB files with Gentize, including examples of your more complex content.

Gentize can help evaluate the likely:

File Complexity → Remediation Workflow → Human QA Requirements → Production Capacity → Scalable Delivery Model

This provides a practical basis for deciding whether overflow accessibility support, backlist remediation, or an ongoing accessibility-production partnership is appropriate for your programme.

Discuss a representative accessibility sample with Gentize Innovations.