• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

benwbrum / fromthepage / 36489529837
75%

Build:
DEFAULT BRANCH: development
Ran 28 Sep 2026 10:04PM UTC
Jobs 4
Files 278
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

28 Sep 2026 09:58PM UTC coverage: 74.781% (+0.1%) from 74.653%
36489529837

push

github

web-flow
Make the accessible PDF export usable by screen readers and Acrobat's checker (#5861)

* Fix Acrobat accessibility checker failures in the accessible PDF export

The Grover/Chrome "accessible PDF" export (accessible_pdf.pdf) failed three
Adobe Acrobat accessibility checks:

- Bookmarks: large documents must have bookmarks. Chrome only emits a PDF
  outline when asked, so pass `outline: true` (with `tagged: true`) to the
  PDF generator. Bookmarks are built from the h1/h2/h3 heading structure the
  export already produces (work title, per-page titles, notes, etc.).

- Tagged content: every page carried one untagged text run - the CSS
  `@page { @bottom-center { content: counter(page) } }` page number. Chrome
  renders margin-box generated content without a structure-tree tag and
  without an Artifact marker, so Acrobat flags it. Remove the page-number
  footer from the export layout.

- Table regularity: transcribers can build TEI tables whose rows have
  different cell counts. Add Work::Export::TableRegularizer, which pads short
  rows with non-breaking-space cells so every row has the widest row's column
  count before the HTML is handed to Chrome. Rowspan tables are left alone.

Verified end to end against the Grover pipeline: resulting PDF has a document
outline, zero untagged text operators on every page, and regular table
structure elements.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MMBG8j4PEQR84hBdE32dSz

* Flatten links and line breaks in the accessible PDF for screen readers

Windows Narrator could not read transcription body text in the accessible
PDF: it announced only the hyperlink URLs and skipped everything else.

Chrome/Skia tags every inline break in the text flow as its own NonStruct
marked-content run. Transcription HTML is dense with inline elements - one
<span class="line-break"> per source line, one <a> per subject link - so each
paragraph shatters into 10-15+ fragment... (continued)

2899 of 4467 branches covered (64.9%)

Branch coverage included in aggregate %.

83 of 84 new or added lines in 3 files covered. (98.81%)

11462 of 14737 relevant lines covered (77.78%)

210.5 hits per line

Uncovered Changes

Lines Coverage ∆ File
1
54.88
0.0% app/helpers/export_helper.rb
Jobs
ID Job ID Ran Files Coverage
1 rspec-1 - 36489529837.1 28 Sep 2026 10:07PM UTC 278
47.76
GitHub Action Run
2 rspec-2 - 36489529837.2 28 Sep 2026 10:08PM UTC 278
43.63
GitHub Action Run
3 rspec-3 - 36489529837.3 28 Sep 2026 10:05PM UTC 278
41.06
GitHub Action Run
4 rspec-0 - 36489529837.4 28 Sep 2026 10:04PM UTC 278
39.36
GitHub Action Run
Source Files on build 36489529837
  • Tree
  • List 278
  • Changed 183
  • Source Changed 2
  • Coverage Changed 183
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #36489529837
  • 2992bbc8 on github
  • Prev Build on development (#36473308744)
  • Next Build on development (#36657252798)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc