Do screen readers read page numbers

What happens when a screen reader encounters a page number?

Screen readers are basically software that turns text into speech or braille. When they bump into a page number, how they handle it depends on how that number was coded in the document or webpage. Here's the thing - screen readers don't automatically read every number they see. They read what's in the text layer or the HTML structure. That's a key difference people miss.

Say you've got "Page 12" typed out in a PDF or on a site. The screen reader might say "Page twelve" or "Page one two." But if that page number lives in a header or footer that's not part of the main reading flow? It could get skipped entirely. In many PDFs, page numbers are placed in headers or footers that get tagged as "artifact" elements. Screen readers are trained to skip those artifacts so they don't keep repeating the same junk on every single page.

Do screen readers read page numbers in PDFs?

How PDF structure affects page number reading

For accessible PDFs, page numbers need proper tagging. The PDF/UA standard says page numbers should be marked as "Page Number" artifacts. When that's done right, a screen reader can spot the number and announce it, usually before reading the main content. But honestly? Most PDFs out there aren't properly tagged. In untagged ones, the screen reader might read the number as part of the text flow, or skip it entirely if it's stuck in a header or footer outside the logical reading order.

Adobe Acrobat and other tools let authors set page number labels. Screen readers like JAWS, NVDA, and VoiceOver can read those labels if they exist. JAWS, for instance, typically says "Page 1 of 10" when you're navigating a tagged PDF. But if the PDF is just a scanned image with no text recognition? No page numbers get read at all. Zero.

Do screen readers read page numbers on websites?

HTML and CSS considerations

On websites, page numbers show up mostly in pagination navigation - think "Page 1, Page 2, Page 3" for blog posts or search results. Screen readers will read these if they're coded as text within links. So a link that just says "2" gets read as "two" or "link two." But if that number is an image or some decorative element with no alt text? The screen reader ignores it completely.

Web developers can use ARIA attributes to make things better. For example, using aria-label="Page 2" on a link ensures the screen reader announces it correctly. Some sites use JavaScript to load content dynamically without changing the URL, and that can really mess things up for screen readers. They might not announce the new page number at all in those cases.

Can screen readers skip page numbers?

User settings and navigation modes

Yeah, absolutely. Screen readers can be set up to skip page numbers. Most have a "browse" or "read" mode where they read everything, and a "focus" or "forms" mode where they only read interactive stuff. Users can also use keyboard shortcuts to jump to headings, links, or landmarks. If a page number isn't in a heading or a link, it might get skipped during quick navigation.

Take NVDA for example - pressing "H" jumps to the next heading. If the page number isn't a heading, it won't be announced during heading navigation. Users who want to hear page numbers can use the "Say All" command (Insert + Down Arrow) to read everything from where they are. But honestly, that's not how most people use it day-to-day.

How to ensure page numbers are read by screen readers

If you really want screen readers to read page numbers, here's what works:

• In PDFs, use the "Add Tags" feature in Adobe Acrobat and make sure page numbers are tagged as "Page Number" artifacts.
• In HTML, put page numbers in the main content area, not in headers or footers that might be hidden from screen readers.
• Use actual text for page numbers, not images. If you absolutely must use images, add descriptive alt text.
• For pagination, use semantic HTML like <nav aria-label="Pagination"> and include visible text labels.
• Test with multiple screen readers - JAWS, NVDA, VoiceOver - to make sure page numbers are announced properly.

Common misconceptions about screen readers and page numbers

Lots of people think screen readers always read page numbers because they're visible on screen. That's just not true. Screen readers rely on the underlying code, not what you see visually. A page number at the bottom of a PDF page might be invisible to the screen reader if it's in a footer artifact. Same thing if it's part of a background image - won't get read.

Another myth is that screen readers automatically announce page numbers when you move between pages. That only happens if the document or website is properly coded. For example, an EPUB ebook needs page numbers embedded in the markup for screen readers to announce them. If they're not there, they're not getting read.

Data table: Screen reader behavior with page numbers

Checklist for accessible page numbers

• Are page numbers in the main reading order?
• Are page numbers text, not images?
• Are page numbers tagged correctly in PDFs?
• Is pagination navigation using semantic HTML?
• Have you tested with JAWS, NVDA, and VoiceOver?
• Are page numbers visible and announced?

Frequently asked questions