PDF Accessibility Checker Report

Links and form fields need to be connected to the document structure so screen readers can announce them in context. Untagged annotations may be announced at random times or missed entirely.

Links need descriptive text so users know where they lead. Without descriptions, screen readers may only announce the URL, leaving users unable to determine if the link is relevant.

Links must be properly nested in the structure tree. Improper nesting causes the link's description to be hidden or announced incorrectly by screen readers.

Every piece of real content needs a tag so screen readers know it exists. Decorative elements (borders, backgrounds) should be marked as Artifacts so they're skipped, avoiding clutter in the audio output.

Low contrast text is hard to read for people with low vision or color blindness. Adequate contrast ensures text remains readable in various lighting conditions and for users with visual impairments.

If fonts aren't embedded, text may display as squares or wrong characters on devices that don't have those fonts. Screen readers may also fail to extract the text correctly.

Each character must have a Unicode value so screen readers can pronounce it. Without proper mapping, text might appear visually correct but be read as gibberish or skipped entirely by assistive technology.

Images need text descriptions so blind users understand their content. Without alt text, screen readers either skip the image entirely or announce 'image' with no context.

If a parent element has alt text, it overrides the figure's own description. This means users hear the wrong description or a generic one instead of the specific image description.

Tables must have proper row and cell structure. Malformed tables confuse screen readers, which may announce data in wrong order or fail to convey the tabular relationships.

Irregular tables with overlapping cells or gaps break screen reader navigation. Users may hear cells in wrong order or miss content entirely.

Rows must be properly placed in the table hierarchy. This enables screen readers to distinguish between header rows, body rows, and footer rows.

Headers must be inside rows for the table structure to be valid. Misplaced headers break screen reader navigation and make tables incomprehensible.

Scope tells screen readers whether a header applies to a row or column. Without it, users can't tell which header describes each data cell in complex tables.

Data cells must be inside rows for proper structure. Screen readers rely on this hierarchy to navigate tables cell by cell and row by row.

Data cells must be linked to their headers. When navigating a table, screen readers announce the relevant headers for each cell so users know what the data means.

Tables without headers are just grids of data with no context. Users cannot understand what each column or row represents without header cells.

A summary helps users understand complex tables before navigating them. Without it, users must explore the entire table to understand its organization.

Documents should start with H1 as the main title. Starting with H2 or H3 suggests missing content and breaks the document's logical hierarchy.

Jumping from H1 to H3 skips a level, confusing users who navigate by headings. Proper nesting (H1 → H2 → H3) creates a logical outline that users can follow.