A PDF can look perfectly normal on screen and still contain significant accessibility problems.

Headings may not actually be recognised as headings. Tables can lose their structure. Images may have no text alternative. Content can be presented to a screen reader in the wrong order, and scanned documents may contain no machine-readable text at all.

The good news is that many of these issues can be corrected through PDF accessibility remediation.

But not every problem is the same. Some issues can be repaired directly within the PDF, while others are better addressed in the original Word, PowerPoint, InDesign or other source document.

In this article, we look at some of the most common PDF accessibility problems, how they can be remediated and when professional document remediation services may be appropriate.

What Is PDF Accessibility Remediation?

PDF accessibility remediation is the process of identifying and correcting barriers that can make a PDF difficult or impossible for people with disability to use.

This can include technical problems within the PDF structure, such as incorrect tags or reading order, as well as issues with the way the original document was designed.

Depending on the document, remediation may involve:

• repairing the tag structure;

• correcting headings;

• fixing reading order;

• making tables accessible;

• adding or improving alternative text;

• remediating lists;

• repairing links;

• improving form accessibility;

• applying OCR to scanned content;

• setting document properties;

• identifying decorative content correctly; and

• addressing visual accessibility issues.

The exact work required depends on how the PDF was created and the complexity of the content.

1. Missing or Incorrect PDF Tags

Tags provide the underlying structure that helps assistive technologies understand the content of a PDF.

They can identify elements such as:

• headings;

• paragraphs;

• lists;

• tables;

• figures;

• links; and

• form elements.

A PDF may be completely untagged, or it may contain tags that are incorrect, incomplete or poorly organised.

Common problems include:

• headings tagged as ordinary paragraphs;

• paragraphs incorrectly identified as headings;

• content missing from the tag tree;

• duplicated tags;

• empty tags;

• decorative elements included unnecessarily;

• incorrectly nested structures; and

• tags appearing in an illogical sequence.

These problems can usually be repaired through PDF remediation.

Automatic tagging tools can provide a starting point, but the resulting structure still needs to be reviewed manually.

For a more detailed explanation, see How to Tag a PDF for Accessibility – and Why Tagging Alone Is Not Enough.

2. Incorrect Heading Structure

Headings are important because they help users understand how a document is organised.

A sighted reader may recognise a heading because it is larger, bold or a different colour. Assistive technology generally relies on the underlying structural information.

A document might visually appear to contain a clear hierarchy but actually use ordinary paragraph tags throughout.

Other common heading problems include:

• multiple H1 headings where only one is appropriate;

• skipped heading levels;

• headings used purely for visual styling;

• paragraphs incorrectly tagged as headings; and

• headings appearing in the wrong order.

During PDF accessibility remediation, the heading structure can be reviewed and corrected so that it more accurately reflects the organisation of the document.

3. Incorrect Reading Order

Reading order is one of the most important accessibility issues in complex PDFs.

A visually designed page may contain:

• two or more columns;

• text boxes;

• sidebars;

• captions;

• footnotes;

• tables;

• images; and

• callout panels.

A sighted reader can usually determine how these elements are intended to be read.

A screen reader follows the underlying document structure.

If that structure is incorrect, content may be announced in a confusing sequence.

For example, a screen reader might begin in the first column, jump to the footer, move to a sidebar and then return to the main text.

The content itself is technically present, but the experience can become extremely difficult to follow.

Reading-order problems can often be corrected by reorganising the tag structure and reviewing how page content is represented within the PDF.

4. Inaccessible Tables

Tables are one of the most common and technically challenging areas of PDF remediation.

A visual table may be easy to understand because a sighted reader can look across rows and columns.

Someone using assistive technology needs the relationship between headers and data cells to be communicated programmatically.

Common table problems include:

• missing table tags;

• header cells incorrectly identified as data cells;

• missing row or column headers;

• incorrectly nested table structures;

• merged cells that are difficult to interpret;

• multiple levels of headings; and

• tables created using spaces or tabs rather than a genuine table structure.

Many table issues can be repaired directly within the PDF.

However, particularly complex tables may be easier and more reliable to correct in the original source document before generating a new PDF.

5. Missing or Poor Alternative Text

Images that communicate meaningful information may require appropriate alternative text.

This can include:

• photographs;

• charts;

• graphs;

• diagrams;

• maps;

• illustrations;

• icons; and

• infographics.

One common problem is that the image has no alternative text at all.

Another is that alternative text exists but does not communicate anything useful.

For example:

“Graph”

is technically alternative text, but it tells the user almost nothing.

Similarly:

“Blue bar chart with red and green bars”

may describe what an image looks like without explaining the information the chart is intended to communicate.

Effective PDF accessibility remediation can include reviewing images and providing text alternatives that reflect their purpose and context.

Decorative images can also be marked appropriately so that they are not unnecessarily announced by screen readers.

6. Decorative Content Being Read by Screen Readers

Not everything visible on the page needs to be included in the accessible document structure.

Decorative content can include:

• background graphics;

• borders;

• repeated design elements;

• page decorations;

• visual separators; and

• purely ornamental images.

If these elements are incorrectly included in the tag structure, they can create unnecessary noise for someone navigating the document with assistive technology.

During remediation, decorative content can often be marked as an artifact so that it is ignored by screen readers.

This can make the document considerably easier to navigate.

7. Lists That Are Not Properly Structured

A list may look completely normal visually while having no meaningful list structure underneath.

For example, someone may have manually inserted bullet characters before each paragraph rather than creating an actual list.

Assistive technology may then read the content as a series of unrelated paragraphs.

PDF remediation can involve creating or correcting the underlying list structure so that users can identify:

• where the list begins;

• how many items it contains; and

• where each item starts and ends.

Nested lists can require additional attention to ensure their relationships remain clear.

8. Scanned or Image-Only PDFs

Scanned PDFs can present major accessibility barriers.

A document may look as though it contains ordinary text while actually consisting entirely of page images.

A screen reader cannot meaningfully interpret an image of text unless Optical Character Recognition, or OCR, has been applied.

OCR converts scanned text into machine-readable text.

However, OCR is only the first step.

The recognised text may still contain:

• spelling errors;

• incorrect characters;

• missing headings;

• no tag structure;

• incorrect reading order;

• inaccessible tables; and

• missing image descriptions.

A scanned document may therefore require both OCR and full accessibility remediation.

9. Inaccessible Links

Links within PDFs can also create accessibility problems.

Common issues include:

• links that are not included correctly in the tag structure;

• vague wording such as “click here”;

• long raw URLs used as link text;

• links with no meaningful accessible name; and

• visually styled text that looks like a link but is not interactive.

During remediation, links can be reviewed to ensure they are correctly identified and that their wording provides sufficient context.

Descriptive links can be particularly helpful to screen-reader users who navigate through a list of links separately from the surrounding text.

10. Inaccessible PDF Forms

Interactive forms require additional accessibility work.

A PDF form may look straightforward to someone using a mouse but be difficult to navigate using a keyboard or screen reader.

Problems can include:

• fields with no accessible label;

• confusing tab order;

• inaccessible instructions;

• required fields that are not identified;

• controls that cannot be operated by keyboard;

• unclear error messages; and

• fields appearing in the wrong position within the document structure.

PDF accessibility remediation can address many of these issues by reviewing field labels, keyboard operation, tab order and the relationship between form controls and surrounding instructions.

11. Missing Document Language

Setting the document language helps compatible assistive technologies determine the correct pronunciation rules.

If the language is missing, a screen reader may not know how the text should be pronounced.

A PDF may also contain sections written in a different language from the rest of the document.

These properties can often be corrected as part of the remediation process.

12. Missing or Incorrect Document Title

A PDF can contain a file name without having a meaningful document title.

For example:

final-report-v7-approved.pdf

may be the file name, but it is not necessarily a useful title.

A meaningful document title can help users understand what they have opened, particularly when working with multiple documents.

Document properties such as title and language are often simple to correct but can easily be overlooked.

13. Problems with Bookmarks and Navigation

Long documents can benefit from bookmarks that allow users to jump directly to major sections.

Annual reports, policy documents, research publications and manuals may become difficult to navigate when users have to move through dozens or hundreds of pages sequentially.

Bookmarks can often be added or repaired during PDF remediation.

However, bookmarks do not replace a meaningful heading structure. Ideally, both should work together to make a long document easier to navigate.

14. Poor Colour Contrast

Some PDF accessibility problems are visual rather than structural.

Text may not have sufficient contrast against its background.

For example:

• light grey text on white;

• coloured text over photographs;

• pale text on coloured panels; or

• low-contrast chart labels.

These issues may affect people with low vision or colour-vision deficiencies.

Contrast problems may sometimes be repairable within the PDF, but in many cases it is preferable to change the original source document and regenerate the PDF.

This is particularly true when the PDF has been created from a professionally designed source such as Adobe InDesign.

15. Information Communicated Using Colour Alone

Colour can be useful for communicating information, but it should not generally be the only way that information is conveyed.

For example, a chart might identify:

• green as “complete”;

• orange as “in progress”; and

• red as “overdue”.

Someone who cannot distinguish those colours may have difficulty interpreting the chart.

Additional information might be communicated using:

• labels;

• patterns;

• icons;

• text; or

• other visual indicators.

Problems like this usually need to be addressed within the source document rather than solely through PDF tagging.

16. Text Embedded in Images

Text that has been converted into an image can create accessibility problems.

Assistive technology cannot interpret text inside an image in the same way that it can interact with real document text.

This is commonly found in:

• infographics;

• diagrams;

• screenshots;

• advertisements;

• charts; and

• designed promotional material.

Depending on the purpose of the image, remediation may involve:

• providing an appropriate text alternative;

• recreating the text as real document content;

• providing a longer description; or

• modifying the original source document.

17. Complex Charts and Diagrams

Charts and diagrams can contain information that is difficult to represent with a short alternative-text description.

A simple image may only require a concise description.

A complex chart may need its key findings communicated in surrounding text or through a more detailed alternative.

In some cases, providing access to the underlying data may also be appropriate.

This is an area where professional judgement matters.

The objective is not merely to satisfy an automated checker by filling in an alt-text field. The important question is whether a user can obtain the information the graphic is intended to communicate.

18. Keyboard Navigation Problems

Accessibility does not only concern screen readers.

Some users navigate entirely by keyboard.

Interactive elements such as links and form fields should generally be reachable in a logical order without requiring a mouse.

Problems with keyboard navigation can include:

• unexpected tab order;

• controls being skipped;

• focus moving to unrelated areas;

• inaccessible form elements; and

• interactive content that cannot be operated from the keyboard.

These issues can often be reviewed and corrected as part of professional PDF remediation.

Can Every PDF Accessibility Problem Be Fixed?

Many problems can be fixed, but the best approach depends on the document.

Some issues can be corrected directly within Acrobat or another specialist PDF remediation tool.

Other problems are better addressed within the original source file.

For example, it may be possible to repair a heading structure directly in the PDF.

But if an entire annual report has poor colour contrast, inaccessible chart designs and text embedded inside graphics, trying to repair everything solely within the finished PDF may be inefficient.

In that situation, the more effective process may be:

1. correct the source document;

2. export a new PDF;

3. remediate the resulting PDF structure; and

4. test the final document.

Access to the original source files can therefore make a significant difference to a remediation project.

How Do You Know Which Problems Your PDF Has?

The first step is usually an accessibility assessment.

Automated tools can identify many technical problems, but some issues require manual review.

For example, software may be able to tell you whether an image has alternative text.

It cannot reliably determine whether that alternative text actually communicates what the image means.

Similarly, a table may technically contain table tags while still being confusing when navigated with assistive technology.

This is why accessibility testing commonly combines automated checks with manual inspection.

For more information, see How Do You Know if a PDF Is Accessible?.

When Are Professional PDF Remediation Services Recommended?

Simple PDFs may sometimes be remediated internally by someone with the appropriate software and accessibility knowledge.

Professional assistance becomes particularly useful when documents contain:

• complex tables;

• charts and diagrams;

• forms;

• scanned content;

• multi-column layouts;

• large numbers of images;

• complicated tag structures;

• substantial design accessibility issues;

• large page counts;

• multiple documents; or

• important compliance or publication requirements.

Professional PDF remediation services can also save organisations from having to develop specialist remediation expertise internally for a task they may only encounter occasionally.

PDF Accessibility Remediation from Atomic Web Strategy

Atomic Web Strategy provides professional document remediation services for organisations that need accessible PDFs and digital documents.

We can assist with:

• individual PDFs;

• reports;

• forms;

• annual publications;

• policies and procedures;

• scanned documents;

• complex tables;

• document collections; and

• editable source documents such as Word, PowerPoint and InDesign files.

Our work can include reviewing the existing document, identifying accessibility barriers, remediating the PDF or source file, and completing appropriate accessibility testing.

Where a document contains issues that cannot reasonably be corrected within the PDF alone, we can also identify where changes to the original source document may provide a better outcome.

Need Help Fixing an Inaccessible PDF?

Most PDF accessibility problems can be improved, but the amount of work required varies considerably from one document to another.

A simple text-based PDF may require relatively minor structural corrections, while a designed report containing tables, charts, forms and complex page layouts may require much more detailed remediation.

If you are unsure what accessibility problems are present in your documents, Atomic Web Strategy can review a representative file and advise what is involved.

Visit our PDF and document remediation services page or send us a sample PDF and the editable source file where available.

We can assess the document and provide a clear remediation scope and quotation.

PDF remediation is the process of identifying and correcting accessibility barriers within a PDF document so that its content can be more effectively understood, navigated and used by people with disability.

At first glance, this can sound relatively simple. Add accessibility tags, run a checker and fix whatever errors appear.

In practice, effective PDF remediation can involve much more.

A PDF may need its underlying structure repaired, its reading order corrected, images described, tables rebuilt, forms labelled and scanned text recognised. Problems within the original visual design may also need to be addressed before an accessible PDF can be produced.

This article explains what PDF remediation involves, why automated fixes are rarely the whole solution and when professional PDF remediation services may be appropriate.

What Is PDF Remediation?

PDF remediation is the process of modifying an existing PDF to remove or reduce barriers that can prevent people with disability from accessing its content.

Many of these barriers are invisible to someone reading the document visually.

For example, a PDF may appear to contain:

• a clear title;

• logical headings;

• neatly formatted paragraphs;

• bullet lists;

• well-designed tables;

• photographs and diagrams; and

• links to useful information.

However, the underlying document might tell a screen reader something very different.

The title may simply be large bold text rather than a heading. Lists may contain no meaningful list structure. A table may be announced as an unrelated sequence of words and numbers. An image may provide important information without any alternative text.

PDF remediation addresses this underlying accessibility information as well as other barriers within the document.

Adobe explains that document structure tags help assistive technologies identify elements such as headings, paragraphs, sections and tables and determine an appropriate reading order. (Adobe – Accessibility features in PDFs)

Why Do PDFs Need Remediation?

PDFs are often created primarily with visual presentation in mind.

A designer can arrange content so that its relationships are immediately obvious to someone viewing the page. Assistive technology cannot necessarily infer those same relationships from appearance alone.

Problems can also arise during conversion from the original source document into PDF.

For example:

• heading information may be lost or incorrectly transferred;

• content may appear in the wrong reading order;

• tables may not convert with the required structure;

• graphical elements may be included unnecessarily in the tag tree;

• form fields may not have meaningful labels;

• images may be missing text alternatives; and

• complex page layouts may produce an incorrect document structure.

Older documents can present additional problems because they may have been created before accessibility was considered.

Scanned PDFs can be particularly problematic. A scanned page may look like ordinary text to a sighted reader but actually consist of a single image. Unless Optical Character Recognition (OCR) has been applied, assistive technology may have no text available to read.

W3C’s PDF accessibility techniques specifically cover areas including reading order, image alternatives, tables, OCR, headings, forms and links. (W3C – PDF accessibility techniques)

What Does PDF Remediation Involve?

The work required depends on the individual document.

A simple text-based PDF may require relatively little intervention. A designed annual report containing tables, charts, multi-column layouts and infographics can require considerably more.

Professional PDF accessibility remediation may involve some or all of the following areas.

1. Reviewing the Existing PDF

Before beginning remediation, it is useful to understand how the document has been constructed and what accessibility information already exists.

An initial review may examine:

• whether the PDF is tagged;

• the quality of the existing tag structure;

• heading hierarchy;

• reading order;

• images and alternative text;

• tables;

• lists;

• links;

• bookmarks;

• forms;

• document properties;

• scanned content;

• visual design; and

• the availability of the editable source document.

Running an automated accessibility checker can help identify some technical problems, but it is only part of this assessment.

Some issues require a person to determine whether the existing accessibility information is actually meaningful.

For more information, see How Do You Know if a PDF Is Accessible?.

2. Creating or Repairing the PDF Tag Structure

Tags provide semantic information about the content within a PDF.

They can identify elements such as:

• headings;

• paragraphs;

• lists;

• list items;

• tables;

• table headings and cells;

• figures;

• links;

• quotations; and

• other document elements.

The tags are organised into a structure tree that helps compatible assistive technologies understand how the content relates.

An untagged PDF may need an initial tag structure created. An already tagged document may still require extensive correction.

Common problems include:

• incorrect tags;

• missing tags;

• unnecessary tags;

• empty tags;

• duplicated content;

• improper nesting; and

• content appearing in the wrong part of the structure tree.

Automatic tagging can provide a useful starting point, particularly for simpler documents, but it does not remove the need for review.

We discuss this process in more detail in How to Tag a PDF for Accessibility – and Why Tagging Alone Is Not Enough.

3. Correcting the Heading Structure

Headings do more than make a document visually attractive.

A meaningful heading hierarchy provides structure that can help people understand and navigate the content.

For example, a document might contain:

• H1 for the document title;

• H2 for major sections; and

• H3 for subsections within those sections.

Simply making text large, bold or a different colour does not make it a structural heading.

During PDF document remediation, headings may need to be identified correctly within the tag structure and checked to ensure that the hierarchy accurately represents the organisation of the document.

4. Repairing the Reading Order

Reading order determines the sequence in which content is presented to assistive technologies.

This can become particularly important in pages containing:

• multiple columns;

• sidebars;

• text boxes;

• captions;

• footnotes;

• tables;

• forms;

• charts; or

• complex graphical layouts.

Imagine a two-column report.

A sighted reader naturally reads down the first column and then moves to the second. If the underlying PDF structure alternates between the two columns line by line, a screen reader may present the content in an order that makes little sense.

W3C identifies correct reading and tab order as a specific PDF accessibility technique, while Adobe provides tools for manually inspecting and repairing reading order. (W3C – Ensuring correct tab and reading order)

Reading order therefore needs to be evaluated rather than assumed from the visual appearance of the page.

5. Remediating Lists

Lists also require meaningful structure.

A visual bullet or number on the page does not necessarily mean the PDF contains an accessible list.

A properly structured list needs to identify the list itself and its individual list items. Depending on the structure, the bullet or number and its associated content may also need to be represented appropriately.

Nested lists can require additional attention so that their relationships remain understandable.

6. Making Tables Accessible

Tables can be among the most time-consuming elements to remediate.

A simple table may need appropriate identification of:

• the table;

• rows;

• column headings;

• row headings; and

• data cells.

The relationships between headings and data are particularly important.

A sighted reader can often look across a row or up a column to determine what a particular value represents. Someone navigating the same table with assistive technology needs those relationships communicated through the document structure.

Complex tables involving merged cells, multiple header levels or unusual layouts may require substantial manual work.

W3C includes the use of appropriate table elements as one of its PDF accessibility techniques. (W3C – PDF accessibility techniques)

7. Adding and Reviewing Alternative Text

Meaningful images may require a text alternative.

These can include:

• photographs;

• charts;

• graphs;

• diagrams;

• maps;

• illustrations; and

• icons.

Effective alternative text does not necessarily describe everything visible in an image.

It should communicate the purpose or information the image contributes within its particular context.

For example, describing a chart merely as “bar graph with blue and green bars” may not provide the information the chart was included to communicate.

Conversely, a decorative image that adds no meaningful information generally should not be announced unnecessarily by a screen reader.

Part of PDF remediation can therefore involve distinguishing meaningful content from decorative content and determining the appropriate treatment for each.

8. Identifying Decorative Content

PDFs frequently contain visual elements that contribute to the design but not the meaning of the document.

Examples might include:

• decorative borders;

• background shapes;

• repeated design elements;

• ornamental graphics; and

• purely decorative images.

If these elements remain unnecessarily within the accessibility structure, they can create noise for someone navigating the document with assistive technology.

Decorative elements can be identified as artifacts so that they are excluded from the meaningful document structure.

9. Remediating Links and Bookmarks

Links need to be appropriately included within the accessible structure of the document.

Their wording also matters.

A list of links all labelled “click here” provides very little information when someone navigates through them independently of the surrounding paragraph.

More descriptive wording can help communicate the purpose or destination of the link.

Longer PDFs may also benefit from bookmarks that provide another way to move between major sections of the document.

10. Making PDF Forms Accessible

Interactive PDF forms introduce additional accessibility considerations.

Form remediation may include:

• providing meaningful accessible names for fields;

• associating labels with controls;

• identifying required fields;

• providing appropriate instructions;

• establishing a logical tab order;

• checking keyboard operation; and

• ensuring that fields appear appropriately within the document structure.

A form can work perfectly well with a mouse while presenting significant difficulties to someone navigating by keyboard or using a screen reader.

Adobe’s PDF accessibility tools include functionality for working with form fields, labels and reading order. (Adobe – Reading Order tool)

11. Applying OCR to Scanned Documents

Scanned PDFs often need Optical Character Recognition before meaningful remediation can begin.

OCR converts images of text into machine-readable text.

However, applying OCR does not automatically create an accessible document.

The recognised text still needs to be reviewed, particularly where the scan quality is poor. The document may then require:

• tagging;

• headings;

• reading-order correction;

• lists;

• table remediation;

• alternative text; and

• other accessibility work.

W3C specifically identifies OCR as a technique for providing actual text in scanned PDF documents. (W3C – PDF accessibility techniques)

12. Checking the Document Properties

PDF remediation can also include reviewing document-level information such as:

• document title;

• primary language;

• language changes within the content;

• bookmarks;

• metadata; and

• security settings that could interfere with assistive technology.

These details may not be obvious when looking at the page itself, but they can affect how the document is identified and interpreted.

Is PDF Tagging the Same as PDF Remediation?

No.

Tagging is an important part of PDF remediation, but it is only one part.

A document can contain tags and still have significant accessibility problems.

For example:

• headings may use the wrong tag;

• reading order may be incorrect;

• tables may be structured poorly;

• alternative text may be meaningless;

• forms may be difficult to navigate;

• text may have insufficient contrast; or

• graphical information may not have an accessible alternative.

This is why simply clicking an automatic tagging option should not be confused with completing PDF accessibility remediation.

The objective is not merely to produce a tagged document. It is to create a document structure and experience that meaningfully communicates the content.

Can PDF Remediation Be Automated?

Automation can make parts of PDF remediation faster, but it cannot reliably make every accessibility decision.

Automated tools can identify many technical conditions.

For example, they may be able to detect that:

• a PDF has no tags;

• an image is missing alternative text;

• a document language has not been set;

• certain content is not tagged; or

• an expected structural element is absent.

What the software may not be able to determine is whether the result makes sense.

It cannot reliably answer questions such as:

• Is this the correct heading level?

• Does this alternative text communicate the image’s purpose?

• Is this decorative image correctly excluded?

• Does this page make sense in the current reading order?

• Are these table relationships meaningful?

• Is this link understandable out of context?

Those decisions require context and human judgement.

For this reason, professional PDF remediation services generally combine specialist software with manual inspection and testing rather than relying entirely on automation.

What About Problems in the Original Document Design?

Not every accessibility issue can or should be fixed solely within the final PDF.

Some problems originate in the source document itself.

These can include:

• insufficient colour contrast;

• information communicated using colour alone;

• difficult-to-read typography;

• text embedded within graphics;

• inaccessible charts;

• complicated visual layouts;

• poor table design; and

• other content or design barriers.

If the original Word, PowerPoint, InDesign or other editable document is available, it may be more appropriate to correct these problems at the source.

A new PDF can then be generated and its technical accessibility structure reviewed and remediated.

This is one of the important distinctions between PDF remediation and broader document remediation.

How Are Remediated PDFs Tested?

Accessibility testing typically involves a combination of automated and manual checks.

Automated validation can efficiently identify many technical issues, while manual review is needed for areas that depend on meaning and context.

Depending on the agreed project requirements, testing might examine:

• tag structure;

• heading hierarchy;

• reading order;

• tables;

• alternative text;

• lists;

• links;

• forms;

• keyboard navigation;

• document properties;

• scanned content; and

• other relevant accessibility features.

Documents may also be assessed against an agreed accessibility standard such as PDF/UA or applicable WCAG requirements.

Importantly, passing an automated accessibility checker should not by itself be treated as proof that every accessibility decision within the document is correct.

Which Documents Commonly Need PDF Remediation?

Almost any organisation publishing documents digitally can encounter accessibility issues.

Common examples include:

• annual reports;

• research reports;

• government publications;

• policies and procedures;

• consultation documents;

• fact sheets;

• application forms;

• financial reports;

• university and educational material;

• manuals;

• brochures;

• conference material; and

• historical document collections.

The complexity of remediation depends much more on the content and structure than simply the number of pages.

A short PDF containing several complicated tables and diagrams may require considerably more work than a long, straightforward text document.

When Should You Use Professional PDF Remediation Services?

Organisations may be able to remediate simple documents internally when staff have the appropriate software, knowledge and time.

Professional PDF remediation services are particularly useful when documents contain:

• complex tables;

• charts and diagrams;

• forms;

• scanned material;

• multiple columns;

• unusual layouts;

• significant design accessibility issues;

• large numbers of pages or documents; or

• firm publication deadlines.

Specialist assistance can also help where an organisation has received accessibility audit findings but does not have the internal resources to remediate its document library.

What Do PDF Remediation Services Include?

The exact scope will depend on the files and project requirements, but PDF remediation services can include:

• reviewing the existing document;

• assessing available source files;

• creating or repairing PDF tags;

• establishing a meaningful heading structure;

• correcting reading order;

• remediating lists;

• repairing table structures;

• adding or reviewing alternative text;

• identifying decorative elements;

• improving links and bookmarks;

• remediating form fields;

• applying and checking OCR;

• setting document properties;

• addressing keyboard and tab order;

• correcting accessibility issues within editable source files; and

• completing automated and manual accessibility testing.

For larger document collections, remediation may also involve prioritising documents and establishing a staged approach rather than attempting to address every file simultaneously.

PDF Remediation Services from Atomic Web Strategy

Atomic Web Strategy provides professional PDF remediation services for organisations that need accessible PDFs and digital documents without adding a complex specialist task to their internal workload.

We can assist with individual documents, complex reports, forms, recurring publications and larger document collections.

Where editable source files are available, we can also address accessibility barriers within the original document before producing and remediating the final PDF.

Our process can include:

• reviewing a representative document;

• identifying technical and design accessibility issues;

• establishing the appropriate remediation approach;

• providing a clear project scope and quotation;

• completing technical and source-document remediation;

• testing the completed documents; and

• identifying any limitations that cannot be corrected within the available files or agreed scope.

Need Help with PDF Remediation?

PDF remediation is much more than adding tags or running an automated accessibility checker.

Depending on the document, it can involve structure, reading order, headings, tables, images, forms, scanned content, navigation, visual design and detailed manual testing.

If your organisation has PDFs that need accessibility work, Atomic Web Strategy can review a representative file and determine what remediation is required.

Visit our document and PDF remediation services page or send us a sample PDF, the editable source document where available, your approximate page count and required completion date.

We can then assess the project and provide a clear scope and quotation.

A PDF may look perfectly fine on screen and still contain significant accessibility barriers.

Headings can look like headings without being identified as headings. A table can be easy to understand visually but make little sense when read by a screen reader. Images may contain important information with no text alternative, and a document that appears to contain normal text may actually consist entirely of scanned images.

So, how do you know if a PDF is accessible?

The answer involves more than running an automated accessibility checker and looking for a green tick. Proper PDF accessibility testing requires a combination of automated checks, manual inspection and an understanding of how people using assistive technologies interact with documents.

What Does an Accessible PDF Look Like?

There is not necessarily any visual difference between an accessible PDF and an inaccessible one.

Many of the features that make a PDF accessible sit behind the visible document.

An accessible PDF will generally have a logical underlying structure that allows assistive technology to understand the content. Depending on the document, this can include:

• properly structured headings;
• paragraphs and lists that are correctly tagged;
• a logical reading order;
• meaningful alternative text for images;
• accessible tables;
• descriptive links;
• an identified document language;
• an appropriate document title;
• accessible form fields;
• keyboard-friendly navigation; and
• searchable text rather than images of text.

W3C provides specific PDF accessibility techniques covering areas including alternative text, bookmarks, reading order, tables, OCR, headings, forms, links, lists and document language.

This means that simply opening a PDF and visually inspecting it is not enough to determine whether it is accessible.

Can You Check PDF Accessibility in Adobe Acrobat Pro?

Yes. Adobe Acrobat Pro includes accessibility checking and remediation tools.

In current versions of Acrobat Pro, you can open All tools > Prepare for accessibility > Check for accessibility and run an accessibility check on the document.

Acrobat then reports its findings under categories such as document structure, page content, forms, alternative text, tables, lists and headings.

Results may be reported as:

• Passed;
• Failed;
• Skipped; or
• Needs Manual Check.

That last result is particularly important.

Adobe explicitly recognises that some accessibility requirements cannot be reliably evaluated automatically and therefore need human review.

An accessibility checker is an extremely useful tool, but it should be viewed as part of the testing process rather than definitive proof that a document is accessible.

Does Passing the Adobe Accessibility Checker Mean a PDF Is Accessible?

Not necessarily.

Automated testing tools are very good at identifying certain types of technical problems.

For example, software can determine whether:

• the document contains tags;
• a document language has been specified;
• a title is present;
• images are missing alternative text;
• content appears to be untagged;
• certain table structures are missing; or
• a scanned document contains no recognised text.

What software cannot always determine is whether those things have been implemented correctly.

For example, a checker may be able to confirm that an image has alternative text. It cannot necessarily decide whether that alternative text accurately communicates the meaning of the image.

A heading may technically be tagged as a heading while still being assigned the wrong heading level.

A table may contain table tags but have incorrect relationships between its headers and data cells.

A document may contain a tag structure while presenting its content in an illogical reading sequence.

That is why accessibility testing needs human judgement as well as automated validation.

Check Whether the PDF Is Tagged

One of the first technical checks is whether the document contains accessibility tags.

PDF tags create an underlying structural representation of the document. They can identify elements such as headings, paragraphs, lists, tables, figures and links so that assistive technologies can understand how the content is organised.

However, the presence of tags does not automatically mean that the PDF is accessible.

Tags can be:

• incorrectly applied;
• in the wrong order;
• improperly nested;
• duplicated;
• missing from some content; or
• used to identify the wrong type of content.

Adobe Acrobat can automatically add tags to an untagged PDF, including through its newer cloud-based auto-tagging functionality, but the resulting structure still needs to be reviewed where accessibility matters. Adobe also provides separate tools for inspecting and repairing reading order and more complex tagging issues.

We discuss this in more detail in our article How to Tag a PDF for Accessibility—and Why Tagging Alone Is Not Enough.

Check the Reading Order

Reading order is one of the areas where an apparently normal PDF can become confusing for someone using assistive technology.

Imagine a page containing two columns, a sidebar, an image caption and a footer.

A sighted reader can usually determine the intended sequence from the visual layout.

A screen reader depends heavily on the underlying document structure.

If that structure is incorrect, it might read:

• part of the first column;
• the footer;
• the second column;
• the image caption;
• and then return to the remainder of the first column.

Every individual piece of content may technically be present, but the resulting information can be difficult or impossible to follow.

W3C specifically identifies correct tab and reading order as a PDF accessibility technique, while Adobe provides a Reading Order tool for manually checking and repairing the sequence of page content.

Check Images and Alternative Text

Images that communicate information generally need an appropriate text alternative.

This can apply to:

• photographs;
• charts;
• graphs;
• diagrams;
• maps;
• icons;
• infographics; and
• illustrations.

The important question is not simply:

“Does this image have alt text?”

It is:

“Does the text alternative communicate the information or purpose that a person needs from this image?”

For a decorative image, the correct approach may be to exclude it from the accessible content altogether by marking it as an artifact.

For a meaningful chart or diagram, a short description of its appearance may not be sufficient. The user may need access to the information, trend or conclusion communicated visually.

This is another area where automated testing can identify a possible problem but human judgement is required to assess the solution.

Check Tables Carefully

Tables can be particularly challenging in accessible PDFs.

A simple table may require clear identification of:

• the table itself;
• rows;
• column and row headers; and
• individual data cells.

More complicated tables may require additional work to ensure that someone navigating the table with assistive technology can understand which headings relate to each data value.

A table can therefore look completely normal while having an incorrect or incomplete underlying structure.

W3C includes specific PDF techniques for table markup, and Adobe notes that more advanced table repairs may require working directly with the tag structure rather than relying only on automated tools.

Annual reports, research documents, government publications and financial documents frequently contain tables, making this an important part of professional PDF accessibility testing.

Check Scanned PDFs

Scanned PDFs present a different accessibility problem.

If a document has been created by scanning printed pages, what looks like text on screen may actually be an image of text.

Without Optical Character Recognition (OCR), a screen reader cannot interpret that image as ordinary document text.

One simple test is to try selecting individual words within the document. If you cannot select the text normally, you may be dealing with an image-only PDF.

OCR can convert the visible text into machine-readable text, but OCR itself is not the end of the remediation process.

The recognised text needs to be checked for accuracy, and the document may still require headings, tags, reading order, lists, tables, alternative text and other accessibility features.

W3C notes that a scanned document consisting only of images of text is inherently inaccessible until actual text is made available.

Check Links and Forms

Interactive elements introduce another layer of accessibility requirements.

Links should be identifiable to assistive technology and should have meaningful link text.

Forms may require:

• accessible field names;
• instructions;
• appropriate labels;
• keyboard navigation;
• a logical tab order;
• identification of required fields; and
• understandable error messages.

A form that works perfectly with a mouse may be difficult to complete using only a keyboard or screen reader.

Testing therefore needs to look beyond the document’s static text and consider how someone actually interacts with it.

Don’t Forget Visual Accessibility

PDF accessibility is not limited to screen readers and tags.

Depending on the document and the accessibility requirements being applied, testing may also need to consider issues such as:

• colour contrast;
• information conveyed using colour alone;
• text size and readability;
• meaningful use of headings;
• instructions;
• visual complexity;
• text embedded within graphics; and
• whether content remains understandable when enlarged.

Some of these issues may be repairable within the PDF itself.

Others are better corrected in the original Word, PowerPoint, InDesign or other source document before creating a new PDF.

This is one reason why professional remediation may involve reviewing both the final PDF and its editable source file.

What About WCAG and PDF/UA?

Two terms commonly encountered when discussing accessible PDFs are WCAG and PDF/UA.

WCAG provides accessibility requirements for digital content and includes PDF-specific techniques showing ways that WCAG success criteria can be addressed in PDF documents. W3C notes that these techniques are informative examples rather than the WCAG requirements themselves.

PDF/UA, or Universal Accessibility, is an ISO standard specifically concerned with accessible PDF technology.

The two approaches overlap in many areas but are not simply interchangeable.

Which standards and level of testing are appropriate can depend on the organisation, document, contractual requirements and intended use.

For organisations publishing important public-facing material, it is worth establishing the required accessibility standard before remediation work begins.

Can Online PDF Accessibility Checkers Tell You Everything?

No.

Automated accessibility checkers are valuable because they can inspect large numbers of technical properties quickly and consistently.

They are particularly useful for identifying obvious failures and highlighting areas that require investigation.

But accessibility contains many questions that require context:

• Is this the correct heading?
• Does this alt text convey the meaning of the image?
• Does this reading order make sense?
• Is this table understandable?
• Does this link description explain where it goes?
• Has decorative content been correctly excluded?
• Can a person understand the document when using assistive technology?

Software cannot reliably answer all of these questions.

A PDF should therefore not be declared accessible solely because an automated checker reports no failures.

When Should You Use Professional Document Remediation Services?

If testing reveals accessibility problems, the next step is remediation.

For a very simple document, someone with appropriate accessibility knowledge and PDF software may be able to correct the problems internally.

Professional document remediation services become particularly useful when you are dealing with:

• large or complex documents;
• reports containing many tables;
• forms;
• charts and diagrams;
• scanned documents;
• multi-column layouts;
• documents created from InDesign or other designed source material;
• recurring publications;
• large document libraries;
• public-sector or compliance-sensitive content; or
• documents that need to be remediated within a defined timeframe.

Effective document remediation is not simply a matter of running an automated repair tool.

It can involve examining the source file, repairing the PDF’s technical structure, addressing visual accessibility issues and manually reviewing the finished document.

What Do Professional Document Remediation Services Include?

The exact work required depends heavily on the document.

Professional document remediation services may include:

• reviewing the existing PDF;
• evaluating the editable source file;
• applying or repairing PDF tags;
• correcting heading structures;
• repairing reading order;
• remediating tables and lists;
• adding or reviewing alternative text;
• correcting links;
• remediating form fields;
• applying OCR to scanned content;
• setting document properties and language;
• identifying decorative content;
• correcting accessibility problems in the source document; and
• completing automated and manual testing.

A ten-page document containing complex tables, forms and graphics may require considerably more remediation than a much longer document consisting mainly of straightforward text.

For this reason, document remediation is usually scoped according to the structure and complexity of the files rather than page count alone.

How Atomic Web Strategy Can Help

Atomic Web Strategy provides document remediation services for organisations that need to improve the accessibility of their PDF and digital documents.

We can assist with individual documents or larger collections of PDFs, including reports, forms, publications and other public-facing material.

Our first step is generally to review a representative document and, where available, its editable source file.

This allows us to understand:

• how the document was created;
• the accessibility problems present;
• whether remediation should occur within the source file, PDF or both;
• the complexity of the technical remediation;
• the testing requirements; and
• the most efficient way to approach the work.

From there, we can establish an appropriate remediation scope rather than simply applying automated fixes and assuming the document is accessible.

Need to Know Whether Your PDFs Are Accessible?

If your organisation publishes PDFs online and you are unsure whether they are accessible, the fact that they look correct or pass a basic automated test may not tell you the whole story.

Tags, reading order, headings, images, tables, forms, links, scanned text and visual design can all affect the accessibility of a document.

Atomic Web Strategy can review your documents, identify accessibility barriers and provide professional document remediation services where remediation is required.

Send us a representative PDF and, if available, the editable source document. We can assess what is involved and provide a clear scope for the remediation work.

PDF tags are an essential part of document accessibility. They provide the underlying structure that helps screen readers and other assistive technologies understand how a document is organised.

However, adding tags does not automatically make a PDF accessible.

A document can be tagged and still contain an incorrect reading order, poorly structured tables, missing alternative text, inaccessible form fields and other barriers that make the content difficult to understand or navigate.

In this article, we explain how to tag a PDF for accessibility, what those tags actually do and why professional PDF remediation may involve considerably more than selecting an automatic tagging option.

What Are Accessibility Tags in a PDF?

PDF tags are hidden structural labels attached to the content within a document.

Visually, a PDF might contain a title, headings, paragraphs, lists, tables, links and images. Without appropriate tags, assistive technology may not be able to identify the purpose of these elements or understand how they relate to one another.

A properly structured tag tree might identify document elements such as:

• headings;
• paragraphs;
• lists and list items;
• tables, rows and cells;
• figures and images;
• links;
• form fields;
• quotations;
• captions; and
• decorative content.

Tags also help establish the order in which the document content should be presented to someone using a screen reader.

Adobe explains that document structure tags define the reading order and identify elements such as headings, paragraphs, sections and tables.

Tags are therefore fundamental to PDF accessibility—but they are only the underlying framework.

How to Tag a PDF for Accessibility in Adobe Acrobat Pro

Adobe Acrobat Pro includes tools that can automatically generate an initial tag structure for an untagged PDF.

The precise interface may vary between Acrobat versions, but Adobe’s current process is:

1. Open the PDF in Adobe Acrobat Pro.
2. Select All tools.
3. Open Prepare for accessibility.
4. Select Automatically tag PDF.
5. Allow Acrobat to analyse the document and create a tag tree.
6. Review any issues identified in the Add Tags Report.
7. Open the Accessibility Tags panel and manually inspect the resulting structure.

Adobe recommends creating the tags when exporting the PDF from an authoring program such as Microsoft Word or Adobe InDesign where possible. This allows the PDF to draw upon the heading styles, lists and other structural information contained within the original document.

Automatically tagging the finished PDF should generally be treated as the beginning of the remediation process rather than the final step.

What Happens When Acrobat Automatically Tags a PDF?

When the automatic tagging tool is run, Acrobat analyses the visible content and attempts to determine:

• which text is a heading;
• which content forms a paragraph;
• whether content is part of a list;
• whether an element is an image;
• how tables may be structured;
• where links appear;
• the intended reading order; and
• how the elements fit together in the tag tree.

This can provide a useful starting point for a relatively simple, well-organised document.

The problem is that Acrobat must make assumptions about the document’s meaning.

It may recognise that text is larger or bolder than surrounding content, but that does not necessarily mean the text is a heading. It may identify a group of lines as a table without correctly understanding the relationship between the row and column headings. It may also struggle with columns, text boxes, sidebars, complex layouts and graphical content.

Adobe specifically warns that automatic tagging cannot always correctly interpret complex page elements or their intended reading order. Closely spaced columns, irregular text alignment, borderless tables and form elements can produce incorrectly combined or out-of-sequence tags.

Every automatically generated tag tree should therefore be manually reviewed.

How to Review the PDF Tag Structure

After adding tags, open the Accessibility Tags panel in Acrobat Pro and examine the tag tree.

The tags should reflect both the visual structure and the meaning of the document.

For example:

• the document title should normally be identified as the primary heading;
• section headings should use an appropriate heading hierarchy;
• ordinary text should be contained within paragraph tags;
• bullet and numbered lists should use proper list structures;
• tables should include correctly associated header and data cells;
• meaningful images should be identified as figures;
• decorative items should generally be marked as artifacts; and
• links should be correctly included within the document structure.

It is not enough to check that tags exist. Each tag must identify the content correctly and appear in a logical location within the tag tree.

Empty, duplicated, incorrectly nested or unnecessary tags may also need to be removed.

Check the Reading Order

Reading order determines the sequence in which screen readers and other assistive technologies present the content.

The visual order of text on a page is not always the same as the underlying reading order.

This is particularly important in documents containing:

• multiple columns;
• sidebars;
• callout boxes;
• headers and footers;
• footnotes;
• images with captions;
• tables;
• forms; or
• complex page layouts.

A document may appear perfectly logical to a sighted reader while a screen reader presents sentences, headings or columns in the wrong sequence.

The reading order should be checked manually through the tag tree and, where appropriate, through Acrobat’s reading-order tools. W3C’s PDF accessibility techniques treat correct tab and reading order as a separate accessibility consideration rather than something solved simply by the presence of tags.

Add Appropriate Alternative Text

Meaningful images need text alternatives that communicate their purpose or the information they contain.

This may include:

• photographs;
• diagrams;
• charts;
• graphs;
• maps;
• icons; and
• instructional illustrations.

The alternative text should be based on the image’s purpose within the document, not merely a literal description of its appearance.

For example, “blue and red bar chart” does not communicate the findings shown by a chart. A useful text alternative may need to explain the comparison, trend or conclusion the reader is expected to understand.

Decorative images that do not communicate meaningful information should generally be marked as artifacts so they are not unnecessarily announced by screen readers.

An automated checker may be able to detect that an image has alternative text, but it cannot conclusively determine whether that text accurately communicates the image’s meaning.

Repair Tables, Lists and Other Complex Structures

Tables are one of the most common sources of PDF accessibility problems.

An accessible table may require:

• a correctly identified table structure;
• table row tags;
• table header and data cell tags;
• appropriate association between headers and cells;
• a logical reading sequence; and
• additional information for particularly complex tables.

Adobe recommends checking tables manually because their structure can be difficult for automated tools to interpret correctly.

Lists also require more than applying a single generic tag. The list itself, each individual list item, its label and its content may need to be represented correctly within the tag tree.

Similar care may be required for quotations, footnotes, captions, formulas and other specialised content.

Check Links and Bookmarks

Links should be keyboard accessible and contain meaningful link text.

Generic wording such as “click here” or a complete web address may be difficult to interpret when announced outside the surrounding sentence. Where appropriate, the accessible name of the link should explain its destination or purpose.

Longer documents may also require bookmarks to help users navigate directly between major sections.

Bookmarks do not replace a correct heading structure, but they can provide an additional method of navigation.

Remediate Accessible PDF Forms

PDF forms require specific accessibility work beyond ordinary document tagging.

Form fields may need:

• meaningful accessible names;
• instructions;
• tooltips or descriptions;
• keyboard operation;
• a logical tab sequence;
• clear required-field information;
• accessible error identification; and
• correct inclusion within the document structure.

A form may look straightforward visually but become unusable when its fields are announced in an unclear order or without meaningful labels.

Automatic tagging alone is unlikely to address every aspect of an interactive PDF form.

Set the Document Properties

Accessible PDF remediation can also include checking the document’s underlying properties.

These may include:

• the document title;
• the primary document language;
• the language of individual passages where required;
• bookmarks;
• page numbering;
• security settings;
• link behaviour; and
• whether all meaningful content is either tagged or correctly marked as decorative.

Setting the language helps compatible screen readers use the appropriate pronunciation rules. The title also helps users identify the document when it is opened or viewed alongside other files.

These requirements can easily be overlooked when someone focuses only on the visible content and the presence of a tag tree.

Run an Accessibility Checker

Once the document has been remediated, it should be reviewed with appropriate PDF accessibility testing software.

Adobe Acrobat includes an accessibility checker that can identify many technical issues. Other specialist tools can validate documents against standards such as PDF/UA.

However, automated testing has limitations.

Software can often identify whether:

• a document has tags;
• a language has been set;
• an image is missing alternative text;
• a table contains expected structural tags;
• a document title is present; or
• content has not been included in the tag tree.

It cannot reliably decide whether:

• the heading hierarchy makes sense;
• the reading order communicates the content correctly;
• alternative text describes an image appropriately;
• a complex table is understandable;
• link wording is meaningful;
• an instruction is clear; or
• information has been communicated effectively to people with different disabilities.

Testing therefore needs to combine automated validation with informed manual review. Even PDF/UA conformance does not, by itself, address every possible accessibility issue within a document’s content or visual design.

Why Tagging Alone Does Not Make a PDF Accessible

PDF tagging addresses the document’s technical structure. Accessibility can also be affected by the original content and visual design.

A tagged PDF may still contain:

• insufficient colour contrast;
• information communicated using colour alone;
• small or difficult-to-read text;
• text placed over complicated images;
• text embedded inside graphics;
• inaccessible charts and diagrams;
• unclear instructions;
• poor link wording;
• unnecessarily complex language;
• scanned pages without reliable text recognition; or
• layouts that are difficult to navigate or magnify.

Some of these problems can be corrected directly within the PDF. Others may require access to the original Microsoft Word, PowerPoint, Adobe InDesign or other editable source file.

This is why effective PDF accessibility remediation may include both technical PDF work and changes to the original document design.

Can You Make a PDF Accessible Yourself?

It is possible to improve a simple PDF yourself when you have:

• Adobe Acrobat Pro or suitable remediation software;
• access to the original source document;
• an understanding of document structure;
• knowledge of applicable accessibility requirements; and
• enough time to inspect and test the document carefully.

A short, text-based document with a straightforward layout may be relatively manageable.

Professional assistance should be considered when the document contains:

• complex or borderless tables;
• forms;
• charts and diagrams;
• multiple columns;
• unusual page layouts;
• scanned content;
• large numbers of images;
• technical or scientific information;
• significant visual design barriers;
• a large number of pages; or
• a firm publication or compliance deadline.

Organisations may also require specialist assistance when they have an entire library of existing PDFs rather than a single document.

What Does Professional PDF Document Remediation Include?

Professional PDF document remediation involves reviewing the document as a whole rather than applying one automated correction.

Depending on the file, remediation may include:

• creating or repairing the tag structure;
• correcting headings and heading hierarchy;
• structuring paragraphs and lists;
• repairing the logical reading order;
• remediating tables;
• writing or reviewing alternative text;
• identifying decorative content;
• improving links and bookmarks;
• setting the document title and language;
• labelling form fields;
• correcting keyboard and tab order;
• repairing scanned or image-only content;
• removing incorrect or empty tags;
• addressing design barriers within the source document; and
• completing automated and manual accessibility testing.

This process requires both technical knowledge and human judgement.

PDF Remediation Services from Atomic Web Strategy

Atomic Web Strategy provides PDF remediation services for businesses, government organisations, councils, universities, not-for-profit organisations, disability service providers and other organisations that need accessible digital documents.

We can assist with individual PDFs, complex reports, forms, recurring publications and larger document collections.

Our process can include:

• reviewing a representative document;
• identifying technical and design accessibility barriers;
• determining whether the editable source file is required;
• defining a clear remediation scope;
• coordinating technical and design remediation;
• testing the completed documents; and
• identifying any limitations that cannot be corrected within the available files or agreed scope.

Where required, completed documents can be tested against the accessibility standard agreed for the project, with a validation certificate or report supplied.

Need Help Making Your PDFs Accessible?

Automatically adding tags may improve an untagged PDF, but it should not be treated as proof that the document is accessible.

The tag structure, reading order, tables, images, links, forms, document properties and visual design may all require additional review.

Atomic Web Strategy’s document remediation services can help you identify and correct these barriers without placing the technical workload on your internal team.

Send us a representative PDF, the editable source document where available, the approximate page count and your required completion date. We can review the files and provide a clear scope and quotation.

How Much Does Local SEO Cost?

In today’s digital age, having a strong online presence is essential for businesses looking to thrive in their local communities. Local SEO (Search Engine Optimisation) plays a crucial role in ensuring that your business is visible to potential customers in your area when they search for products or services online. However, one common question that many business owners have is: How much does local SEO cost?

Factors Influencing Local SEO Cost

The cost of local SEO services can vary depending on several factors. One of the primary factors is the size and type of business. Larger businesses with multiple locations or a wider target audience may require more extensive SEO strategies, which can affect the overall cost. Additionally, the level of competition in the local market can impact pricing, as businesses in highly competitive industries may need to invest more in order to outrank their competitors in search engine results.

Another factor to consider is the scope of services provided by the SEO agency. Some agencies offer comprehensive SEO packages that include a range of services such as keyword research, on-page optimisation, link building, and content creation, while others may offer more limited services at a lower price point. Additionally, businesses may opt for customisations or additional features, such as local listings management or review monitoring, which can also affect the cost of local SEO.

Pricing Models in Local SEO

When it comes to pricing, local SEO agencies typically offer different pricing models to accommodate the needs and budgets of their clients. One common pricing model is the monthly retainer, where businesses pay a fixed monthly fee in exchange for ongoing SEO services. This model provides businesses with consistent support and allows for ongoing optimisation efforts to improve their online visibility over time.

Alternatively, some SEO agencies may charge one-time fees for specific services, such as website audits or keyword research. This option can be more cost-effective for businesses with limited budgets or those looking to address specific SEO needs without committing to a long-term contract.

In some cases, SEO agencies may also offer performance-based pricing, where the cost of services is tied to the results achieved. This could involve paying based on the number of leads or conversions generated through organic search traffic. While this pricing model can offer businesses greater flexibility, it may also come with higher upfront costs or fees based on performance metrics.

Understanding the Value of Local SEO Investment

While the cost of local SEO services may vary, it’s important for businesses to understand the value of investing in their online presence. Local SEO can offer significant benefits, including increased visibility in local search results, higher website traffic, and more qualified leads. By optimising their online presence, businesses can position themselves as industry leaders and attract customers who are actively searching for their products or services.

Additionally, investing in local SEO can provide long-term benefits for businesses, as improved search engine rankings can lead to sustained organic traffic and a higher return on investment over time. Case studies or examples of successful local SEO campaigns can help illustrate the potential impact of these strategies and demonstrate the value of investing in professional SEO services.

Conclusion

In conclusion, the cost of local SEO services can vary depending on a variety of factors, including the size of the business, the level of competition in the local market, and the scope of services provided by the SEO agency. However, investing in local SEO is essential for businesses looking to succeed in today’s digital landscape. By understanding the factors influencing local SEO cost and the value of investing in professional services, businesses can make informed decisions to improve their online visibility and attract more customers in their local communities.