Accessible PDF Menus and HTML Menu Delivery
Publish a structured HTML menu first, with a usable PDF download second. Scope OCR, tags, reading order, tables and screen-reader verification without treating a text layer as a complete fix.
For Florida restaurants, a guest should be able to read items and prices in the browser without downloading a file. We scope a structured HTML menu as the primary version and a remediated PDF as a secondary download where one is needed.
Put the menu on the web first
Publish real text for sections, items, prices and relevant descriptions in a structured HTML menu. Keep it usable at phone width and zoom, with headings that allow navigation and links that say where they go. A printable PDF can remain a clearly labeled secondary download; maintain a process to keep both versions aligned when dishes or prices change.
See the restaurant PDF menu guide and restaurant website service for reservation and ordering handoffs.
Repair the PDF as a document, not just an image
An image-only menu may need OCR to create selectable text, followed by correction against the approved source. A text layer alone is not an accessible PDF. Check document tags and headings, meaningful reading order across columns, table headers and associations where tables are genuinely used, image alternatives, contrast, actionable links, document language and title metadata. Preserve approved menu content and assets rather than inventing items or descriptions.
The W3C PDF3 technique discusses correct reading order in PDF. Tags alone do not prove the reading experience is usable.
Verify the delivered versions
Agree on the source file, menu version, HTML placement, PDF delivery and update owner. Check the HTML with keyboard, zoom and structure review, and scope an actual screen-reader usability session for the PDF if required. Record what was checked, correct observed order or label defects, and retest the delivered file. A checker pass does not establish human readability.
PDF remediation and human screen-reader validation are separately scoped. See how a human session is documented.
Plan menu delivery
Core website remediation starts at $2,449 for up to 15 pages after scope confirmation; specialist PDF work is separate. Monitoring starts at $49/month for agreed pages, not unlimited menu edits or document repairs. Request a free public-page scan for initial website signals or request a menu project estimate. See the service overview.
Sources
Request a free accessibility scan
Selected public pages only; not human review or recurring enrollment. Request a free scan.
Request a scoped estimate
Specialist PDF work is separately scoped from website remediation. Tell us about the approved source menu, HTML version and secondary PDF.
Frequently Asked Questions
Can we keep the printable PDF?
Yes. Keep it as a clearly labeled secondary download while the structured HTML menu is the primary way to read items and prices. Agree on an update owner so the two versions stay aligned.
Is OCR or adding tags enough to make a menu accessible?
No. Correct OCR text against the approved source, then review headings, reading order, tables, contrast, links, language and title. Tags or a selectable text layer alone do not establish screen-reader usability.
How is the delivered PDF verified?
Agree on the document version and checks, inspect its structure and reading order, scope an actual screen-reader session if needed, then record and retest observed defects. Do not treat a checker pass as proof of complete accessibility.
Is specialist PDF work included in the starting website price?
No. Specialist PDF remediation and human screen-reader validation are separately scoped. Core website remediation starts at $2,449 for up to 15 pages after scope confirmation; monitoring starts at $49/month for agreed pages.