Your architecture portfolio may be visually polished and still be difficult to open, search, navigate or read. A recruiter may review it on a phone, a laptop with limited bandwidth or an assistive technology setup. A hiring manager may try to copy your email address from the file and discover it is baked into an image. These are practical failures of the application, not merely aesthetic details.
An accessible PDF helps more people understand your work. It can also make your own story clearer: real headings, meaningful captions and an intentional reading order force you to decide what the reader should encounter first. You do not need to turn a design portfolio into a plain report. You do need to ensure that the design survives the way real people receive it.
Test the file in the conditions you send it into
Export a short first-contact portfolio and open it on a normal laptop, phone and, if possible, a slower connection. Do not judge the PDF only on the large monitor used to design it. Check the file size, load time, page orientation and whether details remain readable at ordinary zoom. There is no universal magic megabyte limit; follow an employer’s stated cap and make a lighter version when the delivery route is uncertain.
If images are enormous, optimise them for screen viewing while keeping drawings legible. Export at a reasonable resolution, remove unused layers where appropriate and avoid embedding multiple full-size renders behind tiny crops. Compression should be checked visually. A section whose notes become unreadable after export is not improved by a small file size.
Give the PDF a useful file name, such as Maya_Chen_Architecture_Portfolio_2026.pdf, and add your name and contact details inside. Files are often downloaded, renamed or forwarded away from the original email. Put the role or location in the email subject rather than stuffing every application detail into the file name. Check that the file opens without a password or access request unless the employer agreed to one.
Use real text for essential information
Your name, headings, project captions, dates and role descriptions should be actual selectable text. A whole page exported as a flat image can look perfect while being hard to search or read with assistive technology. Try selecting the text and copying a paragraph into a plain editor. If the characters are missing or arrive in a nonsensical order, revisit the export settings.
Use fonts that remain readable at common viewing sizes. Tiny grey text may be elegant on a print mock-up and useless on a laptop. Aim for clear contrast and avoid placing important words across busy photographs. If the diagram contains labels that carry the argument, make them readable or repeat the key information in a nearby caption.
Real text also helps a recruiter find your contact details and project keywords. Do not treat that as a promise that an applicant tracking system will interpret every designed PDF correctly. Systems vary. Keep a separate, simple résumé for forms that request one; let the portfolio do its own job of explaining work.
Create a logical reading order
A two-column portfolio spread may look natural to a sighted reader but export in a surprising order: right caption, footer, left heading, image label. Tagged PDF structure and reading order matter for assistive technology. The W3C technique for PDF reading order explains that the logical order should match the intended meaning, and it recommends checking the sequence with relevant tools or a screen reader. It is a technique, not a guarantee that every PDF will work on every device.
Start with a simple page hierarchy: project title, brief, your role, key decision, image descriptions and outcome. Use the authoring tool’s accessible export options, headings and tags where available. Then inspect the resulting PDF’s tag order. If you can, read it aloud with a screen reader or use a PDF accessibility checker and manually review what the checker flags. A pass result is not a substitute for reading the actual sequence.
Avoid a layout where the only way to understand the project is to see that a red arrow points to a green box. Give the same relationship a text label: “Revised public route” and “Existing service zone.” Colour can help, but it should not be the only carrier of meaning.
Describe images according to their role
A hero photograph may set context. A plan may explain the central decision. They need different text alternatives. For a plan showing a new entrance sequence, describe the meaningful relationship: “Ground-floor plan showing the new public entrance on the east side and a separate staff route.” You do not need to narrate every door and line if the adjacent text already covers them. Decorative images can be marked as such in the PDF structure when your tool supports it.
The W3C PDF technique on text alternatives provides examples of adding alternatives to images in tagged PDFs. Use it as guidance, then test your own document. A generic alternative such as “architecture image” communicates almost nothing. A 200-word inventory of every visible object can obscure the point. Describe what the image contributes to the page’s argument.
If you include a chart or complex diagram, add a brief adjacent explanation of the conclusion. A portfolio can remain visual while allowing someone who cannot see the exact marks to follow your reasoning. This also benefits a hurried hiring manager viewing a small preview.
Make links and navigation usable
Link text should say where it goes: “Full case study,” “Project publication” or “Email Maya,” rather than “click here.” Test each link after export. Avoid a portfolio where all project navigation depends on tiny icons with no labels. For longer PDFs, bookmarks can help a reader jump to projects. A short portfolio may only need a contents page, but the page numbers should match the actual PDF sequence.
Check whether links in captions point to public pages that you are permitted to share. Do not link to private cloud folders that ask the interviewer to request access. Test every URL in a private browser session to catch permissions you may not see while logged in.
If the application system strips links, the file should still make sense without them. Include the essential evidence within the submitted PDF, and use external case studies as optional depth. A link is not a substitute for a readable first page.
Run a five-minute quality check
If you use a portfolio website alongside the PDF, keep the essential project facts consistent between them. A recruiter may open one while a hiring manager opens the other. Different dates, roles or statuses can create unnecessary questions. The website may be easier to update, but the submitted PDF is a snapshot of what you claimed at application time. Archive that version so you know exactly what the firm saw.
Before sending: open the exported file; scan at 100% on a laptop; inspect the first two pages on a phone; copy the contact details; search for a project keyword; tab through links; check the reading sequence; and confirm that each page credits your contribution. Ask someone unfamiliar with the project to describe your role after thirty seconds. If they cannot, the problem may be editorial rather than technical.
Send the file to yourself using the same route the employer will use. If a mail provider rejects it or a cloud link requests permission, fix that before applying. Keep a version number privately so a corrected export does not get confused with an earlier one. If you update a link after submission, make sure it still points to the same approved materials.
The AIA’s portfolio advice for job seekers makes a simple point: reviewers need to understand your work and contribution. Accessible delivery supports that goal. A portfolio succeeds when the right person can open it, navigate it and understand what you actually did, in the time and tools they have.
Browse current architecture jobs on Jobs.archi and compare your next step with our architecture portfolio and interview guide.
The post The Accessible Architecture PDF: File Size, Text and Reading Order Matter first appeared on jobs.archi.