Looks like the inlineTextBoxes in PDFs don't have wordStarts and wordEnds.

Fixed in https://chromium-review.googlesource.com/c/chromium/src/+/919543.

Reverting to Assigned to katie@ 

Google Chrome 67.0.3369.0 (Official Build) canary (64-bit)
Firmware Version Google_Samus.6300.276.0
Flag enabled: #enable-experimental-accessibility-features


# Enable STS in Accessibility Settings
# Launch text PDF such as this one: http://unec.edu.az/application/uploads/2014/12/pdf-sample.pdf
# Highlight text using mouse then press Search + s
Expected: STS reads text
Actual: earcon is played for nothing selected 

# Clear highlight on the PDF by clicking anywhere with the mouse
# Invoke STS by pressing search button and dragging highlight around text in the PDF
Expected: highlight appears around text and word highlighting lines up with word being read
Actual: Highlight ring is offset from actual selection, word highlighting is moving in this offset area and doesn't line up visually with any words.

Uh oh, it was working a few days ago! Laura, can you please bisect from here to see what went wrong?
https://chromium-review.googlesource.com/c/chromium/src/+/936454 / commit 4d87bccef0d6c07cdecf43449af4157736ac3f35

Moving from just having STS label to also having the UI>Accessibility>SelectToSpeak component to make searching easier in the future.