🎓 Text Doc Digital Accessibility Converter

📋 Applying Heading Styles in Word

Heading styles (Heading 1, Heading 2, Heading 3, Title) are different from heading formatting (bold, larger font). A paragraph that looks like a heading because it is bold and large is invisible to screen readers — it is just bold text. Only a paragraph with a proper heading style applied creates a navigable outline.

How to apply a heading style:

1. Click anywhere in the paragraph you want to make a heading.
2. In the Home ribbon, find the Styles gallery (a row of style thumbnails). Click Heading 1, Heading 2, or Heading 3 as appropriate.
3. If you don't see the Styles gallery, click the small arrow at the bottom-right of the Styles group to open the Styles pane.
4. For the document title, use the Title style (also in the Styles gallery).

Tip: You can still apply bold, italic, or a different font size on top of a heading style without losing its accessibility. The style is what matters to screen readers, not the visual appearance.

Hierarchy: Use Heading 1 for top-level sections, Heading 2 for sub-sections within those, and Heading 3 for sub-sub-sections. Do not skip levels (e.g., do not jump from Heading 1 directly to Heading 3).

🗂️ Why Heading Structure Matters — and How to Navigate It

Heading styles do more than make text look like a heading. They create an invisible structural outline of your document that both sighted users and screen reader users depend on to find their way around. Think of it as a built-in, always-current table of contents embedded in the document's structure.

For screen reader users: Screen readers can present a list of all headings in a document, letting users jump directly to any section without reading through everything in between. This is often the primary way blind or low-vision users navigate long documents — the same way a sighted reader skims headers to find the section they want. Without proper heading styles, that navigation simply does not exist: the document becomes a single undifferentiated block of text.

For all users — the Navigation Pane: Word's Navigation Pane is one of its most powerful and least-known features. It displays your document's heading structure as a clickable outline on the left side of the screen, letting you jump to any section instantly and see the shape of your document at a glance. For anyone writing long documents — lecture notes, reports, course materials — it is genuinely transformative.

How to open the Navigation Pane:

1. Go to the View tab in the ribbon.
2. Check the Navigation Pane checkbox in the Show group.
3. The pane appears on the left. Click the Headings tab at the top of the pane (the other tabs are Pages and Results).
4. You will see your document's heading structure as a collapsible outline. Click any heading to jump directly to that section.

If your Navigation Pane shows nothing under Headings, it means your document has no paragraphs with real heading styles applied — which is exactly what this converter helps you fix.

How to use the outline effectively:

• You can drag headings in the Navigation Pane to reorder entire sections of your document — the heading and all its content move together.
• You can right-click a heading in the pane to promote or demote its level, delete the section, or add a new heading before or after it.
• The outline gives you an immediate visual check on your document's structure — if it looks wrong in the Navigation Pane, it will feel wrong to a reader navigating with a screen reader too.

The accessibility connection: A well-structured heading outline is the single most impactful accessibility improvement you can make to a long document. It benefits screen reader users, users of other assistive technologies, users who rely on keyboard navigation, and — as the Navigation Pane demonstrates — every other reader as well. Accessibility and good document structure are the same thing.

Carrying heading structure into PDF: When you export a Word document to PDF, you can embed the heading structure directly into the PDF so it remains navigable for screen reader users — not just in Word. In Word: File → Export → Create PDF/XPS, then click Options… and check "Document structure tags for accessibility" before clicking Publish. The resulting PDF will have a proper heading outline, bookmarks panel, and reading order that assistive technologies can use — but only if the headings were properly styled in the Word document first.

🎨 Modifying Heading Styles Globally in Word

When you apply a heading style, Word uses its built-in appearance — often a blue, serif font that may not match your document's design. You do not need to reformat every heading individually. Instead, redefine the style itself once, and every paragraph using that style updates automatically throughout the entire document.

How to modify a heading style globally:

1. Apply the heading style to one paragraph (e.g., Heading 1) as described above.
2. Manually format that one paragraph the way you want all Heading 1s to look — font, size, color, bold, spacing, etc.
3. Right-click Heading 1 in the Styles gallery on the Home ribbon.
4. Select "Update Heading 1 to Match Selection".
5. All paragraphs styled as Heading 1 throughout the document instantly update to match your new formatting.

Alternative — edit the style directly:

1. Right-click Heading 1 in the Styles gallery → Modify…
2. Set font, size, color, and spacing in the dialog. Click Format at the bottom for additional options (paragraph spacing, borders, etc.).
3. Make sure "New documents based on this template" is selected if you want your changes to carry over to future documents. Click OK.

Tip: Repeat this for Heading 2 and Heading 3 to create a consistent, custom heading hierarchy that is both visually on-brand and fully accessible. The accessibility is carried by the style name, not the visual appearance — so you can make headings look however you like without sacrificing screen-reader compatibility.

🖼️ Adding Alt Text to Images in Word

Alt text (alternative text) is a written description of an image that screen readers read aloud to users who cannot see the image. Without it, screen reader users hear either nothing or the raw file name (e.g., "image001.png"), which is useless.

How to add alt text:

1. Right-click the image.
2. Select Edit Alt Text… (or Format Picture → Alt Text on older versions of Word).
3. Type a description in the text box. Click outside when done.

What makes good alt text:

• Describe what the image shows and why it matters in context — not just what type of image it is.
• Do not start with "Image of…" or "Photo of…" — screen readers already announce it as an image.
• Keep it concise: one or two sentences is usually enough.
• For graphs and charts, describe the key finding or trend, not every data point.
• For purely decorative images (dividers, backgrounds), check the Mark as decorative checkbox instead of writing alt text.

Example: Instead of "Graph", write "Bar graph showing bacterial colony counts declining by 80% over 24 hours following phage treatment."

Using an AI to generate alt text: AI assistants (ChatGPT, Claude, Gemini, etc.) can help write alt text descriptions. Paste the image into the AI chat along with this prompt:

"Please write a concise alt text description for this image suitable for use with a screen reader. Describe what the image shows and why it matters in an academic or educational context. Keep it to 1-2 sentences. Do not start with 'Image of' or 'Photo of'. Focus on content and significance."

The Review & Fix tab includes Copy AI prompt and Copy image buttons next to each image to make this workflow easier.

Color accessibility: Alt text addresses screen reader accessibility, but images also need to be accessible to colorblind readers. If your figures use color to convey information, check them at colors.phage.org — a free tool that simulates how images appear under different types of color vision deficiency. The Review & Fix tab includes a Download image button so you can save a figure, adjust its colors in the Colors tool, and use Replace image to swap the revised version back into the document.

📊 Tables and Digital Accessibility — A Practical Guide

Tables are one of the most challenging accessibility problems in Word documents, especially those converted from PDF. This guide covers what the issues are, what works, what doesn't, and what you can do instead.

Why table accessibility matters: Screen readers navigate tables by reading column and row headers aloud as the user moves between cells. Without designated headers, every cell sounds the same — the user has no way to know which column or row they are in. A table without headers is effectively unnavigable for screen reader users.

The standard fix — and why it may not work

The standard approach is:

1. Click anywhere in the first row of your table.
2. Go to the Table Design tab → check Header Row.
3. Right-click the first row → Table Properties → Row tab → check "Repeat as header row at the top of each page". Click OK.

Known Word limitation: In Word 365 and some recent versions, it is not possible to designate only the first row as a header row — the option either does not apply correctly, or marks all rows as headers. This appears to be a bug in Word. Additionally, right-clicking to access Table Properties may not be available in all versions. If this is the case, do not spend time trying to force Word to comply — use one of the alternative approaches below.

Tables converted from PDF — a different problem

When a PDF is converted to DOCX, tables rarely survive as real Word tables. They typically become either plain text with manual spacing, or a grid of text boxes. In these cases, "Convert Text to Table" in Word usually does not work because the text structure does not match what Word expects. Do not waste time trying to reconstruct the table structure manually.

Alternative approach 1 — Convert the table to text

If the table content can be understood as a list or sequence of text, converting it to plain text is often the cleanest accessible solution:

1. In Word: select the table → go to Table Design or Layout tab → click Convert to Text.
2. Choose a separator (tabs work well for columnar data; paragraph marks work for simple lists).
3. The result is plain text that screen readers handle perfectly.

This converter's Review & Fix tab shows a tab-separated text preview of each detected table, with a copy button. You can paste this directly back into your Word document as a text alternative to the table.

Alternative approach 2 — Convert the table to an image

If the table's visual layout is important (complex headers, merged cells, colour coding), converting it to an image with a thorough alt text description is a valid approach:

1. In Adobe Acrobat: use Edit PDF → Snapshot tool to capture the table as an image.
2. In Word: take a screenshot of the table, or use Insert → Screenshot.
3. Insert the image into your document and write a comprehensive alt text description covering the table's content and key findings.

Note: This approach turns a structural accessibility problem into an alt text problem — which is solvable. A well-written alt text description of a table can fully convey its content to a screen reader user.

Alternative approach 3 — Distribute DOCX instead of PDF

Untagged PDFs (those converted without accessibility structure) cannot be made fully accessible after the fact. If your document is primarily text with tables, distributing the DOCX file directly — rather than exporting to PDF — sidesteps the problem entirely. DOCX files are natively accessible to Word's own accessibility tools and screen readers.

If you must distribute a PDF, export it from Word using File → Export → Create PDF/XPS → Options → Document structure tags for accessibility. This embeds heading and structure tags into the PDF, making it navigable. However, table header accessibility in the resulting PDF still depends on whether Word correctly marked the headers beforehand.

Tables that span multiple pages

For tables that span multiple pages, the header row needs to repeat at the top of each page. If Word's "Repeat as header row" option is working in your version, use it. If not, the table-to-text or table-to-image approaches above are the most reliable alternatives.

Summary — what actually works

• ✅ Convert table to text — works reliably, fully accessible, supported by this converter's preview tool
• ✅ Convert table to image + alt text — works reliably, requires a good description
• ✅ Distribute DOCX instead of PDF — avoids the problem entirely
• ⚠ Word's Header Row checkbox — works in some Word versions, unreliable in Word 365
• ❌ Reconstructing PDF tables in Word — generally not worth attempting

📋 Creating Proper Lists in Word

Typing a bullet character (•) or a number (1.) manually and pressing Tab creates text that looks like a list but is not recognized as one by screen readers. Use Word's built-in list formatting instead.

How to create a proper list:

1. Place your cursor where you want the list to begin.
2. In the Home ribbon, click the Bullets button (●≡) for a bulleted list, or the Numbering button (1≡) for a numbered list.
3. Type your list items, pressing Enter between each one.
4. Press Enter twice (or click the button again) to end the list.

To convert existing manual list items: Select the paragraphs, then click the Bullets or Numbering button. Word will apply proper list style and you can delete the manual characters.

✅ Checking Accessibility in Word

Word has a built-in accessibility checker that complements this converter. It can catch issues this tool may miss, and will confirm that the fixes applied here have taken effect in the final document.

How to run the accessibility checker:

1. Go to the Review tab in the ribbon.
2. Click Check Accessibility.
3. The Accessibility pane opens on the right, listing errors, warnings, and tips.
4. Click any item in the list to jump to the relevant element in the document and see suggested fixes.

Common findings and what they mean:

• "Missing Alt Text" — an image has no description. Right-click → Edit Alt Text.
• "Table has no header" — mark the first row as a header row (see above).
• "Document has no title" — apply the Title style to your document title, or set the document title in File → Properties.
• "Hard-to-read text contrast" — text color is too close to the background color for low-vision readers.

Running Word's checker after downloading your corrected file from this converter is a good final step before distributing it.

📝 Using Google Docs Instead of Word

If you author documents in Google Docs rather than Word, most of the same accessibility principles apply. Google Docs supports heading styles, alt text on images, and document outline navigation — and documents can be exported to .docx for use with this converter.

Applying heading styles in Google Docs:

1. Click anywhere in the paragraph you want to make a heading.
2. Open the Format menu → Paragraph styles → choose Title, Heading 1, Heading 2, or Heading 3.
3. Alternatively, use the style dropdown in the toolbar (it usually shows "Normal text") and select the heading level from there.

Modifying heading styles globally in Google Docs:

1. Format one paragraph the way you want all headings of that level to look.
2. Go to Format → Paragraph styles → Heading 1 (or whichever level) → "Update 'Heading 1' to match".
3. All paragraphs of that heading level update throughout the document.

The Document Outline — Google Docs' Navigation Pane equivalent:

1. Go to View → Show document outline (or press Ctrl+Alt+A / ⌘+Alt+A).
2. The outline panel appears on the left, showing all headings as clickable links.
3. Click any heading to jump to that section instantly.

As with Word, if the outline is empty, it means no real heading styles have been applied.

Adding alt text to images in Google Docs:

1. Right-click the image → Alt text.
2. Fill in the Description field. (The Title field is optional.)
3. Click OK.

Table headers in Google Docs:

This is where Google Docs falls short of Word. As of 2025, Google Docs does not provide a built-in way to mark a table row as a header row in the accessibility sense that screen readers recognize. The visual appearance of a header row can be achieved with formatting (bold, background color), but this does not create accessible header markup. If accessible tables are important for your document, consider completing the table in Word or using this converter's output as a starting point and finishing in Word.

Exporting to .docx for use with this converter:

1. In Google Docs: File → Download → Microsoft Word (.docx).
2. Upload the downloaded .docx to this converter.
3. Note that heading styles you applied in Google Docs will be preserved in the exported .docx, so the converter will recognize them as real headings — a good reason to apply styles in Google Docs before exporting.

Checking accessibility in Google Docs: Google Docs does not have a dedicated accessibility checker equivalent to Word's. The best approach is to export to .docx, run it through this converter, and then use Word's built-in accessibility checker on the result.

🔗 Hyperlinks and Plain-text URLs

There are three categories of link issues this tool detects:

• Non-descriptive hyperlinks in body text — clickable links whose display text is a bare URL or generic phrase like "click here". These need descriptive replacement text that makes sense out of context: "2023 phage therapy review in Lancet", not a bare URL.
• In-text citation links — hyperlinks with display text like [1] or [2], linking internally to the reference list. These are not an accessibility problem — they are a well-understood academic convention. The tool shows them collapsed for information only.
• Reference-section links — URLs embedded in citations after the References heading. DOI and PubMed URLs are flagged as probably-deletable; URLs with "accessed/retrieved" language nearby are flagged as probably-essential (the URL is the reference itself). The section is collapsed by default since reference links are often acceptable as-is.

Plain-text URLs appear as unclickable text — often because PDF conversion strips hyperlink formatting. The converter detects these and offers "Make live" to convert them to clickable hyperlinks with optional descriptive display text.

Tip: In Word, select any plain-text URL and press Ctrl+K (Cmd+K on Mac) to make it a live hyperlink manually.

🔄 Using This Tool Iteratively

This tool works best across multiple passes rather than a single session:

1. First pass — upload the original document, review the Critique, accept the clear fixes (language, obvious headings, lists). Skip anything uncertain.
2. Download and re-upload — the corrected DOCX becomes the input for the next pass. Issues marked Skip will reappear; issues marked Ignore will not.
3. Subsequent passes — address remaining issues with more context. Headings you previously rejected are tagged with a NotAHeading style and will not be re-flagged.
4. Final verification — run the finished document through Word's built-in checker (Review → Check Accessibility) and/or your institution's designated accessibility checker to confirm.

Remember: there is a difference between digitally accessible, aesthetically acceptable, and perfect. Achieving two out of three is sufficient for most applications — do not let the perfect be the enemy of the accessible!

About this tool

The Text Doc Digital Accessibility Converter is a browser-based tool for instructors that converts Word documents (.docx) into digitally accessible output. It runs entirely in your browser — no files are uploaded to any server.

Primary use case

Many documents exist only as PDFs with no accessibility structure. Converting a PDF to .docx (via Adobe Acrobat, Smallpdf, ILovePDF, or similar) and running it through this converter is often the only practical path to producing an accessible version of an existing document. This tool is designed to make that workflow as fast as possible.

What this tool checks and fixes

• Document language — sets lang="en-US" in the document XML (automatic)
• Heading structure — detects manually-formatted headings using font size, bold/caps/italic formatting, and text length as signals; proposes Title/H1/H2/H3 styles for review. Boundary paragraphs (References, Acknowledgements, etc.) are also proposed as headings. Already correctly-styled headings are shown in a "Show all" view.
• List formatting — detects manual bullet/number characters and converts to proper Word list styles (automatic, opt-out per item). Reference-section paragraphs are excluded.
• Hyperlinks — three categories:
  • Main text external — bare URLs or generic text; needs descriptive replacement
  • Main text internal — citation numbers [1][2] linking to the reference list; not an accessibility problem, shown collapsed for information only
  • Reference section — links after the References/back-matter heading; collapsed by default, sub-classified as probably-essential (has "accessed/retrieved" language), probably-deletable (DOI/PubMed), or review
• Plain-text URLs — detects URLs that appear as plain text rather than live hyperlinks; offers "Make live" to convert them to clickable links with optional descriptive text
• Images — detects images without alt text; shows thumbnails with AI-prompt and copy-image buttons; separate Description and Title fields; strip per image or strip all
• Tables — detects tables, warns about missing header rows and all-rows-as-headers; shows tab-separated text preview per table; checkbox to auto-insert text rendering after the table in the output DOCX (using a TableTextRendering style)

Limitations

• Heading detection is heuristic — imperfect, especially in PDF-converted documents. Always review before accepting. Rejected headings are marked with a NotAHeading style so they are not re-flagged on subsequent passes.
• Alt text is not generated automatically — write descriptions yourself; use the AI prompt buttons to get help from an AI assistant.
• Table header markup has known Word 365 bugs — see the Help tab for workarounds including table-to-text and table-to-image approaches.
• Reference section detection — uses text-matching (style-agnostic) and sequential numbering patterns; may not detect all boundaries in unusual citation formats.
• Use iteratively — apply fixes, download, re-upload to verify. This tool does not substitute for your institution's official accessibility checker.

Why these things matter

Headings applied as bold text rather than Word heading styles, images without alt text, plain-text URLs, and tables without header row markup are among the most common reasons documents fail digital accessibility assessments. Screen readers depend on these structural cues to navigate and interpret documents. Remember: there is a difference between digitally accessible, aesthetically acceptable, and perfect — achieving two out of three is often sufficient!

Output formats

• Accessible DOCX — Word document with corrected styles, suitable for further editing or conversion to PDF (use File → Export → Create PDF/XPS → Options → Document structure tags for accessibility)
• Accessible HTML — clean readable HTML suitable for embedding in course pages or sharing as a standalone reading

Privacy

All processing happens in your browser using JavaScript. Your document is never sent to any server.

Citation

Abedon, S.T. Text Doc Digital Accessibility Converter. docaccess.biologyaspoetry.org. DOI: 10.5281/zenodo.20095643