You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
The definition of API needs to be corrected (the word 'Accessibility' is used instead of 'Application'): Portable Document Format Accessibility <abbr title="Application Programming Interfaces">APIs</abbr> Mapping (PDF-AAM) Task Force
Furthermore, in the summary sentence, I'd recommend implementing the best practice of ensuring an abbreviation’s full meaning is expressed in the content immediately following a heading that contains abbr.
To solve this problem, would it be possible to make a tweak to the second sentence in the summary, as follows?:
'It assists this Working Group to map Accessibility APIs (Application Programming Interfaces) to PDFs and keep the development of PDF-AAM in sync with WAI-ARIA.'
If we can't add the expanded form of the abbreviation to the summary or find another way to provide it earlier, then instead I suggest adding the expanded form of API where it appears under the heading, 'Current work':
'As this work develops, the Editor’s Draft will be updated with the latest PDF Accessibility API (Application Programming Interface) mappings.'
Note: In the above sentence, 'Editor's Draft' still needs to be linked, as you had done originally (that link has been removed in the latest update).
72287c7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is working as expected in preview: https://deploy-preview-974--wai-website.netlify.app/about/groups/task-forces/pdf-aam/ .
Note: If you do decide to use
abbr
in theh1
, then it's no longer necessary to also use it in the summary sentence below.A couple of other things:
The definition of API needs to be corrected (the word 'Accessibility' is used instead of 'Application'):
Portable Document Format Accessibility <abbr title="Application Programming Interfaces">APIs</abbr> Mapping (PDF-AAM) Task Force
Furthermore, in the summary sentence, I'd recommend implementing the best practice of ensuring an abbreviation’s full meaning is expressed in the content immediately following a heading that contains
abbr
.To solve this problem, would it be possible to make a tweak to the second sentence in the summary, as follows?:
'It assists this Working Group to map Accessibility APIs (Application Programming Interfaces) to PDFs and keep the development of PDF-AAM in sync with WAI-ARIA.'
If we can't add the expanded form of the abbreviation to the summary or find another way to provide it earlier, then instead I suggest adding the expanded form of API where it appears under the heading, 'Current work':
'As this work develops, the Editor’s Draft will be updated with the latest PDF Accessibility API (Application Programming Interface) mappings.'
Note: In the above sentence, 'Editor's Draft' still needs to be linked, as you had done originally (that link has been removed in the latest update).