While that depends on how one defines "digital-native," I just don't think I agree.
For a start, PDF was designed as a way to digitally send documents in print-ready form with embedded fonts and, in the case of PDF/X, other prepress-specific requirements. I get it may seem like I'm using "digitally" there as a mere technicality because the indented output is still physical print, but this is a computing-era solution to a computing-era problem.
Less pedantically, though, I'm pretty sure that in 2022 a lot of PDFs are never printed, but are just viewed on-screen. They allow "print-like" typesetting and layout, but they're still being not just produced digitally but consumed digitally. Both my A/V receiver and my car have huge manuals that are delivered as PDFs, but I doubt either NAD and Honda are intending me to fire up the old laser printer to read 'em, right? (I don't think either one is even a standard printer page size.)
Furthermore, the OP specifically mentioned accessibility! Accessible PDFs are absolutely a digital-native thing, since what makes PDFs accessible includes features like document structure tags, fully searchable text, interactive form fields, navigational aids, and alternative text image descriptions.
Definitely in the tabletop RPG community, PDFs are a digital product, in that a lot of people buy PDFs to use as a digital reference tool and never print them out. I mean, there's a minor cottage industry in auto-fillable PDF character sheets!
In that situation, digital accessibility in PDFs is hugely important, even just little things like having your contents page actually link to the other pages in a document.
Oh yes, I was absolutely blown away when my gf showed me a PDF character sheet that she bought, which worked better than any of the proper apps (including the official website) made for this purpose. For all intents and purposes, it was an app - there was hierarchical content you could search through, setup wizards, automatic calculation... all implemented in PDF forms and whatever cursed scripting language Adobe inclues in Acrobat these days.
For a start, PDF was designed as a way to digitally send documents in print-ready form with embedded fonts and, in the case of PDF/X, other prepress-specific requirements. I get it may seem like I'm using "digitally" there as a mere technicality because the indented output is still physical print, but this is a computing-era solution to a computing-era problem.
Less pedantically, though, I'm pretty sure that in 2022 a lot of PDFs are never printed, but are just viewed on-screen. They allow "print-like" typesetting and layout, but they're still being not just produced digitally but consumed digitally. Both my A/V receiver and my car have huge manuals that are delivered as PDFs, but I doubt either NAD and Honda are intending me to fire up the old laser printer to read 'em, right? (I don't think either one is even a standard printer page size.)
Furthermore, the OP specifically mentioned accessibility! Accessible PDFs are absolutely a digital-native thing, since what makes PDFs accessible includes features like document structure tags, fully searchable text, interactive form fields, navigational aids, and alternative text image descriptions.