Notebook / HTML
Start with the document, not the layout
A few choices that make a page easier to read, navigate and maintain.
The button that should have been a link
A clickable card looks simple until someone tries to open it in another tab. If clicking an element takes you to another page, an ordinary link is usually the right starting point. A button makes more sense for an action, such as opening a menu or submitting a form. Styling can come afterwards.
Read the headings on their own
A useful check is to read just the headings, from top to bottom. Do they describe the page, or are they mostly phrases like “Discover more”? A heading does not need to be clever. “Delivery options” tells a reader more than “Made for your lifestyle”.
Keep the useful defaults
Native controls already have a lot of behavior: focus, keyboard input and familiar interaction patterns. Rebuilding all of that with a clickable div creates work that is easy to underestimate. There are good reasons to build custom controls, but appearance alone is rarely enough.
A small check before moving on
Try reaching every link and control using the Tab key. The order should make sense, focus should stay visible and nothing should require a mouse. This is not a complete accessibility review. It is a quick way to catch a surprisingly awkward page before spending more time on the details.