Describe the issue or problem
To comply with Title II by April 24, 2026 we need to be able to add metadata that specifies that an article is an Archive and Pre-Existing Document.
Steps I took leading up to the issue
We could manually edit each item, but this is problematic after the content is published. There are no steps that I know of to complete this task.
What application are you using?
OJS 3.3.0.19
Hi @rsauls,
Could you explain this a little further:
Is there a link to a standard or requirements that gives further details perhaps on this requirement. I’m not sure what is meant by “Archive” and “Pre-Existing document” as that could mean different things in different contexts.
-Roger
PKP Team
@rsauls , why isn’t the publication date the authoritative metadata for whether the document was published before or after the Title II enforcement deadline?
Apologies I wasn’t notified someone responded,
we are looking to add a new field if possible
Field: accessibilitySummary
Or we could place this within Description for now.
Exemption Example
Accessibility Summary:
In accordance with Title II regulations this content meets all points of exemption as Archived web content and/or Preexisting conventional electronic documents.
Compliance Example
Accessibility Summary:
This publication conforms to WCAG 2.1 Level AA.
We want to add this to all existing articles, so one at a time is not realistic.
To answer the other reply- date alone may suffice in a court proceeding, but we are having requests to mark content with accessibility statements for the users. We want our content to have the widest impact possible, and having clear accessibility compliance information is needed.
We are also working on updating the Accessibility Statement on our footer, but this is for individual articles so that when they are indexed we are making it clear if items have been exempted, remediated, or built with compliance.
Hi @rsauls,
Very interesting - thanks for sharing. I’m paging my colleague @israel.cefrin here, who does a lot of work around accessibility for him to weigh in here.
-Roger
PKP Team
Hi @rsauls , given that metadata would require to ingest data and customize a theme to display it, maybe you could break it down in two parts:
Customize the article landing page to show the accessibility summary for every published article (hard code) based on time/date.
Meanwhile, you could work in a SQL script to add the summary in the description. Later on, you could remove the hard-coded summary text from the customized article landing page theme.
A theme customization (or child theme) will create a clear “Archive” wrapper/section and displays the required labels automatically for all articles published before the 2026 deadline if you add a condition to match the time range. At the same time, it is just a workaround that will allow you to stick to the idea of adding the info to the description or even into a metadata field if you’d like to.
Hope it helps.
Israel