Publications, from corporate memos to newsletters to electronic books to scholarly journal articles, must be considered first-class content on the Web, equal to the more common forms of Web pages available today. This document describes the various use cases highlighting the problems users and publishers face when these publications are to be used in a digital, Web environment. The requirements that come from those use cases provide the basis for the technical considerations in a companion document, currently entitled “Web Publications” [[wpub]].

This is work in progress. The final version of this document is planned to be published as a Working Group Note.

A previous version of this document was published by the Digital Publishing Interest Group as an Interest Group Note. After the closure of that Interest Group the Publishing Working Group took it over for further work.


The Web emerged in 1994, based on a model of individual pages loosely joined by hyperlinks. Clustering within domains and with explicit navigation elements built into them, webpages evolved into websites. Despite the Web's strong connections to print media (e.g. web resources are “pages” and the in-memory model for Web applications is the “Document Object Model”), this document argues that the web platform may still not be meeting certain requirements from print media that users desire.

Over centuries, “books” have assumed many forms: journals, magazines, pamphlets of long-form articles and essays, newspapers, atlases, comics, notebooks, albums of all sorts. We can define these different manifestations as “publications”: bound editions of meaningful media, made public.

Another form of publication that also has a long history in both the printed as well as the digital world are documents. These are publications that are written and distributed in a more ad-hoc manner, such as legal briefs, corporate memos, and even the definitions of standards, such as this content currently being read.

We believe there is great value in combining this older tradition of portable, bounded publications with the pervasive accessibility, addressability, and interconnectedness of the Open Web Platform (OWP). New models of economic sustainability and innovative experiences of knowledge depend on this.

It is the task of the W3C Digital Publishing Interest Group to explore the uniqueness, desirability, and feasibility of bringing these two great models of publishing together. This document explores requirements based on examples of real world use cases and scenarios. Requirements for publications on the Web are explored first, without referring to any packaging aspect that would correspond to current practices like EPUB. This is followed by requirements of those packaging aspects, as a structure on top of a purely Web based distribution. The complete list of requirements is also collected in a separate table in .



Web Standards

Open Web Platform

Web Publications should be able to make use of all features offered by the Open Web Platform (OWP).

There is a remarkable development of tools and frameworks built on top of OWP that make it possible to develop powerful interactive layers on top of OWP. These include, for example, data visualization systems (e.g., d3, built on top of SVG), possibilities to access external services like Wolfram Alpha, or tools to create and store (possibly as part of the publication) annotations. These tools have been traditionally developed around browsers, and provide possibilities that publications should also benefit from. That requires that Web Publications become first class citizens on the Web platform.

  • A large, multidisciplinary, Web-based journal relies on traditional Web technologies like HTML and CSS for its content. The journal, responding to the evolving expectations of its audience, is increasingly using additional media such as video, audio, animated graphics, and very large images; the trend is to consider these as integral parts of the scientific output. The journal as a result needs access to the latest visualization and other data management tools that the OWP-based tools can offer.
  • Educational publications are increasingly making use of OWP features. In addition to video, audio, and animations, they may also include interactive exams (possibly linked to online evaluation facilities), visualization of data or of algorithms, and built-in interpreters for various languages (e.g., for courses on programming). In many respects, the borderline between these publications and Web applications is becoming fuzzy.
  • BigBoxCo, a large technology company with extensive “in-house” documentation to support technical and administrative processes and user documentation for their various products, develops all this material in digital-only formats. The quantity of documentation makes it impractical to produce these documents in print. Instead, the company publishes them on the company intranet, and/or provides them to their employees and contractors via specialized mobile applications. These documents, as a type of publication, require accessibility, portability of annotations, and the possible inclusion of complex media.
  • Like scholarly journals, news outlets are also leveraging OWP features. [Need more expansion on this use case.]
  • [The addition of an example for graphic novels / comics may be worth considering.]

Horizontal Dependencies

A Web Publication should conform to the requirements of all horizontal dependencies.

Web content has to be consumed under different circumstances: it must be available to the largest possible audience in a secure manner, providing the necessary protection of the reader’s privacy. Publication content must be able to answer to a number of principles like accessibility, internationalization, device independence, security, and privacy. (These are usually referred to, in the W3C context, as “horizontal” dependencies.) These principles are, in general terms:

People with disabilities should be able to access the content of a publication. They should be able to perceive, understand, navigate, and interact with it, as well as contribute to it. Accessibility encompasses all disabilities that affect access to the content, including visual, auditory, physical, speech, cognitive, and neurological disabilities.
Publications should be well adapted to any language, writing systems, region, or culture. This includes the usage, when appropriate, of left-to-right, right-to-left, horizontal or vertical writing; item numbering, or interactive forms specific to local cultures; usage of the right character sets and of local typographic conventions.
Device Independence:
The content in a publication should be usable on a large number of devices with very different device characteristics: different screen types and sizes, various input modalities, varying level of processing power, etc. These different affordances should be automatic with no, or very little, user intervention.
Publications should be presented by a User Agent using a security model that is at least (if not more) secure than the standard Web security model. Doing this will prevent publications that contain malicious attacks, data theft, and other security incidents from impacting users by jeopardizing the integrity of the underlying data or machine operations.
The content in a publication should maintain and support user privacy, in spite of the fact that the evolution of online technologies has increased the possibility for the collection and processing of personal, and possibly sensitive, data. However, since a publication may use any part of the OWP, it may choose to use functionality such as the ability to track a user's activity within the publication.

These principles correspond to technical requirements on the underlying technologies (i.e., OWP, and its possible extension to Web Publications) insofar as the technologies must empower the authors (writers, editors, publishers, etc.) to produce content that follow them. Whether authors use the possibilities of these technologies or not is not addressed in this document.

All these constraints are formalized in the context of the usage on the Web and by extension Web Publications. This means that they are valid for publications in general. In some cases, for example due to legislative reasons, the demands on publications may be more stringent than for generic Web sites. The use cases below provide some examples for the publication-specific situations. Note also that some aspect of horizontal dependencies (e.g., accessibility or security), are also the subject of further use cases and requirements elsewhere in this document.

  • (On Accessibility) Legal Publishing Ltd. publishes all the official texts as issued by the government of its country. Per local legislation, the publication must be accessible, following W3C’s WCAG Level AA requirements, to serve as official references in courts.
  • (On Privacy, Accessibility) EducationPublishing Ltd. publishes digital textbooks to cover BigUniversity’s curriculae. These (digital) educational publications also include access to interactive tests via specialized services on the Web that regularly access the student’s progress. The privacy and the integrity of the student’s test data must be preserved. This, and the fact that digital textbooks must also abide to WCAG Level AA requirement in terms of accessibility, are such that EducationPublishing may be liable in case they are not fulfilled.
  • (On Internationalization) PublicationInternational SA. publishes literary work all over the world and in many languages. In order to continue its business in Japan, it must be able to produce digital publications with right-to-left and vertical writing, and following the Japanese typesetting traditions, because that is the only way those publications are accepted by local customers.
  • (On Privacy) Thomas has written a pamphlet advocating a government overthrow. The government has decreed that the author of the pamphlet as well as its readers of the pamphlet shall be jailed. Thomas needs to distribute the pamphlet in ways that preserve his anonymity and allow the public to read without fear of the government cyber-police.
  • (On Device Independence) Yoshio usually reads a book on his tablet when he is at home, but he does not carry his tablet around while commuting on the train. Instead, he prefers to use his phone to continue reading. Publications must be able to adapt to the consumption environment, so as to provide a good reading experience regardless of the device.
  • (On Security) LocalLibrary receives publications from a variety of sources that they then make available to their members. It is imperative that none of these publications can cause any damage to their own systems or those of their members.



Web Publications should include technical and descriptive metadata as well as any additional characteristics of the constituent resources.

A user agent may require information about the publication and its components in order to process it. For example, performance and memory requirements may prevent a user agent from parsing a large number of content documents in order to discover the necessary components and their relationships. A user agent may need to make some decisions about how to present content before displaying it.

A Web Publication should be able to include additional information that the user agent can use like:

  • the rights of various components identified in the package
  • captions belonging to multimedia resources within the publication;
  • whether there is a need for additional processing, such as with MathML;
  • the title, author(s), cover image, etc., to display the publication on a shelf without downloading all its content;
  • Marla is writing an art book and wish to include the rights relevant to the image of the Mona Lisa owned by the Louvre, so that a user agent will know whether it is permissible to download the image for offline use.
  • Ferdous wants to buy a book about a museum exhibit, but before he does that, he wants to guarantee that the images and videos about the exhibits have detailed descriptions, to ensure that he will be able to read it with a screen reader or refreshable Braille display. This can be done because the publisher provided that information as part of the metadata assigned to the Web Publication.
  • A university professor is developing a course and the professor knows that he is required by the university's policy to use digital materials that conform to WCAG 2.0 level AA. The professor searches to determine which titles are accessible and therefore suitable for his use. This can be done because the publishers have added the Accessibility Metadata to the Web Publication, describing the accessbility characteristics for each constituent resource.
  • A library wants to promote a particular type of publication depending on different categories available in a publication’s metadata (age suitability, genre, author). [I did not see some of these fields, such as genre or age suitability, available in the manifest dictionary. Is this something that has been discussed, or something that is accounted for elsewhere?]
  • Is there a way currently outlined (and would it be desirable) to have books with multiple authors (who authored specific chapters) to be identified as the authors of those chapters? I recall some discussion about a WP of WPs as well though. But I can see how this might not always been desirable. Use case: An online literary magazine wishes to compile an anthology of short stories authored by a specific writer. The magazine should be able to identify the stories within the manifests by author and bring those chapters together into a new Web Publication.


The information regarding the constituent resources of a Web Publication must be easily discovered and there should be a way to differentiate between essential and non-essential resources.

A Web Publication will likely be composed of multiple Web documents and their resources. A more complicated Web Publication may have many resources, some of which are essential and some of which are not. Because of this complexity, extracting in advance all the references to some or all constituent resources may be prohibitive. It is therefore necessary for the user agent to have an easy access to the list of constituent resources and some of their characteristics such as whether they are essential, their media types, or their sizes.

In a publication, some content is essential to the user being able to consume it while other content could be either absent or have a provided fallback for situations such as limited connectivity or storage. This information, provided by the author or publisher of the Web Publication, would enable a user agent to provide a better experience to the user. For example, the user agent can ensure that essential resources are made available when offline (see ).

  • Nick is reading a long-form narrative on a device with limited storage: a publication filled with text, images, sounds, and multimedia files. Nick also rides the subway, where he loses Internet connectivity frequently and without warning for long stretches of time. During offline or low-storage situations, there are still critical parts of the publication that are consumable, mainly the text (and possibly images). Having a reasonable fallback for video, such as a poster image or placeholder image, would allow Nick to read the content while offline or on a device with limited storage.
  • Gösta is reading a treatise on the theory of functions. A mathematical font is essential for the proper display of the mathematical formula in this publication, so the author has marked the font as essential so it is made available offline.
  • While reading an article on a new spam analysis algorithm, Lars is primarily interested in the findings of the research. Since the research was funded by a government agency, the dataset, consisting of millions of anonymized log files, is also available. Because of its size, the researchers have marked the dataset as non-essential for conveying the results of the paper and therefore indicates it can be skipped when reading the publication offline.
  • Sarah is reading a publication about the stock exchange. The current value of the stock is fetched (from a remote resource) when she opens the publication. However, when she is on the train (without a connection) one week later and opens the stock exchange publication, she will continue to see the value of the stock as it was the last time she opened the publication. It should be possible for either the content itself or the user agent to provide some user experience that notifies her that the currently presented data is a week old.
  • Risha publishes an article which includes an interactive component that accesses a database, exposed to the Web via a RESTful API. The interactive component is implemented as a JavaScript library. Such data cannot be included in a packaged publication and the interactive module is of no use without such data. Risha therefore marks the Web Publication component relative to the interactive module as not relevant when offline.
  • Stephanie, a student, is answering questions in an assessment embedded in a web publication. Her internet connection is unreliable at home. She should be able, via the user agent or the content itself, to save those responses in the Web Publication. If there is component wherein the student would have to submit the responses to the assessment to a database, a user experience within the Web Publication, provided within the content itself or via the user agent, should notify her whether the data has been successfully submitted.

Alternative Modalities

The notion of a Web Publication should enable specific publications like audio books, graphics books, and mixed media.

All concepts and structures related to a Web Publication should enable the creation and/or production of alternative renderings for visual and auditory content.

  • Faye, a busy mother of five, wants to access audio books while commuting, jogging, doing dishes, or otherwise not able to use her eyes or hands.
  • Khoudia, a librarian focusing on the children's section of her local library, is looking exclusively for material rich in audio and video components so as to reach a wider age bracket.
  • James, a musician, requires that the musical score within a publication come preformatted in braille music notation in order to read it, as he uses freely available assistive technology which does not have braille music translations built in.

Time-based Media

A Web Publication needs to support both time-based media and text.

A Web Publication needs to support time-based media, such as synchronized video, audio, captions or transcript, or sign language interpretation. A Web Publication must also be able to enable a synchronized media experience while navigating through the publication, with sufficient level of granularity.

  • Illyés has a cognitive disability and uses accommodated texts in the classroom, to help learn the content while improving his reading. His assistive technology uses combined audio and highlighted text, which it obtained from the UA through the information provided in the Web Publication, to turn the page for him while reading along in sync with the page currently open.
  • Marco is learning German as a second language. In order to improve his understanding and pronunciation, while reading a German text, he uses a read-aloud function available through his User Agent and made accessible by the information provided in the Web Publication.


Web Publications should be able to include data as resources, just as it does with text, images, etc.

  • Rosa has submitted an article to EsteemedJournal and provided her research data in CSV format. She and EsteemedJournal provide users access to the CSVs when accessing her article in any situation by including the CSV data, as well as the Javascript library to display the content in human friendly form, as part of the Web Publication.
  • A news organization wishes to run a series of articles containing graphs based on a set of raw data. Those graphs are generated dynamically in each article, depending on what the topic is. The data is also available to the user for transparency.
  • An exercise in an educational Web Publication requires the student to push data to a CSV and analyze the subsequent graphs that are dynamically created with each datapoint that the student enters.


Publication Identification

There must be a way to uniquely identify a Web Publication.

The unique identification of a specific Web Publication is essential. If not expressed as a URL, there should be a way to map this unique identification onto a Web Address.

  • Scholarly references demand a unique identification of the publication and, possibly, its internal structure. That unique identification must be available as a Web link, to make it possible for other publications and other sites (e.g., the authors’ institutional sites) to unambiguously link to the publication. These features are essential in the scholarly community to make, for example, the assessment of individual researchers possible.
  • Textbook editions should be clearly distinct from one another using unique identifiers. Links should be accurate in order to avoid confusion in classes, especially since each class is not necessarily using the latest edition.

User agents must treat a Web Publication as a single logical resource with its own URL, beyond the references to individual, constituent resources.

  • Marwin wants to search for a term on the publication. As a reader, he does not know the internal structure of the book, i.e., whether the content is one or several HTML files; he wants to search to be executed on the whole (logical) content, regardless of its internal representation.
  • Svetlana sets her preferences in terms of font selection and size, background color, etc, for a particular book. She wants those to be in effect on all chapters of the book automatically.
  • User agents that support value counters (page counters, section numbering, footnotes, endnotes), should do so across the entire Web Publication (as opposed to individual components being numbered separately)
  • Assistive Technology such as screen readers or voice dictation control needs to have the Web Publication presented to it as if it was a single unit.

Resource Identification

All constituent resources, and their contents, should be uniquely identifiable.

The requirement that a Web Publication be uniquely identifiable can be easily extended to the constituents of a Web Publication, as well as the fragments, parts, sections, etc, of those resources. Those idenfications should be stable, resilient to changes and new iterations of the publication.

  • Markus refers to a specific mathematical theorem in a publication. That reference must be unique, stable and retrievable on the Web, and it should not depend on whether the publisher issues a new iteration of the target publication (thereby possibly change the section numbering).
  • Judit uses an annotation tool to comment on a publication authored by Pablo. She puts an annotation against a sentence in a particular paragraph, anchoring that annotation to the sentence using a reliable way of identifying it. That identification should not be invalidated by a subsequent change of the document by Pablo (unless he, e.g., removes that sentence).


This section is under construction!


I believe the requirements related to style are addressed in 5.2 personalization, req: "The user must have the possibility to personalize his or her reading experience. This may include, for example, controlling such features as font size, choice of fonts, background and foreground color, tone of audio, etc"


For the purposes of layout, each resource of a Web Publication is treated as a separate document. User agents must not mix content from multiple resources in the same rendering (e.g., CSS floats or absolutely positioned elements from one resource cannot intrude or overlap with content from an other resource).

  • Helga is authoring an internal work document for her company as a Web Publication. This Web Publication spans several resources / documents, and she would like to use decimal-dot notation to indicate the section numbers. The CSS counter should be able to accumulate across the multiple resources to provide an accurate count. <- this is currently limited by CSS / I wonder too whether it would be complicated by the fact that the CSS would also have to interact with the manifest to determine this counter. Would this be the only reason for the CSS to interact with the manifest? Or is there another manner in which this can be accomplished in CSS without having to interact with the manifest?


User agents should provide the option to save this progression in the publication and returns the user to their last location the next time they open the publication.

  • Filbert is reading a comic as a Web Publication. In his user agent, he marks a specific page to return to and exits the user agent. When he returns the next day, he opens the Web Publication and continues reading from the location he marked.


It should be possible to see the Web Publication in a “paginated” view.

When a user agent renders a Web Publication in a paginated layout, it must lay out each document in the default reading order sequentially, with the last page of a resource being followed by the first page of the subsequent one.

Whereas a “scrolling” view is the dominating approach on the Web in browsers, a user or author may wish to view their publications in a paginated view. As such, it should be possible for an individual publication or user agent to provide the ability to switch to pagination view. This pagination may automatically adapt page sizes to the device’s or the browser’s viewport, and may contain separate headers, footers, and/or page numbers.

This is distinct from the need to retain original page numbering (often from the print edition) which must be available on demand and must be usable to discover specific locations in the publication.

For more detailed requirements on pagination, see here.

  • Ann reads War and Peace which, when printed, is over 1200 pages. In order to have a better sense of her progress in the book and to make navigation within the book easier (i.e., to support usability) she decides to switch her reading environment to paged view.
  • Susan uses a flexible CSS layout, that includes images, to create a rich, interactive publication on the history of a city. Each major historical milestone is defined as a standalone unit that would be a single page when printed, with a timeline with the main events in the footer area of the page.
  • IndyPublisher wants to provide transition effects between pages, both within and across content documents.
  • Mr. Oayia, a classroom teacher, says, “turn to page 137 of your textbook.” Regardless of layout and font size, students reading digital editions need to find the same location in the textbook as one another and as students reading the print edition.


It should be possible to create and distribute a Web Publication as a single unit over different protocols or physical media. This can done through the usage of Packaged Web Publications.

See also Archiving.


The distribution of a Packaged Web Publication should not affect its iterations.

Simply distributing or sharing a Packaged Web Publication to multiple destinations and devices should not result in (technically) different iterations of the Web Publication unless they contain modifications that make them different Web Publications.

  • Publisher Corp. Inc. publishes a new Packaged Web Publication and sends it to its distributors and customers. This Packaged Web Publication is downloaded to devices or made available to a customer-specific cloud. Customers can access this file from different retailers, through different applications, either directly or downloaded from a private cloud. Thus, the Web Publication is duplicated many times, resulting in a huge number of copies. There remains a single source manifestation, and therefore one canonical identifier for all of the items spread across devices and buyers.
  • Mary creates a Packaged Web Publication and sends it to Dave and Kristin. Kristin simply sends it along to two other friends, but Dave adds some comments first to his copy before sending to two friends. By doing so, Dave has created a new Web Publication with its own canonical identifier while the version used by Mary, Kristen and her friends remains the same as the original.
  • Slicendice Publishing publishes many Packaged Web Publications, some of which are different iterations or subsets or combinations of others. Slicendice needs not only to be able to uniquely identify each unique Web Publication but also to identify each “copy” or “delivery” (“item”) of each of those Web Publications so that it can track “what” has been sold and “how many” of each one have been sold.
  • BigRetailer receives a Web Publication from EsteemedPublisher that it intends to add to its catalogue. BigRetailer wants to adds it own “teaser” via an alternative reading order. To achieve that, BigRetailer provides its own version of the publication’s manifest, that the user agent will use instead of the publisher’s manifest.

The distribution of Packaged Web Publications should respect the existing processes and expectations of professional publishing channels as well as ad-hoc methods of distribution (eg. email).

  • Ahmed acquires a Packaged Web Publications on an e-commerce platform. He expects to be able to receive the Web Publication as a file (rather than only having access to it) and to be able to load it onto its different reading devices.
  • Alice acquires a Packaged Web Publication through a subscription service and downloads it. When, later on, she decides to unsubscribe from the service, this Web Publication becomes unavailable to her.
  • Leila has just written a report for school as a Web Publication, but she is required to email it to her teacher. She takes advantage of the fact that it is possible to package up a publication and then sends it off.


We take for granted the relative durability of print artifacts, many of which have survived with little more than benign neglect. In contrast, digital documents are unlikely to persist without more active interventions, such as making copies, monitoring software dependencies, and validating integrity. Since future consumers of publications represent the most open-ended user group, it is desirable that digital documents be instilled with more of the inherent durability that characterizes print artifacts. Packaged Web Publications offer this potential, by making it easier for archiving services to locate, harvest, update, and describe digital publications. Long-term preservation of digital publications ensures that they may continue to be accessible, beyond the tenure of individual authors, file formats, publishers, or publishing platforms.

Fundamental use cases and requirements already help aid our archiving requirements. For example:

However, archival raises an additional requirements:

There should be a way to indicate whether one or more Packaged Web Publication components contain (embedded) descriptive metadata.

An archiving service needs a reliable way to determine which, if any, Web Publication components contain descriptive metadata, such as that described in metadata and resources. Without such a mechanism, the archiving service will have to develop and maintain publisher- and/or platform-specific heuristics for locating or parsing out descriptive metadata, making archiving more expensive and decreasing the reliability of reporting.

  • An archiving service sets out to conduct an initial harvest of an article. Along with the images, markup, scripts, and style and layout instructions that constitute the object, it is able to locate a file containing descriptive metadata. The archiving service retrieves these resources and packages them into a logical archival unit for ingest into a preservation repository. A related process identifies and parses the descriptive metadata and saves its contents into an associated management database.

There should be a way to discover that one or more new components have been added to or deleted from a Web Publication.

An archiving service needs a reliable way to learn that one or more Packaged Web Publication components have been added to or removed from a Packaged Web Publication in order to be able to update the associated archive of the publication.

  • An archiving service regularly polls for changes to an article that it has already archived. One such poll indicates that several resources have been added to the object. The archiving service retrieves these resources and store them as incremental updates to the appropriate archival unit in a preservation repository.
  • A publisher issues a retraction for a published article, resulting in the addition of new resources to the object (i.e., the retraction notice) and the removal of others (i.e., the article content). An archiving service regularly polls for changes to this article, which it has already archived, and discovers the retraction. The archiving service retrieves the new resources and record those that are no longer accessible, carrying over the cumulative updates to a preservation repository.
  • A copyright dispute results in the takedown of a published book. An archiving service regularly polls for changes to this book, which it has already archived, and discovers that it has been taken down. It records that the resources that constitute the object are no longer accessible and propagates this update to a preservation repository.

For Authors

Default Reading Order

There should be a means to indicate the author’s preferred navigation structure among the resources of a Web Publication.

A user agent needs to know the sequence in which to present components of a Web Publication to the user, including the starting point.

Random Access to Content

Authors of a Web Publication should be able to provide the user agent with information to access random parts of the publication.

It should be possible for the author to convey several potential reading orders that may go beyond the “default” for the content of the publication. This alternative reading order may only includes specific parts of the publication rather than the full content of the Web Publication.

A user agent should be able to access the resources of the publication in whatever order it chooses—beyond the order provided by the publication itself.

For Publishers


The publisher should be able to provide information in a Portable Web Publication that can be used to check the origin of the publication and its authenticity.


The publisher should be able to provide information in a Portable Web Publication proving that the publication has not been tampered with during delivery.


A Web Publication should be able to express the access control and write protections of the publication.

For Readers


A Web Publication should also be available offline.

The same content of the Web Publication should be accessible offline, if circumstances so dictate, without the necessity for the user to take any particular, technical actions.


The user must have the possibility to personalize his or her reading experience. This may include, for example, controlling such features as font size, choice of fonts, background and foreground color, tone of audio, etc.


The user must have the ability to quickly browse to a corresponding pointer as identified in a physical book. A user must quickly be able to locate the position of content that is identified within a print book.

Escalating trust

User agents may provide a method for escalating trust for a specific publication. Some publications may require additional capabilities (for example, access to camera or geolocation) that a user agent might normally not enable. Today, some platform and UA vendors offer methods for otherwise untrusted local scripts to become trusted and regain API privileges, a similar ability needs to exist for publications as well.

List of Requirements

Number and reference Short description

Accessibility Requirements

Ensuring accessibillity is a strong requirement for publishers. Instead of dealing with accessibility features as separate requirements and use cases, this document provides use cases for requirements whenever appropriate. This table lists those requirements, and also the use case number(s) within that section that are related to accessibility.

Number and reference Short description Use case(s)
1, 4
2, 3