How to properly use encapsulation in Page Object pattern?

Question

Java

Tell me how to properly use encapsulation in the Page Object pattern.
I read that only methods from PageObject, such as login , addToCart , etc., should be available to the client, and it's better not to use selenium methods, such as driver.click() , in tests .
But often in tests you need access to page elements, you just need to click on them, for example, or check visibility.
If you hide all page elements in a PageObject, the encapsulation becomes absurd, and you will have to write getters for each element or methods like addToCartButtonClick() .
It seems to be correct to hide elements inside PageObject and use only methods, but in practice it is very inconvenient. How to do it right?

Answer 1

encapsulation reaches the point of absurdity, and you have to write getters for each element or methods like addToCartButtonClick().

Supporting OOP with SOLID and other DRY is not very convenient at all, but what can you do?)
Another thing is that instead addToCartButtonClickthere should be a method addProductToChartwhere the PageObject already decides what it needs: press the button, pull the slider, etc., then this can be called encapsulation and the absurdity will disappear.
If you don't need getters for each element, then make them private. Obviously, a good OOP code tries to hide as much as possible in the class, make it static and constant, and expose the user only what is necessary and sufficient to solve his problems.

Answer 2

PageObject means working with page elements in the test without calling the webdriver directly.