`, lists) or ARIA landmarks/roles where appropriate. + +### 7. Focus visible (WCAG 2.4.7) + +**Rule:** Any keyboard focusable element must have a visible focus indicator. + +**What you need to do:** +- **Manually:** Tab through the entire page and confirm every focusable element shows a clear focus ring or highlight. If you use `outline: none`, provide an alternative (e.g. `:focus-visible` styles). + +### 8. Link and button purpose (WCAG 2.4.4, 4.1.2) + +**Rule:** Links and buttons must have an accessible name that describes their purpose (avoid "click here" or "read more" without context). + +**What you need to do:** +- Run the scanner and fix any link/button text issues. +- **Manually:** With a screen reader, focus each link and button and confirm the purpose is clear from the name alone; add `aria-label` or `aria-labelledby` where needed. + +--- + +## Web: Rules that cannot be automated (manual verification only) + +These WCAG success criteria **cannot be fully automated**. The scanner does not check them; you must verify them manually. + +| WCAG | Level | Criterion | What you must verify manually | +|------|-------|------------|--------------------------------| +| **1.1.1** | A | Non-text Content | That every **meaningful** image has an **appropriate** (not just present) text alternative; that decorative images are correctly marked. | +| **1.3.3** | A | Sensory Characteristics | That instructions do **not** rely only on shape, color, size, visual location, orientation, or sound (e.g. "click the green button" is insufficient without another cue). | +| **1.4.1** | A | Use of Color | That information is **not** conveyed by color alone; that links, errors, and states have an additional cue (e.g. text, icon, underline). | +| **1.4.2** | A | Audio Control | That any auto-playing audio (>3s) can be paused/stopped or volume controlled; test with real playback. | +| **1.4.4** | AA | Resize Text | That text can be resized to 200% without loss of content or function; zoom to 200% and check. | +| **1.4.10** | AA | Reflow | That content reflows at 320px width (or 256px height for horizontal scroll) without horizontal scrolling (except where 2D layout is essential). | +| **1.4.13** | AA | Content on Hover or Focus | That content that appears on hover/focus is dismissible, hoverable (if hover-triggered), and persistent until dismissed or invalid. | +| **2.1.1** | A | Keyboard | That **all** functionality is operable via keyboard (no mouse-only actions); complete key tasks with keyboard only. | +| **2.1.2** | A | No Keyboard Trap | That focus is never trapped; you can leave every component with keyboard (e.g. Tab, Escape). | +| **2.1.4** | A | Character Key Shortcuts | That single-character shortcuts can be turned off, remapped, or are active only when the component has focus. | +| **2.2.1** | A | Timing Adjustable | That time limits can be turned off, adjusted, or extended (or fall under an exception). | +| **2.2.2** | A | Pause, Stop, Hide | That moving/blinking/auto-updating content (>5s) can be paused, stopped, or hidden. | +| **2.4.3** | A | Focus Order | That the focus order is **logical** and matches the visual order; tab through and verify. | +| **2.4.6** | AA | Headings and Labels | That headings and labels are **descriptive** and appropriate (human judgment). | +| **3.2.1** | A | On Focus | That **no** change of context occurs when a component receives focus (e.g. no auto-submit on focus). | +| **3.2.2** | A | On Input | That **no** unexpected change of context occurs when the user changes a setting (e.g. no auto-nav on selecting a dropdown option unless expected). | +| **3.3.1** | A | Error Identification | That **all** input errors are clearly identified (e.g. in text) and not only by color or icon. | +| **3.3.3** | AA | Error Suggestion | That **suggestions** for correcting errors are provided when possible. | +| **4.1.3** | AA | Status Messages | That status messages (e.g. live regions) are announced by assistive tech without moving focus; test with screen reader. | + +### Manual-only checklist — What to do (Web) + +**1.1.1 Adequacy of text alternatives** — **Manually:** With a screen reader, confirm each meaningful image is announced with a **correct and sufficient** description; fix vague or wrong alt text. + +**1.3.3 Sensory characteristics** — **Manually:** Review all instructions (forms, UI copy); ensure none rely **only** on "the green button," "the right side," "the round icon," etc. Add text or other non-sensory cues. + +**1.4.1 Use of color** — **Manually:** Identify every place information is conveyed by color (links, errors, status); add a second cue (text, icon, pattern, underline). Test in grayscale if needed. + +**1.4.2 Audio control** — **Manually:** If any audio auto-plays for more than 3 seconds, confirm a visible control pauses/stops it or controls volume; test with real playback. + +**1.4.4 Resize text** — **Manually:** Zoom the page to 200% (browser or OS); confirm no loss of content or functionality and no horizontal scrolling for body text. + +**1.4.10 Reflow** — **Manually:** Resize the viewport to 320px width (or use device toolbar); confirm content reflows and no horizontal scrolling except where 2D layout is essential (e.g. data table, map). + +**1.4.13 Content on hover or focus** — **Manually:** Trigger every tooltip/popover (hover and keyboard focus); confirm it can be dismissed without moving focus, can be hovered if hover-triggered, and stays visible until dismissed or invalid. + +**2.1.1 Keyboard** — **Manually:** Unplug the mouse; use only Tab, Shift+Tab, Enter, Space, Arrow keys, Escape. Complete every critical task (submit form, open/close modal, use menus/dropdowns). Fix any that cannot be done. + +**2.1.2 No keyboard trap** — **Manually:** Tab into modals, dialogs, custom widgets; confirm you can leave with Tab, Shift+Tab, or Escape; no focus trap. + +**2.1.4 Character key shortcuts** — **Manually:** If the page uses single-letter shortcuts, confirm they can be turned off/remapped or are only active when the relevant component has focus. + +**2.2.1 Timing adjustable** — **Manually:** If there are time limits (session, form, reading), confirm the user can turn off, extend, or adjust them (or that an exception applies). + +**2.2.2 Pause, stop, hide** — **Manually:** If content moves, blinks, or auto-updates for more than 5 seconds, confirm a control pauses, stops, or hides it. + +**2.4.3 Focus order** — **Manually:** Tab through the page; confirm focus order follows a logical reading/visual order; fix tabindex or DOM order if not. + +**2.4.6 Headings and labels** — **Manually:** Review headings and form labels; ensure they are **descriptive** and accurate (not generic or misleading). + +**3.2.1 On focus** — **Manually:** Tab to each focusable element; confirm nothing triggers a change of context (e.g. new page, submit) just from receiving focus. + +**3.2.2 On input** — **Manually:** Change form controls (dropdowns, checkboxes, etc.); confirm no **unexpected** change of context (e.g. auto-navigation) unless the user is clearly informed. + +**3.3.1 Error identification** — **Manually:** Trigger validation errors (submit invalid form); confirm each error is identified in **text** (and not only by color or icon). + +**3.3.3 Error suggestion** — **Manually:** Where validation fails, confirm **suggestions** for correction are provided when possible (e.g. "Password must be at least 8 characters"). + +**4.1.3 Status messages** — **Manually:** Trigger status messages (e.g. "Saved," "Error"); with a screen reader, confirm they are announced (e.g. via `role="status"` or live region) without moving focus. + +--- + +
+
+3. Install the ACCELQ Agent Dashboard.
+
+## Integrating 
+
+3. You need to use the external device provider for web, mobile, or both platforms. For example, if you wish to perform web browser automation, select **Use external device provider for Web**.
+
+
+
+4. Now enter your 
+
+3. Once the authentication is successful, you can select the real devices that is fetched from the