Selenium: ElementClickInterceptedException: element click intercepted

Selenium found the element and it is displayed, but when the driver checked the exact point it was about to click, a different element was on top. A real user clicking there would hit that other element, so the driver refuses. The message names both: the element you wanted, the coordinates, and the element that would receive the click.

That last part is the key to the fix. It is usually an overlay: a cookie banner, a modal backdrop, a loading spinner, a sticky header or footer, or a chat widget. Sometimes it is a child or label of your target positioned over it, which is common with custom-styled checkboxes and radio buttons.

What is not wrong: the locator and the element's visibility. If the element were missing or hidden you would see NoSuchElementException or ElementNotInteractableException instead.

from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC

wait = WebDriverWait(driver, 10)
wait.until(EC.invisibility_of_element_located((By.CSS_SELECTOR, ".loading-overlay")))
button = wait.until(EC.element_to_be_clickable((By.ID, "submit")))
driver.execute_script("arguments[0].scrollIntoView({block: 'center'});", button)
button.click()

Handle consent banners once at the start of every session. After each action that triggers a request, wait for the app's loading indicator to vanish before the next click. Use a consistent window size so layouts, and therefore overlaps, are reproducible between local and CI runs.