Overview

Fixed-layout publications can be created using HTML documents to combine text and images. Each document is assigned a fixed height and width, the canvas on which the content is positioned. CSS is used to absolutely position content elements within this display area, or images are embedded in the page that fit the dimensions.

The advantage of using HTML for fixed layouts is that it makes the text content of each page available to assistive technologies. In the case of images, it allows the native accessibility techniques HTML affords to be used to provide alternative text and extended descriptions.

EPUB

Although it is possible to create fixed layouts on the Web, they are not naturally supported by browsers. A browser will render the page as designed but not make any optimizations to support the rendering.

To fix this problem for publishing, EPUB 3 introduced metadata to aid reading systems in creating the appropriate display area and characteristics for each fixed layout page.

EPUB publications can consist entirely of fixed layout XHTML pages or there may only be a few fixed layout pages interspersed in a reflowable publication (e.g., a map might be included as a fixed layout in an otherwise reflowable publication).

It is also possible to mix fixed-layout SVG pages with fixed-layout XHTML pages, or with images directly in the EPUB reading order.

Note

Refer to the fixed layouts overview page for more information about how fixed-layout publications are created.

Accessibility

The same practices that make reflowable publications accessible are used to create fixed layout HTML pages with the greatest accessibility. Some key practices include:

Even when following these practices, a key problem that limits the accessibility of fixed layouts is that reading systems often lock out users from changing the appearance of the documents to preserve the author's layout (e.g., disabling the ability to increase font size or changing text color). As a result, even the best efforts to make a fixed-layout publication accessible may still leave it unreadable to some users.
http://kb.daisy.org/publishing/docs/fxl/html.html
kb.daisy.org
crawl=CC-MAIN-2022-33
5519
application/http; msgtype=response
sha1:33E2DCC6RFKIBEMHZPVXTXQMLMYCGB4U
<urn:uuid:1ec78c13-62e8-479a-92c4-2d4d84be4772>
2022-08-20T02:53:04Z
185.199.111.153
text/html
sha1:NTDHU6Z5Q5K3E7DQ5SE2QQWELWKD56IL
<urn:uuid:bac2c403-e81b-4402-90e3-1e733ea29c85>
http://kb.daisy.org/publishing/docs/fxl/html.html
response
<urn:uuid:7cc484c8-ed1a-4aeb-a3e1-a2edbd2f9e8d>
isPartOf: CC-MAIN-2022-33
publisher: Common Crawl
description: Wide crawl of the web for August 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-170
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/