On paper, the two columns are easy to scan. Instructions run down the left; reminders occupy a shaded box on the right. Copy a line of text and it pastes neatly, so the project team marks the PDF accessible. A screen reader opens the same file and moves from the first step to the third reminder and then back into the middle of a telephone number. Every word was technically present. The order broke the notice.

Selectable text means the characters exist as text, or were recognized by software. It does not establish that headings, tables, lists and links have meaningful relationships, or that the sentences are exposed in the proper order. Materials supplied by a program and an employer’s own summary also have different jobs. Make the employer copy accessible without claiming that editing it changes the provider’s underlying terms.

Start with the source, then check the export

If you own the document, fix its source rather than relying on recurring cleanup. Use real paragraph and heading styles, a proper list for ordered steps, and a plain table only where relationships require rows and columns. Keep labels and their explanations together. Avoid putting essential operating instructions in an image of text. If a screenshot is necessary to demonstrate a control, describe which control matters in nearby prose; a generic “screenshot” marker does not convey the interaction. Hide decorative data from the reading sequence only if it genuinely adds nothing the reader needs.

Choose a tagged-PDF export and check the file itself. A source document and PDF do not necessarily expose the same order. Image-only pages may need reliable text recognition before attention to structure, followed by comparison against the originals for omissions and incorrect characters. W3C’s PDF3 technique explains why tags and tab order matter and provides ways to test them. Section508.gov’s PDF testing training describes checks for common document elements; using its method does not make an employer’s file subject to federal procurement standards.

Test for the sentence a reader could misunderstand

Open the version you expect to send and find the section explaining how to ask HR for help. Move there by headings if your reader supports it. Continue through the first full paragraph and any nearby note. If a sample deadline, advice, or unrelated phone number is spoken mid-sentence, record exactly where it enters. For a bulleted section, find out whether the numbers are merely visual or whether the structure tells the reader that these items belong together. On a multi-page notice, check that decorative titles and footers do not repeatedly interrupt the main text.

Where a table is needed, have the tester name the row and column associated with a sample cell. A calendar that lists morning and evening help windows can be clearer as short headings and paragraphs if it only compares two cases. For genuine tables, pass the meaningful header associations through to the output. Check what happens when the reader reaches a course link or support link. Is the destination described in words, and does the focus path follow the text? A link that points to a different date or file is a content bug even if it is perfectly keyboard accessible.

Review the document’s declared language and any language switches relevant to reading. This matters when a notice includes a full paragraph letting employees know a translated edition is available. Test the sentence on the reader combinations you support. On the HTML counterpart, use the markup for actual language changes; simply italicizing foreign text does not tell assistive technology how to interpret it.

Make the second format comparable

Sometimes a signed, issuer-supplied or locked document cannot be edited without permission. Separate that constraint from work you can do. Request a verified accessible version from the document owner. In the meantime, put a clearly dated, accessible explanation of the employer’s process next to the source where appropriate. Identify its scope. A short description of the employer’s help route is not a substitute for the complete, applicable disclosure or agreement. Do not remove legally material text to get a better checker score, and ask the appropriate owner how the required original should be provided in a usable form.

Publish file formats with descriptive link text instead of serving an unnamed attachment. If the HTML version contains the same operative information, say so after comparing both. If it is an editorial summary, label it. Include accessible formats in the same release schedule and check each attachment from a recipient’s test inbox. Write a short playback note with the location, expected order, actual order and what changed in the export.

A quick keyboard and screen-reader pass will expose failures in the notices around the PDF, too. Set up an alternate-format request handoff for readers whose needs the published versions do not meet. For dated bilingual versions, use the language review procedure.