Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Grouping Accessibility Metadata] accessibilityFeature = bookmarks? #149

Closed
gregoriopellegrino opened this issue Jan 31, 2023 · 7 comments
Closed

Comments

@gregoriopellegrino
Copy link
Collaborator

This issue is part of the wider work presented in the issue #144 Proposal for Grouping Accessibility Metadata into Categories.

Working on a system for grouping accessibility metadata into distinct categories the editors had this question that we repost in this issue so that it can be discussed by the community.

The question is about metadata accessibilityFeature = bookmarks: is the bookmarks feature related to the publication or the reading device? Is this related to PDFs?

@clapierre
Copy link
Collaborator

Sounds like this was related to PDF's, and I say for one let's move this out as this is specific to the Reading Device. Now should we have a category for related metadata for "Reading Systems"?

@madeleinerothberg
Copy link
Collaborator

This feature was included in Schema.org for describing reading systems, not books. In the crosswalk this is noted as:

N/A (Reading system feature)

I think that means it should not appear in the guide to presenting metadata about books.

@MiiaKirsi
Copy link

I agree about leaving this out (or have a separate category for reading systems). Otherwise it could be confusing, as it's generally instructed that (accessible) PDFs should have bookmarks in them to help with navigation. Bookmarks provided by the PDF creator and bookmarks user can set up within a reading system are also two different things.

@rickj
Copy link
Collaborator

rickj commented Feb 7, 2023

Per http://kb.daisy.org/publishing/docs/metadata/schema.org/accessibilityFeature.html this is NOT the "bookmark this page in my reading system" but rather references navigation in PDF's.

Given the above, this is related to the publication and should be grouped with other navigation items.

@madeleinerothberg
Copy link
Collaborator

Rick, thanks for sharing that document. That is a different definition than given on the W3C vocabulary page:

https://www.w3.org/2021/a11y-discov-vocab/latest/#bookmarks:
4.2.1.3 bookmarks (deprecated)
The work includes bookmarks to facilitate navigation to key points.

NOTE
The use of the bookmarks value is now deprecated due to its ambiguity. For PDF bookmarks, the tableOfContents value should be used instead. For bookmarks in ebooks, the annotations value can be used.

We may need a new issue/task to get those two sources of information in sync.

@rickj
Copy link
Collaborator

rickj commented Feb 8, 2023

I don't see those definitions in conflict. They both reference navigation in a PDF using the standard terms from that document type. It's hard to deprecate a term that is canonical in Adobe's ecosystem https://www.adobe.com/acrobat/hub/how-to/learn-to-add-bookmarks-to-a-pdf

@gregoriopellegrino
Copy link
Collaborator Author

As decided in the February 9 call I moved accessibilityFeature = bookmarks to a section called Out of scope (relative to reading solutions).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants