Editorial: Rename PDF-Object to be named #2688
Open
+14
−15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for wai-aria ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
daniel-montalvo
requested changes
Dec 3, 2025
| <p> | ||
| This specification defines how PDF user agents (commonly referred to as “PDF processors” in ISO standards for PDF technology) respond to and expose PDF-object to be named (structure elements, | ||
| structure attributes, or property lists associated with marked content, etc., as defined in ISO 32000-2 clauses 14.7–14.9). | ||
| This specification defines how PDF user agents (commonly referred to as “PDF processors” in ISO standards for PDF technology) respond to and expose PDF Logical Structure Items (structure elements, structure attributes, or property lists associated with marked content, etc., as defined in ISO 32000-2 clauses 14.7–14.9). |
Contributor
There was a problem hiding this comment.
Suggested change
| This specification defines how PDF user agents (commonly referred to as “PDF processors” in ISO standards for PDF technology) respond to and expose PDF Logical Structure Items (structure elements, structure attributes, or property lists associated with marked content, etc., as defined in ISO 32000-2 clauses 14.7–14.9). | |
| This specification defines how PDF user agents (commonly referred to as “PDF processors” in ISO standards for PDF technology) respond to and expose <abbr title="PDF Logical Structure Items">PLSIs</abbr> (structure elements, structure attributes, or property lists associated with marked content, etc., as defined in ISO 32000-2 clauses 14.7–14.9). |
| <div> | ||
| <dl class="termlist"> | ||
| <dt><dfn data-export="">PDF-object to be named</dfn></dt> | ||
| <dt><dfn data-export="">PDF Logical Structure Item (PLSI)</dfn></dt> |
Contributor
There was a problem hiding this comment.
Suggested change
| <dt><dfn data-export="">PDF Logical Structure Item (PLSI)</dfn></dt> | |
| <dt><dfn id="dfn-plsi" data-export="">PDF Logical Structure Item (PLSI)</dfn></dt> |
| </div> | ||
| </section> | ||
|
|
||
| <section id="mapping-pdf-object-to-be-named"> |
Contributor
There was a problem hiding this comment.
Suggested change
| <section id="mapping-pdf-object-to-be-named"> | |
| <section id="mapping-plsis"> |
| <h3>General Rules for Exposing PDF Semantics via HTML or WAI-ARIA Semantics</h3> | ||
| <p> | ||
| Unless indicated otherwise, a PDF-object to be named with default Accessible Rich Internet Applications (WAI-ARIA) 1.2 semantics MUST be exposed to the platform accessibility APIs according to | ||
| Unless indicated otherwise, a PLSI with default Accessible Rich Internet Applications (WAI-ARIA) 1.2 semantics MUST be exposed to the platform accessibility APIs according to |
Contributor
There was a problem hiding this comment.
Suggested change
| Unless indicated otherwise, a PLSI with default Accessible Rich Internet Applications (WAI-ARIA) 1.2 semantics MUST be exposed to the platform accessibility APIs according to | |
| Unless indicated otherwise, a <abbr title="PDF Logical Structure Items">PLSI</abbr> with default Accessible Rich Internet Applications (WAI-ARIA) 1.2 semantics MUST be exposed to the platform accessibility APIs according to |
| Unless indicated otherwise, a PLSI with default Accessible Rich Internet Applications (WAI-ARIA) 1.2 semantics MUST be exposed to the platform accessibility APIs according to | ||
| the relevant WAI-ARIA mappings defined in the | ||
| <a href="https://www.w3.org/TR/core-aam-1.2/">Core Accessibility API Mappings 1.2</a> specification. Where a PDF-object to be named has equivalent semantics to a WAI-ARIA role, user agents | ||
| <a href="https://www.w3.org/TR/core-aam-1.2/">Core Accessibility API Mappings 1.2</a> specification. Where a PLSI has equivalent semantics to a WAI-ARIA role, user agents |
Contributor
There was a problem hiding this comment.
Suggested change
| <a href="https://www.w3.org/TR/core-aam-1.2/">Core Accessibility API Mappings 1.2</a> specification. Where a PLSI has equivalent semantics to a WAI-ARIA role, user agents | |
| [[[Core-AAM-1.2]]] specification. Where a <abbr title="PDF Logical Structure Item">PLSI</abbr> has equivalent semantics to a WAI-ARIA role, user agents |
| <h3>Exposing PDF-object to be named That Do Not Directly Map to Accessibility APIs</h3> | ||
| <p>Where a PDF-object to be named does not have any default HTML or WAI-ARIA semantics, the applicable mapping for each platform accessibility API is defined by this specification.</p> | ||
| <h3>Exposing PLSIs That Do Not Directly Map to Accessibility APIs</h3> | ||
| <p>Where a PLSI does not have any default HTML or WAI-ARIA semantics, the applicable mapping for each platform accessibility API is defined by this specification.</p> |
Contributor
There was a problem hiding this comment.
Suggested change
| <p>Where a PLSI does not have any default HTML or WAI-ARIA semantics, the applicable mapping for each platform accessibility API is defined by this specification.</p> | |
| <p>Where a <abbr title="PDF Logical Structure Items">PLSI</abbr> does not have any default HTML or WAI-ARIA semantics, the applicable mapping for each platform accessibility API is defined by this specification.</p> |
| <p>Where a PLSI does not have any default HTML or WAI-ARIA semantics, the applicable mapping for each platform accessibility API is defined by this specification.</p> | ||
|
|
||
| <h3>Exposing PDF-object to be named That Require a Minimum Role</h3> | ||
| <h3>Exposing PLSIs That Require a Minimum Role</h3> |
Contributor
There was a problem hiding this comment.
Suggested change
| <h3>Exposing PLSIs That Require a Minimum Role</h3> | |
| <h3>Exposing <abbr title="PDF Logical Structure Items">PLSIs</abbr> That Require a Minimum Role</h3> |
| <p> | ||
| A minimum role is the equivalent WAI-ARIA role a PDF-object to be named will map to if the element does not have a more specific implicit role or platform role mappings, e.g., a non-generic | ||
| role. Minimum roles help ensure that users of assistive technologies get the best possible experience for valid PDF-object to be named where otherwise a role would not be exposed. | ||
| A minimum role is the equivalent WAI-ARIA role a PLSI will map to if the element does not have a more specific implicit role or platform role mappings, e.g., a non-generic |
Contributor
There was a problem hiding this comment.
Suggested change
| A minimum role is the equivalent WAI-ARIA role a PLSI will map to if the element does not have a more specific implicit role or platform role mappings, e.g., a non-generic | |
| A minimum role is the equivalent WAI-ARIA role a <abbr title="PDF Logical Structure Item">PLSI</abbr> will map to if the element does not have a more specific implicit role or platform role mappings, e.g., a non-generic |
I'd like to hear others' input here to avoid potential confusion introduced by the concept of "minimum role", which I haven't seen in other parts of the ARIA suite.
| <h3>PDF Element Role Mappings</h3> | ||
| <p> | ||
| PDF-object to be named with implicit WAI-ARIA role semantics MUST be mapped to platform accessibility APIs according to the identified WAI-ARIA role mapping as defined in the | ||
| PLSIs with implicit WAI-ARIA role semantics MUST be mapped to platform accessibility APIs according to the identified WAI-ARIA role mapping as defined in the |
Contributor
There was a problem hiding this comment.
Suggested change
| PLSIs with implicit WAI-ARIA role semantics MUST be mapped to platform accessibility APIs according to the identified WAI-ARIA role mapping as defined in the | |
| <abbr title="PDF Logical Structure Items">PLSIs</abbr> with implicit WAI-ARIA role semantics MUST be mapped to platform accessibility APIs according to the identified WAI-ARIA role mapping as defined in the |
| </p> | ||
| <p> | ||
| Where a PDF-object to be named is indicated as having “No corresponding (WAI-ARIA) role”, or is mapped to the generic role, user agents MUST NOT expose the | ||
| Where a PLSI is indicated as having “No corresponding (WAI-ARIA) role”, or is mapped to the generic role, user agents MUST NOT expose the |
Contributor
There was a problem hiding this comment.
Suggested change
| Where a PLSI is indicated as having “No corresponding (WAI-ARIA) role”, or is mapped to the generic role, user agents MUST NOT expose the | |
| Where a <abbr title="PDF Logical Structure Item">PLSI</abbr> is indicated as having “No corresponding (WAI-ARIA) role”, or is mapped to the generic role, user agents MUST NOT expose the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes w3c/pdf-aam issue #20
Officially replaces the placeholder term with the PDF Association agreed upon term: "PDF Logical Structure Item (PLSI)"