
Accessibility
Fixed-Layout EPUB Accessibility: What Publishers Need to Test Before Release
Fixed-Layout EPUB Accessibility: What Publishers Need to Test Before Release
Fixed-layout EPUB is often the right choice when the design of a page carries meaning. Children’s books, comics, illustrated textbooks, cookbooks, activity books, and highly visual educational titles may depend on the exact relationship between text, images, labels, and page elements.
That design strength can also create accessibility challenges.
A fixed-layout EPUB may look excellent on screen while presenting a confusing reading order to a screen-reader user. Text may be difficult to enlarge. Important words may be embedded inside images. Interactive features may work with touch but fail with a keyboard. Two-page spreads may also lose meaning when shown one page at a time.
For publishers, fixed layout EPUB accessibility should therefore be part of production planning, not a final check added before release.
The goal is not simply to reproduce the print page. The goal is to preserve the information, relationships, and purpose of the publication for readers who may not experience the page visually.
When is fixed-layout EPUB the right choice?
The first accessibility decision happens before production begins.
Not every illustrated title needs fixed layout.
Fixed layout makes the most sense when the position of content is essential. A comic may depend on panel order. A picture book may connect one sentence to a specific illustration. A textbook may place labels around a diagram. A workbook may depend on carefully arranged activities.
In these cases, moving elements freely could change the meaning.
But if the design is mainly decorative, a reflowable EPUB may offer readers more control over text size, spacing, margins, and screen width.
That makes format selection part of accessibility planning.
Publishers should ask:
Does the content require fixed positioning, or does the design simply prefer it?
Making that decision early can prevent expensive changes later.
Reading order should make sense without the visual page
Reading order is one of the most important areas to test.
A sighted reader naturally uses page position to understand what comes first. A heading may appear at the top, followed by body text, an illustration, and a caption.
A screen reader follows the underlying content order.
If that order is wrong, the page can sound completely different from the way it appears.
For example, a reader might hear a caption before the image it describes, a sidebar in the middle of a paragraph, or a decorative label before the main heading.
The EPUB may still look correct.
The reading experience will not.
A useful test is to listen to the page without looking at it.
Ask whether the content still follows a clear sequence. Headings should appear at the right point. Body text should remain together. Captions should sit logically near the content they describe.
If the sequence is confusing, the reading order needs to be corrected.
Visual position should not replace document structure
Fixed-layout production naturally focuses on placement.
But coordinates are not structure.
A heading should still be identified as a heading. A list should remain a list. A table should preserve the relationship between its headers and data. A figure should have the right role. Links should be clear and usable.
This matters because assistive technology depends on the underlying structure of the EPUB.
Large bold text may look like a heading to a sighted reader. If the markup does not identify it as one, the user may not be able to navigate to it as a heading.
Strong fixed-layout production therefore protects two things at the same time:
visual design and semantic structure.
Neither should replace the other.
Important text should remain accessible text
Some fixed-layout titles use page images to preserve print design.
That can create problems when important words exist only inside those images.
If the text is not available as real digital text, readers may not be able to search it, select it, enlarge it, or use it effectively with assistive technology.
Where possible, important content should remain as real text rather than becoming part of an image.
This is especially important for educational and reference content.
Some publications will still contain text inside artwork. Comics, maps, diagrams, worksheets, and highly illustrated books may need it.
In those cases, publishers should ask:
If the reader cannot see this text, how will they access the same information?
The answer may involve real HTML text, structured SVG text, alternative text, or another accessible treatment.
Test text enlargement before release
Readers do not all use the default text size.
Some need larger type. Others increase line spacing or word spacing.
Fixed layout can make these changes difficult because each text block has been designed to fit within a specific area.
When text grows, it may overlap another element, move outside the visible region, cover an image, or hide a control.
That is why visual QA at the default setting is not enough.
Test larger text sizes where the reading system allows it. Check whether content remains visible and understandable.
Also review spacing changes.
A layout that looks fine at its default size may fail as soon as a reader increases line or word spacing.
These tests help reveal whether the design gives readers enough flexibility.
Understand the limits of reflow
Reflow is one of the biggest differences between fixed-layout and reflowable EPUB.
In a reflowable title, text can adapt to the size of the screen.
In fixed layout, the page normally stays in place.
When a reader zooms in, the result may simply be a larger version of the same page. The user may then need to move left, right, up, and down to follow one paragraph.
This can make reading slower and more tiring.
Before release, publishers should test what happens when the page is enlarged.
Check whether important content stays visible, whether navigation remains practical, and whether the reader must move in several directions to follow basic text.
If the title depends heavily on long passages of text, that may be a sign that reflowable EPUB would provide a better experience.
Images need the right level of description
Fixed-layout EPUBs are often image-heavy.
That makes image treatment a major accessibility task.
The first question should not be:
“Does this image have alt text?”
The better question is:
“What information does this image provide?”
A decorative image may need no meaningful description. A photograph may need a short one. A chart may need a summary of the main trend. A complex diagram may need a longer explanation.
The description should preserve the information the reader needs.
It does not need to describe every colour, line, or decorative detail unless those details matter to the meaning.
For publishers, image descriptions should be treated as editorial content rather than as a technical field to complete at the end.
Text inside images needs extra attention
Some visuals contain essential words.
Examples include maps, speech bubbles, infographics, worksheets, diagrams, and labels.
A sighted reader sees the text as part of the image.
A screen reader may not.
If those words carry meaning, the EPUB needs another way to expose them.
This may involve real text, structured SVG, alternative text, an extended description, or another accessible representation.
The goal is simple:
essential information should not depend only on sight.
Test two-page spreads in more than one view
Two-page spreads are common in illustrated publishing.
They can also create accessibility problems.
Imagine a diagram on the left page and its explanation on the right. On a tablet, both pages may appear together.
On a phone, the reader may see only one page at a time.
That can break the relationship between the content.
Important spreads should therefore be tested in both spread view and single-page view.
Ask whether the meaning remains clear when only one page is visible.
If it does not, the EPUB may need stronger structural links or an alternative explanation.
The visual spread should not be the only way the relationship can be understood.
Navigation should support real reading tasks
Fixed layout does not remove the need for good navigation.
Readers should be able to move through the publication without turning every page one by one.
Depending on the title, navigation may include a table of contents, chapter links, page navigation, internal links, and landmarks.
This is especially important in educational and reference publishing.
A teacher may ask students to move to a specific page. A researcher may need to return to a figure. A reader may want to jump directly to a chapter.
The navigation should support those tasks without unnecessary effort.
Gentize already covers EPUB page navigation in a separate article, so the focus here is not on implementation. The important point is to test whether navigation works correctly inside the fixed-layout reading experience.
Interactive content needs more than visual testing
Some fixed-layout EPUBs include interactive content.
Examples include audio controls, quizzes, hotspots, menus, pop-ups, and video controls.
These features should work for more than touch users.
For each control, ask:
- Can the reader reach it?
- Is its purpose clear?
- Can it be used with a keyboard?
- Does the focus move in a logical order?
- Does the reader know what happened after using it?
For educational titles, this is especially important.
If a student cannot complete an activity, the accessibility problem becomes a learning barrier.
Interactive features need both functional QA and accessibility QA.
Keyboard focus should follow a logical path
Focus order matters whenever the EPUB contains interactive elements.
A keyboard user should be able to move through controls in a sequence that matches the page.
The focus should not jump from the top of the page to the bottom and then back to the middle.
That creates confusion even if every control works individually.
Testing without a mouse is a simple way to expose these problems.
If the focus order feels unpredictable, the page needs more work.
Colour should not carry meaning by itself
Fixed-layout titles often use colour as part of the design.
That is fine.
But important information should not rely only on colour.
For example, a workbook may use green for correct answers and red for incorrect ones.
Readers who cannot easily distinguish those colours may lose the meaning.
Add another cue, such as an icon, text label, shape, or pattern.
Also check text contrast, especially when text sits over images, coloured panels, or pale backgrounds.
A professional design can still be visually rich while remaining clear.
Avoid unnecessary orientation locks
Some fixed-layout books are designed for landscape or portrait use.
But forcing one orientation can create barriers.
A reader may use a device mounted in a fixed position. Another user may not be able to rotate the screen easily.
If the publication works in both orientations, give readers that choice.
Only restrict orientation when the content genuinely depends on it.
A design preference alone is not a strong reason to reduce user control.
Accessibility metadata should match the final EPUB
Metadata helps platforms and readers understand what accessibility features a publication supports.
It may describe navigation, text alternatives, structural information, or known hazards.
The important point is accuracy.
Do not claim a feature simply because it was planned during production.
Check that the final file actually provides it.
Accessibility metadata should be part of the QA process, not a last-minute administrative task.
Test the EPUB in more than one reading system
A fixed-layout EPUB may behave differently across reading apps.
One application may expose image descriptions well. Another may handle zoom differently. Navigation may work smoothly in one environment and less well in another.
Publishers do not need to test every reading system available.
They should choose a useful sample based on the audience.
For trade publishing, consumer reading apps may matter most.
For educational titles, classroom and institutional platforms may be more important.
The test set should reflect how readers are likely to use the publication.
Automated validation is only one part of QA
Technical validation is essential.
It can identify broken markup, packaging errors, missing resources, and other technical problems.
But validation cannot judge the full reading experience.
A tool cannot always decide whether a reading order feels natural. It cannot judge whether an image description explains the right information. It cannot tell whether a complex spread is easy to understand.
That is why fixed layout EPUB accessibility testing should use several layers:
Validation → Manual Review → Human Testing → Correction → Retest
Each stage finds a different type of problem.
Human QA should test complete reading journeys
Human testing is most useful when testers use the publication as a reader would.
Instead of checking isolated elements, ask them to open the title, use the table of contents, move to a chapter, read several pages, follow a link, review image descriptions, use a spread, and try interactive features.
This reveals problems that individual technical checks may miss.
A page may pass validation but still feel confusing.
The goal is not simply to prove that assistive technology can find an element.
The goal is to confirm that a reader can use the publication with confidence.
Gentize supports screen-reader testing, keyboard testing, and human-led accessibility QA as part of its accessibility services.
Use a risk-based QA plan
Not every page needs the same level of review.
A title with one repeated layout may need deep testing on selected pages.
An illustrated children’s book may use a different composition on every spread.
A textbook may combine standard pages with diagrams, tables, quizzes, and interactive elements.
Publishers can use a risk-based QA plan to decide where deeper testing is needed.
QA Area | What to Test |
|---|---|
Format choice | Does the title truly need fixed layout? |
Structure | Are headings, lists, figures, and tables represented correctly? |
Reading order | Does the page make sense without visual position? |
Text | Is important text available to assistive technology? |
Enlargement | What happens when text or the page is enlarged? |
Images | Do meaningful visuals have useful descriptions? |
Spreads | Does the meaning survive single-page viewing? |
Navigation | Can readers move to important content easily? |
Interaction | Do controls work without touch alone? |
Focus | Does keyboard focus move in a sensible order? |
Metadata | Do accessibility claims match the final file? |
Reading systems | Has the EPUB been tested in realistic environments? |
Human QA | Can readers complete normal tasks successfully? |
This approach gives publishers a clearer way to plan time, cost, and QA depth.
Common mistakes publishers should avoid
One common mistake is treating the print edition as the accessibility model.
Print and EPUB are different formats.
The digital edition may need a different structure even when the visual design remains similar.
Another mistake is checking only appearance.
A publisher may compare every page with the print file and still miss a broken reading order or poor keyboard focus.
A third mistake is adding accessibility after production is complete.
If hundreds of pages have already been built as images, adding usable text and structure later may be much harder.
Accessibility should be planned during production, not treated as a repair stage.
When should publishers choose reflowable EPUB instead?
Reflowable EPUB is often a better choice when the publication is mainly text.
It gives readers more control over font size, spacing, margins, and screen width.
That does not mean reflowable EPUB is automatically accessible.
It still needs correct structure, navigation, images, tables, metadata, and QA.
But it removes some of the limits created by fixed positioning.
If the meaning of the book does not depend on exact spatial relationships, reflowable EPUB may provide a more flexible reading experience.
How Gentize supports fixed-layout EPUB accessibility
Gentize supports fixed-layout and reflowable EPUB as part of its digital publishing and accessibility services.
Support can include EPUB production, structural review, reading-order QA, image descriptions, complex content, tables, navigation, validation, screen-reader testing, keyboard testing, and human accessibility QA.
For fixed-layout titles, these activities should work together.
The design cannot be reviewed separately from the reading order.
Alt text cannot be reviewed separately from the purpose of the image.
Validation cannot replace human testing.
A representative pilot is often a useful starting point.
The pilot should include the most difficult pages, not only the easiest ones.
For an illustrated title, test an important spread.
For a textbook, include a page with labels, tables, images, and links.
For an interactive title, include the main controls.
This helps define the right production and QA approach before the full title or backlist moves forward.
A better pre-release decision
Before release, publishers often ask:
“Did the EPUB pass validation?”
That question matters.
But it should not be the only question.
A stronger review asks whether the reading order makes sense, important text is available, meaningful images are explained, navigation works, controls are usable, and the title behaves well in representative reading systems.
It should also ask whether someone has tested the real reading experience.
If those questions have clear answers, the publisher has much stronger evidence that the EPUB is ready.
Final takeaway
Fixed-layout EPUB is excellent at preserving design.
That is also what makes accessibility more challenging.
The visual page may communicate relationships that are not obvious in the underlying content.
Publishers should therefore test more than appearance.
A reliable process is:
Choose the Format → Build the Structure → Check Reading Order → Review Text and Images → Test Navigation → Validate → Human Test → Correct → Retest
The final question should not be:
“Does the ebook look exactly like the print edition?”
It should be:
“Can readers access the same information and purpose without depending on the visual layout?”
That is the standard publishers should use before release.
Frequently asked questions
What is fixed-layout EPUB accessibility?
Fixed-layout EPUB accessibility means making a fixed-page ebook usable for readers with different access needs. This includes clear structure, logical reading order, useful image descriptions, navigation, accessible controls, and support for assistive technology.
Why is reading order important in fixed-layout EPUB?
The visual position of content does not automatically control the order used by screen readers. If the underlying order is wrong, headings, captions, sidebars, and body text may be read in a confusing sequence.
Should every illustrated book use fixed-layout EPUB?
No. Fixed layout is most useful when meaning depends on exact spatial relationships. If the content works well without fixed positioning, reflowable EPUB may offer readers more control.
Is EPUB validation enough before release?
No. Validation can find many technical problems, but it cannot fully judge reading order, image meaning, interaction quality, or the overall screen-reader experience. Manual review and human testing are also important.
How should publishers test fixed-layout EPUB accessibility?
Publishers should review structure, reading order, text access, images, page enlargement, navigation, interactive controls, keyboard focus, metadata, reading-system behaviour, and real assistive-technology use.
Keep reading
Accessibility
White-Label PDF Remediation Services for Agencies
Need more PDF remediation capacity without expanding your team? Discover how white-label partnerships help accessibility agencies manage client projects, quality and delivery. Copy
Accessibility
EPUB Accessibility Metadata: What Publishers Must Check
Accessibility
Document Accessibility Remediation Services: PDF & EPUB QA
PDF and EPUB files need different accessibility checks. Learn how publishers can improve document structure, navigation, tables and human QA before release. Copy
Related services
Want this kind of work shipped on your project?
Brief the studio
Got something on your desk that needs this kind of attention?
Tell us the rough outline. We reply within a working day with a scoped response from the practice lead — not a sales person.
