A resume can look polished and still be hard to read
A lot of resumes fail in a very quiet way.
They look sharp on screen. Clean fonts. Neat columns. Maybe a sidebar, a few icons, a touch of color. But once that file is opened by a screen reader, moved into another app, or exported badly as a PDF, the polish stops helping. Microsoft’s accessibility guidance for Word recommends built-in heading styles, accessible link text, readable font and color choices, proper lists, and avoiding tables for layout because those choices directly affect whether a document can be read and navigated properly.
That matters because resumes are rarely reviewed in one perfect setting. They get skimmed on laptops, forwarded between teams, saved as PDFs, and sometimes reviewed with assistive technology. W3C explains that headings are not just visual decoration. They help communicate the organization of a page, and assistive technologies can use them for navigation. GOV.UK makes a similar point from the document side: if your Word file is accessible, it is much easier to turn it into an accessible PDF later.
So this is not about making your resume plain for the sake of it. If you want a broader look at why formatting still matters in hiring, see our guide on resume formatting and why it matters.
It is about making sure the content survives the trip from your computer to someone else’s workflow without losing clarity.
What accessible resume formatting actually means
An accessible resume is one that can be read, navigated, and understood without forcing the reader or the software to guess what you meant. In practice, that usually means a clear top-to-bottom flow, real headings instead of text that merely looks like headings, strong contrast, descriptive links, proper list formatting, and very little decorative clutter. For a deeper look at how hiring systems actually read candidate files, our article on resume parsing is a useful next step. Microsoft also advises keeping important information in the main body of the document rather than relying on headers and footers, because that content may be missed or treated inconsistently by assistive tools. See Microsoft’s accessibility guidance for Word.
The core rules for an accessible resume
Start simple.
A one-column resume is usually the safest option. Not because columns are always impossible, but because the more you split the page into competing zones, the more chances you create for the file to be read out of order or handled inconsistently after export. Microsoft recommends avoiding tables where possible, and GOV.UK says tables should not be used to lay out page content. For resumes, that same logic applies to sidebars, floating text boxes, and visual blocks that exist mainly for design.
Next, use standard section names and make them real headings.
“Experience,” “Education,” and “Skills” should not just be bigger bold text. They should be actual heading styles created with Word’s built-in tools. W3C’s guide to headings explains why proper heading hierarchy helps screen readers understand and navigate a document.
W3C explains that headings help users understand how content is organized and help assistive technologies navigate it. Microsoft says the same thing in practical terms: use built-in title, subtitle, and heading styles instead of manually styling text to look right.
Keep the typography easy to read.
Microsoft recommends accessible font formatting and color choices, including avoiding low contrast text and using the Accessibility Checker to catch hard-to-read contrast issues. WebAIM’s guidance on contrast explains why this matters: users with visual disabilities still need to perceive content clearly, and low contrast gets in the way fast. In plain terms, dark text on a light background is still one of the best choices you can make. It is boring. It is also reliable. If you want to test your color choices manually, the WebAIM Contrast Checker is a quick way to catch contrast problems before you send the file.
Be careful with links too.
A raw URL dumped into the resume is rarely the best move. W3C’s guidance on link purpose says link text should identify the purpose of the link so users can decide whether they want to follow it, even when assistive tech presents a list of links out of context. That means “LinkedIn profile,” “Portfolio,” or “GitHub repository” is usually stronger than pasting a long web address across the page. W3C’s guidance on link purpose is a useful reference if you want to understand why descriptive link text makes documents easier to use.
Use real lists.
Do not fake bullets by typing hyphens manually or spacing things until they look right. We also break down the basics of what automated resume formatting is and why consistency matters more than visual flair.
Microsoft recommends built-in bulleted and numbered lists because they are easier for screen readers to interpret correctly. GOV.UK makes the same recommendation for accessible Word documents. This is one of those small choices that feels trivial while editing and matters later when the file is being read another way.
And keep visuals on a tight leash.
Most resumes do not need icons, logos, charts, or decorative graphics. If a visual is carrying real meaning, Microsoft says it should have alt text. If it is decorative, it is often better to remove it or make sure the important information appears in normal text instead. Text placed inside an image is especially risky because assistive tools cannot treat it like ordinary document text.
Resume choices that quietly break accessibility
The biggest accessibility mistakes often look modern.
That is why people keep making them.
The classic example is the stylish two-column template. One side holds contact information, skills, icons, maybe links and certifications. The other side holds work history. Visually, it can look efficient. Functionally, it introduces more chances for the document to be read in the wrong sequence or for content to become fragile when the file moves between apps. Microsoft’s advice to avoid layout tables and GOV.UK’s guidance against using tables for page layout both point in the same direction: simpler page flow is usually the safer choice.
Another common failure is the image-like PDF.
Adobe explains that scanned pages and image-based text are accessibility problems because assistive software cannot read them the way it reads searchable text. A file can look perfectly normal to you and still be functionally locked to a screen reader. That is why the source file matters so much. If the original Word document is accessible and the export is handled properly, you are in a much better position.
Then there is the small stuff that adds up.
Pale gray body text. Full paragraphs in italics. Headings that only look like headings. Visual labels with icons but no words. Contact details tucked into a header. None of these choices sounds dramatic on its own, but together they make the resume harder to scan, harder to reuse, and less dependable when assistive technology gets involved. Microsoft specifically flags low contrast, missing alt text, weak heading use, and poor list formatting as issues worth fixing.
How to test your resume before you send it
Do not trust your eyes alone.
Test the file.
Microsoft’s Accessibility Checker is the first stop because it can flag common problems such as low contrast, missing alt text, and other issues that make documents harder to read and use. Run it in Word before export, not after. Microsoft also says that checking accessibility before saving as PDF helps preserve accessibility information in the final file.
Then do a manual pass.
Check whether your section titles are real headings. Check whether your bullets are actual list items. Check whether your links still make sense when read on their own. If you are using color beyond plain black text, test the contrast with a tool like WebAIM’s Contrast Checker. WebAIM notes that its tool lets you test foreground and background colors directly, and its contrast guidance explains why color and contrast choices matter for users with visual disabilities.
Finally, reopen the exported PDF and verify it again.
Adobe’s accessibility tools are built for exactly this problem. Adobe says accessible PDFs depend on searchable text, tags, and correct reading order, and its accessibility checker can flag common issues such as scanned text, images, tables, and missing document information. A PDF is not “done” just because it opens. Adobe’s guide to creating and verifying PDF accessibility is a good reference for understanding tags, reading order, and why some PDFs still fail screen readers. It is done when it still works.
Why this matters for recruiters and staffing agencies too
For one candidate, this is a single-document problem.
For recruiters, it is a repeatable workflow problem.
Teams receive resumes in every possible format, from clean Word files to heavily designed PDFs that look good and behave badly. If those resumes are being cleaned up, reformatted, anonymized, or sent on to clients, accessibility should improve during that process, not get stripped out. The same best practices still apply: real headings, clear flow, readable text, meaningful links, and careful PDF export. Simpler files tend to travel better across teams and tools.
That is also the natural place for a subtle iReformat mention.
Not as the point of the article. Just as a practical example. When an agency is handling many resumes and trying to keep formatting clean and consistent, a tool like iReformat can help reduce manual cleanup and make it easier to apply the same accessibility-minded choices across many files.
Quick FAQ
Can I use columns on a resume?
Yes, but a single-column layout is usually more reliable. Simpler page flow is less likely to create reading-order problems and less likely to break during export or reuse.
Are PDF resumes accessible?
Some are. Some are not. Adobe says accessible PDFs rely on searchable text, tags, and correct reading order, so a PDF is not automatically accessible just because it opens correctly.
Is ATS-friendly the same as accessible?
Not exactly. They overlap a lot, but accessibility also covers navigation and how assistive technology reads the document. W3C’s guidance on headings and link purpose helps explain why that extra layer matters.
To learn about applicant tracking systems, read our dedicated guide.
Do resumes need alt text?
Only when a visual is doing real communication work. If the icon, logo, or image is just decorative, the better move is often to remove it and keep the meaning in normal text.
Final takeaway
A screen-reader-friendly resume is usually not flashy.
It is clear.
That clarity helps people using assistive technology. It helps recruiters skimming quickly. It helps the file survive Word, PDF, email, and handoff without falling apart. Accessibility is not extra polish added at the end. It is solid formatting from the beginning.
If you want, I can now turn this into a CMS-ready version with meta title, meta description, slug, and internal link suggestions for Recruiteze.