Category: Document Accessibility

Bookmarks

Also known as: Bookmark, Favorites, Favorite

Simply put

A bookmark is a saved link to a web page, or a tag placed on content, that lets a user quickly return to it later. In a web browser, bookmarks are typically created by the user and stored so the page can be reopened without retyping its address. Some documents and applications also use bookmarks to mark specific spots, such as words, images, or other objects, for quick access.

Formal definition

In the context of the World Wide Web, a bookmark is a Uniform Resource Identifier (URI) stored for later retrieval in any of various storage formats, generally created by the user through a browser interface. More broadly, a bookmark is a feature that tags words, pictures, charts, or other objects so they can be located and viewed again. Browser implementations vary in how bookmarks are stored, organized, and accessed; for example, some access paths may require multiple navigation steps unless supplemented by additional tools or extensions. This entry describes bookmarks as a general web and computing feature and does not itself address specific accessibility conformance requirements.

Why it matters

Bookmarks are a foundational convenience of web browsing and document navigation, letting users store a link or tag a location so they can return to it without retyping an address or scrolling through content. For people who navigate the web with assistive technology, or who benefit from reduced cognitive or physical load, the ability to save and quickly return to a known page can meaningfully reduce the effort required to complete recurring tasks.

The way bookmarks are exposed matters as much as the feature itself. Access paths vary between browsers and applications, and reaching a saved bookmark can involve multiple navigation steps. For example, some browsers require several clicks to reach the bookmarks menu, and third-party extensions exist specifically to shorten that path. Additional steps can create friction for users who rely on keyboard navigation, screen readers, or switch devices, where every extra interaction adds time and complexity.

Bookmarks are a general web and computing feature rather than a defined accessibility requirement, and this entry does not establish any specific conformance obligation. Whether a particular bookmarking interface is usable by people with disabilities depends on how it is implemented in a given browser or application, and that should be evaluated through appropriate manual and assistive technology testing rather than assumed.

Who it's relevant to

UX designers and product teams

Teams designing browser features, applications, or document tools decide how many steps it takes to create and reach a bookmark. Because access paths vary and can require several navigation steps, designers should consider how efficiently keyboard and assistive technology users can save and return to content, and validate those flows through manual and assistive technology testing.

Accessibility engineers and QA testers

Bookmark interfaces should be evaluated for how they are exposed to assistive technology and how many interactions are required to use them. Since implementations differ across browsers and applications, testing the actual saved-link and tag-navigation flows is more reliable than assuming a given interface is usable.

End users who rely on efficient navigation

People who use keyboard navigation, screen readers, switch devices, or who benefit from reduced cognitive load may depend on bookmarks to return to frequently used pages or spots within content. For these users, shorter and more predictable access paths can reduce the effort of recurring tasks, and browser extensions are sometimes used to streamline reaching saved bookmarks.

Content and document authors

Authors who add bookmarks within documents to tag words, images, charts, or other objects create shortcuts that let readers jump directly to relevant spots. Thoughtful use of these markers can support easier navigation, though their effectiveness depends on how the host application presents them.

Inside Bookmarks

Bookmarks (PDF context)

Navigational links, typically presented in a side panel of a PDF viewer, that allow users to jump directly to specific sections, pages, or headings within a document. In accessible PDFs, bookmarks provide an alternative navigation mechanism that supports orientation and wayfinding for users who rely on structured access to long documents.

Bookmarks (web browser context)

User-created saved references to web pages stored within a browser, allowing a person to return to a location without re-navigating. These are a user-agent feature rather than a property of the content itself.

In-page anchors and skip links

Related mechanisms in web content, such as named anchors and 'skip to content' links, that let users move to a specific location within a page. These support the same wayfinding goal that document bookmarks address but are implemented in HTML.

Relationship to document structure

Bookmarks in a well-authored document generally mirror the underlying heading hierarchy, so their usefulness depends on the document having correctly tagged headings and a logical reading order.

Relationship to WCAG navigation criteria

Navigation aids like bookmarks relate to WCAG success criteria addressing multiple ways to locate content and clear headings and labels. These are commonly discussed under Level A and AA, but bookmarks are one method among several rather than a specific named success criterion.

Common questions

Answers to the questions practitioners most commonly ask about Bookmarks.

Are PDF bookmarks the same thing as browser bookmarks?

No. Although they share a name, they serve different purposes. Browser bookmarks (sometimes called favorites) are user-saved links to web pages stored in the browser. PDF bookmarks are navigational elements embedded within a document that link to specific locations, headings, or sections inside that PDF. When discussing accessibility, the term most often refers to the structured, in-document navigation aids found in PDFs and similar documents rather than browser favorites.

Does adding bookmarks to a document make it accessible on its own?

No. Bookmarks are one helpful navigation feature, but they do not make a document accessible by themselves. Accessibility generally depends on a combination of factors, including proper heading structure, tagged content, reading order, alternative text, and other elements. Bookmarks can complement these features but cannot substitute for them. Conformance with recognized standards typically requires manual review and assistive technology testing in addition to any single feature.

How should bookmarks be organized in a long document?

Bookmarks are commonly organized to reflect the document's logical structure, often mirroring the heading hierarchy. Nesting bookmarks to match section and subsection levels can help users understand relationships between parts of the document and locate content efficiently. Descriptive, concise labels generally make bookmarks more useful than generic or truncated text.

Should bookmark labels match the document's headings?

Aligning bookmark labels with the corresponding headings is a common practice because it provides consistency and helps users predict where a bookmark leads. Labels are generally most useful when they are meaningful out of context and accurately describe the destination they point to.

Can bookmarks be generated automatically from a document's structure?

Many authoring and PDF tools can generate bookmarks automatically from an existing heading structure, which is why establishing proper headings first is often recommended. Automatically generated bookmarks should still be reviewed, because generation depends on the underlying structure being correct and the resulting labels being clear and accurate.

How can I verify that bookmarks work as intended?

Verification generally involves opening the document and confirming that each bookmark navigates to its intended destination, that the hierarchy reflects the content structure, and that labels are descriptive. As with other accessibility features, checks that rely solely on automated tools may not capture all issues, so manual review is commonly recommended to confirm that navigation functions as expected.

Common misconceptions

Adding bookmarks to a PDF makes the document accessible.

Bookmarks are only one navigation aid. Accessibility of a PDF also depends on proper tagging, a logical reading order, alternative text, correct heading structure, and testing with assistive technology. Bookmarks alone do not satisfy these requirements, and their presence does not guarantee conformance with WCAG or compliance with any legal standard.

Browser bookmarks and document bookmarks are the same feature.

Browser bookmarks are a user-agent convenience for returning to web pages and are controlled by the individual user, while document bookmarks are authored navigation elements embedded within a file such as a PDF. They serve related wayfinding goals but are distinct in ownership, scope, and implementation.

If bookmarks exist, users can always navigate the document with assistive technology.

Bookmarks are only useful when they are exposed to assistive technology and when they correspond to an accurate, correctly tagged structure. Automated presence of bookmarks does not confirm they are usable; manual and assistive technology testing is generally needed to verify the navigation experience.

Best practices

Generate bookmarks from the document's actual heading structure so that navigation mirrors a logical, correctly tagged reading order rather than being added ad hoc.

Treat bookmarks as one of several navigation methods; also provide clear headings, descriptive labels, and where applicable skip links or in-page anchors to support multiple ways of locating content.

Verify that bookmarks are exposed to and operable with assistive technology through manual testing, since automated checks detect only a portion of accessibility issues.

Keep bookmark labels concise, descriptive, and consistent with the section titles they reference so users can predict where each link leads.

For long or complex documents, ensure the bookmark hierarchy reflects nesting levels so users can understand the document's organization at a glance.

Remember that adding bookmarks supports usability but does not by itself ensure WCAG conformance or legal compliance; consult qualified counsel and current agency guidance where legal obligations are in question.