Use the element that matches the action
Links navigate somewhere. Buttons change something on the current page. Choosing the correct HTML element gives keyboard users and assistive technology a useful starting point before any extra behavior is added.
An icon on its own needs an accessible name. A project-opening control should identify the project, while a close button should say what it closes. Visible focus styles make these actions discoverable without a pointer.
Make state available
A filter should expose which option is selected. A collapsible section should communicate whether its content is expanded. When a dialog opens, focus should move inside it, stay within the dialog, and return to the trigger when it closes.
Established dialog primitives can handle much of this behavior. They still need a useful title, a description where appropriate, and a clear close control.
Respect a quieter experience
Movement can make an interface feel responsive, but some visitors prefer less of it. Respecting the prefers-reduced-motion setting means reducing decorative movement and avoiding unnecessary animated scrolling.
The underlying content and available actions should stay just as useful when motion is reduced. Animation adds to a good interaction; it should never be required to understand it.