tagging code unconditionally requires some environments be defined

[mbertucci47]

If you try

\DocumentMetadata
  {
    lang=en-US,
    pdfversion=2.0,
    pdfstandard=ua-2,
    testphase={phase-III,math,title,table,firstaid}
  }
\documentclass{minimal}
\begin{document}
blub
\end{document}

you get errors

! LaTeX cmd Error: Environment 'quote' undefined.

and similarly for quotation, description, and verse. Now, I know minimal is highly discouraged, but I can imagine that some reasonable class doesn't define these environments. Should there be a check for their being defined before doing \RenewDocumentEnvironment?

[FrankMittelbach]

either a check or perhaps simply \Declare... as we intend to win in this case

[u-fischer]

In any case one should mark minimal as "non-compatible", even if it doesn't error.

[FrankMittelbach]

why is that? shouldn't minimal produce valid tagged pdfs more or less automatically? (I mean if the tagging doesn't error with verse etc not defined?

[u-fischer]

perhaps, I didn't really check what it does and if it misses something. I only think that we do not want to get test files using the class and that would happen if we classify it as "compatible".

[FrankMittelbach]

I doubt that this is becoming a serious problem. In my opinion if the minimal cls is compatible we should say so (or partially compatible with a comment that it isn't that useful, not even for a MWE).