Added ElementNotVisibleException to Error Documentation

website_and_docs/content/documentation/webdriver/troubleshooting/errors/_index.en.md

@@ -163,3 +163,18 @@ This exception occurs when the WebDriver is unable to create a new session for t
 - On macOS, go to **System Settings > Privacy & Security**, and allow the driver to run if blocked.
 - Verify the driver binary is executable (`chmod +x /path/to/driver` on Linux/macOS).
 
+## ElementNotVisibleException
+
+This exception is thrown when the element you are trying to interact with _is_ present in the DOM, but is not visible. 
+
+### Likely Cause
+
+This can occur in several situations:
+* Another element is blocking your intended element
+* The element is disabled/invisible to the user
+
+### Possible Solutions
+
+This issue cannot always be resolved on the user's end, however when it can it is usually solved by the following: 
+using an explicit wait, or interacting with the page in such a way to make the element visible 
+(scrolling, clicking a button, etc.)

website_and_docs/content/documentation/webdriver/troubleshooting/errors/_index.ja.md

@@ -157,4 +157,20 @@ This exception occurs when the WebDriver is unable to create a new session for t
 
 - Ensure the WebDriver version matches the browser version. For Chrome, check the browser version at `chrome://settings/help` and download the matching driver from [ChromeDriver Downloads](https://chromedriver.chromium.org/downloads).
 - On macOS, go to **System Settings > Privacy & Security**, and allow the driver to run if blocked.
-- Verify the driver binary is executable (`chmod +x /path/to/driver` on Linux/macOS).
+- Verify the driver binary is executable (`chmod +x /path/to/driver` on Linux/macOS).
+
+## ElementNotVisibleException
+
+This exception is thrown when the element you are trying to interact with _is_ present in the DOM, but is not visible. 
+
+### Likely Cause
+
+This can occur in several situations:
+* Another element is blocking your intended element
+* The element is disabled/invisible to the user
+
+### Possible Solutions
+
+This issue cannot always be resolved on the user's end, however when it can it is usually solved by the following: 
+using an explicit wait, or interacting with the page in such a way to make the element visible 
+(scrolling, clicking a button, etc.)

website_and_docs/content/documentation/webdriver/troubleshooting/errors/_index.pt-br.md

@@ -159,3 +159,18 @@ This exception occurs when the WebDriver is unable to create a new session for t
 - On macOS, go to **System Settings > Privacy & Security**, and allow the driver to run if blocked.
 - Verify the driver binary is executable (`chmod +x /path/to/driver` on Linux/macOS).
 
+## ElementNotVisibleException
+
+This exception is thrown when the element you are trying to interact with _is_ present in the DOM, but is not visible. 
+
+### Likely Cause
+
+This can occur in several situations:
+* Another element is blocking your intended element
+* The element is disabled/invisible to the user
+
+### Possible Solutions
+
+This issue cannot always be resolved on the user's end, however when it can it is usually solved by the following: 
+using an explicit wait, or interacting with the page in such a way to make the element visible 
+(scrolling, clicking a button, etc.)

website_and_docs/content/documentation/webdriver/troubleshooting/errors/_index.zh-cn.md

@@ -161,3 +161,19 @@ Actions class with `Actions.moveToElement(element)`.
 - 确保 WebDriver 版本与浏览器版本匹配。对于 Chrome，请在浏览器中访问 `chrome://settings/help` 检查浏览器版本，并从 [ChromeDriver 下载](https://chromedriver.chromium.org/downloads)页面下载匹配的驱动程序。
 - 在 macOS 上，转到 **系统设置 > 隐私与安全性**，并允许驱动程序运行（如果被阻止）。
 - 验证驱动程序二进制文件是否可执行（在 Linux/macOS 上运行 `chmod +x /path/to/driver`）。
+
+## ElementNotVisibleException
+
+This exception is thrown when the element you are trying to interact with _is_ present in the DOM, but is not visible. 
+
+### Likely Cause
+
+This can occur in several situations:
+* Another element is blocking your intended element
+* The element is disabled/invisible to the user
+
+### Possible Solutions
+
+This issue cannot always be resolved on the user's end, however when it can it is usually solved by the following: 
+using an explicit wait, or interacting with the page in such a way to make the element visible 
+(scrolling, clicking a button, etc.)