Richard has said that he hasn't had much experience with the Power Platform.  He made a poll last year asking members what they would like him to make content for.  A majority voted Access, and not a single vote was for Power Platform.

I trialed Power Apps for 30 days recently and built a customer CRUD form with it:  https://www.youtube.com/watch?v=Y6eOT4YjFsc  .  

If you are proficient with Access, learning Power Apps may not be too difficult.  Power Apps is a similar type of tool to Access: a front-end designer for a back-end database.  But it uses an entirely different coding language called PowerFx.  Every code is just a series of functions: F1(a,b); F2(c,d); F3(e,f,g,h), etc. -- which is mainly the reason why it is called "low code."  No SQL is used.  Every query is done with a function, similar to DLookup() in Access.

Dataverse is an online database back-end that uses proprietary, Microsoft-only data format.  I have not used it.  I use an online SQL Server database instead, which uses SQL, is more mainstream, has a free version, and can be installed locally.  Dataverse is none of those things.

I would consider the Power Platform only if online access and multi-platform usage are indispensable components for me.

Access can only create local Windows desktop applications, not online apps like Power Apps can.  To create online web apps for Access and/or SQL Server, you need to use something like Visual Studio, which is much harder to use than Access.

But the Power Platform resides entirely online.  What if you lose Internet connection?  SQL Server can be used locally, but Dataverse and the Power Platform are entirely online.  

And what if Microsoft pulls the plug on the Power Platform in the future?  When you make a mission-critical application for a business that you expect to last for years and decades, you need to think about this.