← Back to Extension
Exploratory Tester

Exploratory Tester - Help Guide

📑 Quick Navigation

Error - Critical issue that needs fixing
Warning - Potential issue to review
Pass - Element meets best practices

📊 Understanding Test Coverage

Test Coverage shows what percentage of the 21 available test categories were executed on the page.

How is Coverage Calculated?

Coverage % = (Categories Run ÷ 21 Total Categories) × 100

100%
All 21 categories tested
76%
16 of 21 categories tested
38%
8 of 21 categories tested

Why might coverage be less than 100%?

• Disabled by user: You turned off specific test categories in settings
• Timeout: Tests stopped before completing all categories
• Manual Stop: You stopped the tests early

What does "N/A" mean?

When a test category reports N/A, it means the page doesn't have the relevant elements (e.g., no forms = form tests show N/A). N/A categories still count toward 100% coverage since the test ran and correctly determined there was nothing to check.

Note: 100% coverage means all test categories ran — it doesn't mean the page has no issues! Only visible elements are tested; hidden elements are skipped.

📸 Screenshot Capture

Screenshots are automatically captured when issues are found to help you identify and locate problems.

20 Max screenshots per test run
2 Max per error category
600ms Minimum interval between captures

Tip: Click the 🎯 icon next to any issue to highlight the element on the page!

🔤 Spelling Mistakes

Scans all visible text content on the page for common typos, misspellings, and informal abbreviations using a built-in dictionary of 200+ known errors.

🧪 Test Cases Covered:
❌
Common misspelling detected
teh → the, recieve → receive, seperate → separate, definately → definitely
⚠️
Informal abbreviation or slang found
plz → please, ur → your, govt → government, qty → quantity
⚠️
Suspicious vowel-less word (3+ chars)
Words like "bcz", "wld", "frm" that lack any vowel
✅
No spelling mistakes detected in visible text
ℹ️
Skips: script, style, code, pre, textarea, and input tags

📧 Email Field Validation

Finds email input fields (by type, name, id, or placeholder containing "email") and checks they use proper HTML5 validation.

🧪 Test Cases Covered:
❌
Email field missing type="email"
Field named "email" but uses type="text" — no browser validation
❌
Email validation not working
type="email" present but "invalid-email" passes checkValidity()
✅
Email field has type="email" and rejects invalid input
ℹ️
N/A — No email fields found or none visible on page

📱 Phone Number Validation

Finds phone input fields (by type="tel", or name/placeholder containing "phone" or "mobile") and checks they restrict alphabetic input.

🧪 Test Cases Covered:
❌
Phone field accepts alphabetic characters
Typing "abcdefg" into the phone field is accepted as valid input
✅
Phone field restricts input to numbers only
ℹ️
N/A — No phone fields found or none visible on page

⌨️ Input Fields Status

Checks all visible input, select, and textarea elements for disabled or read-only state that might prevent user interaction.

🧪 Test Cases Covered:
⚠️
Input is disabled
User cannot interact with this field (reports up to 10 individually)
⚠️
Input is read-only
User can see but cannot edit this field (reports up to 10 individually)
✅
All visible inputs are enabled and editable
ℹ️
N/A — No input fields found or none visible on page

⚠️ Required Fields

Tests all fields with the "required" attribute inside visible forms to verify they reject empty submissions via browser validation.

🧪 Test Cases Covered:
❌
Required field accepts empty value
Field has "required" but passes checkValidity() when empty
✅
Required field correctly rejects empty value
ℹ️
N/A — No forms, no required fields, or none visible on page

🔢 Number Field Validation

Finds numeric input fields (by type="number" or name containing "amount", "quantity", "price") and verifies they reject text input.

🧪 Test Cases Covered:
❌
Number field accepts text input
Field named "amount" or "price" accepts "abc123" as valid input
✅
Number field has type="number" or properly restricts text
ℹ️
N/A — No number fields found or none visible on page

🔐 Password Fields

Checks visible password fields for minimum length requirements and HTTPS security.

🧪 Test Cases Covered:
❌
Password allows short passwords
minLength attribute is missing or less than 6 characters
❌
Password on non-HTTPS page
Password field found on http:// page — data sent insecurely
✅
Password requires 6+ characters and page uses HTTPS
ℹ️
N/A — No password fields found or none visible on page

🔘 Button Functionality

Checks all visible buttons (button, input[type="submit"], input[type="button"], [role="button"]) for accessible labels and disabled state.

🧪 Test Cases Covered:
❌
Button has no text or label
No textContent, value, or aria-label — inaccessible (reports up to 10)
⚠️
Button is disabled
Button exists but user cannot click it
✅
Clickable buttons found with proper labels
ℹ️
N/A — No buttons found or none visible on page

📝 Form Submission

Checks each visible <form> on the page for the presence of a submit button. Hidden forms (e.g., internal widgets) are skipped.

🧪 Test Cases Covered:
❌
Form has no submit button
No button[type="submit"], input[type="submit"], or untyped button found
⚠️
Form submit button is disabled
Submit button exists but user cannot click it
✅
Form has a working submit button
ℹ️
N/A — No forms found or none visible on page

☑️ Checkboxes & Radio Buttons

Checks all visible checkboxes and radio buttons for associated labels — either via label[for="id"] or a wrapping <label> element.

🧪 Test Cases Covered:
❌
Checkbox or radio button has no label
No label[for] match and not wrapped in <label> — inaccessible (up to 10)
✅
All visible checkboxes/radio buttons have associated labels
ℹ️
N/A — No checkboxes or radio buttons found, or none visible on page

📅 Date Fields

Finds date input fields (by type="date" or name/placeholder containing "date") and checks they use proper date pickers or reject invalid dates.

🧪 Test Cases Covered:
❌
Date field accepts invalid dates
Text field accepts "99/99/9999" as valid date input
✅
Date field uses type="date" or type="datetime-local" picker
ℹ️
N/A — No date fields found or none visible on page

📄 Text Areas

Checks visible, enabled <textarea> elements for character length limits (maxLength attribute).

🧪 Test Cases Covered:
⚠️
Text area has no character limit
No maxLength attribute — user can enter unlimited text
✅
Text area has maxLength character limit set
ℹ️
N/A — No text areas found or none visible on page

🖼️ Images

Checks all visible <img> elements for broken/failed loading. Skips data URLs, blob URLs, and SVGs. Uses naturalWidth/naturalHeight and CSS sizing to detect broken images.

🧪 Test Cases Covered:
❌
Image failed to load (broken image)
Image completed but has no natural or CSS dimensions (reports up to 10)
✅
All visible images loaded successfully
ℹ️
N/A — No images found or none visible on page

💬 Input Placeholders

Checks visible text, email, and tel inputs plus textareas for having either a placeholder, a label, or an aria-label so users know what to enter.

🧪 Test Cases Covered:
⚠️
Input has no placeholder, label, or aria-label
User has no indication of what to enter in the field (reports up to 10)
✅
All visible inputs have placeholders or labels
ℹ️
N/A — No text inputs found or none visible on page

❌ Error Messages

Scans the page for visible error message elements (elements with class "error", "error-message", "alert-danger", or role="alert") that indicate something went wrong.

🧪 Test Cases Covered:
❌
Visible error message on page
Shows first 50 characters of each error text found (reports up to 10)
✅
No error messages visible on page

⏱️ Page Loading

Checks for loading indicators (spinners, loaders) that are still visible, suggesting the page hasn't finished loading content.

🧪 Test Cases Covered:
⚠️
Loading indicators still visible
Elements with class "loading", "spinner", or "loader" are visible
✅
Page fully loaded — no loading indicators visible

🌐 API/Network Failures

Monitors XHR and Fetch API calls made by the page. Detects failed requests (HTTP 4xx/5xx, network errors) and slow requests taking over 3 seconds.

🧪 Test Cases Covered:
❌
API call failed
GET HTTP 404: /api/users or POST Network Error: /api/data (up to 5)
⚠️
Slow API request (>3 seconds)
GET took 5.2s: /api/large-dataset (reports up to 3)
✅
All API calls successful / No API calls detected

📦 Resource Loading

Uses the Performance API and DOM inspection to detect failed resource loads (broken images, failed stylesheets) and slow resources taking over 5 seconds.

🧪 Test Cases Covered:
❌
Image resource failed to load
img.complete is false or img.naturalHeight is 0 (reports up to 5)
❌
CSS stylesheet failed to load
<link rel="stylesheet"> has null sheet property
⚠️
Slow resource loading (>5 seconds)
Resource took too long per Performance API (reports up to 3)
✅
All resources loaded successfully

🔍 SEO Meta Tags

Comprehensive check of 10 SEO elements: title tag, meta description, keywords, canonical URL, hreflang, Open Graph tags, viewport, robots directives, H1 tag, and HTML lang attribute.

🧪 Test Cases Covered:
❌
Missing or empty <title> tag
Page has no title — critical for search engine indexing
❌
Missing meta description
No <meta name="description"> — affects search result snippets
❌
Missing viewport meta tag
No <meta name="viewport"> — critical for mobile SEO
❌
No <h1> tag or empty <h1>
Page is missing its primary heading — important for SEO
❌
Invalid canonical URL
<link rel="canonical"> has malformed href value
⚠️
Title or meta description length issues
Title: recommended 10-60 chars | Description: recommended 50-160 chars
⚠️
Missing or incomplete Open Graph tags
Missing og:title, og:description, og:image, or og:url for social sharing
⚠️
Page set to noindex or nofollow
<meta name="robots" content="noindex"> blocks search indexing
⚠️
Multiple <h1> tags or missing HTML lang attribute
Recommended: exactly 1 H1 and lang attribute on <html> tag
⚠️
Too many meta keywords or missing canonical URL
Recommended: ≤10 keywords | Canonical URL helps avoid duplicate content
✅
SEO element properly configured
Title, description, canonical, viewport, H1, OG tags, lang present and valid

♿ Accessibility (WCAG 2.1 AA)

Audits the page for WCAG 2.1 AA compliance across 18 checks — covering page structure, keyboard navigation, ARIA correctness, images, forms, media, focus visibility, color contrast, and more. Helps catch issues before users with disabilities encounter them.

🧪 Test Cases Covered:
❌
Missing lang attribute on <html>
Screen readers need lang="en" (or appropriate language code) to select the correct voice engine — WCAG 3.1.1
❌
Missing <title> tag
Every page must have a descriptive title so users can identify the tab — WCAG 2.4.2
❌
No <main> landmark
Screen reader users rely on landmarks to navigate quickly; <main> is required — WCAG 1.3.6
❌
Multiple <main> landmarks
Only one <main> element is allowed per page — WCAG 1.3.1
❌
No <h1> heading
Every page must have exactly one H1 as its primary heading — WCAG 1.3.1
❌
Image missing alt attribute
All <img> elements must have an alt attribute (empty alt="" is valid for decorative images) — WCAG 1.1.1
❌
Form input has no accessible label
Every visible input, select, and textarea must be associated with a <label>, aria-label, or aria-labelledby — WCAG 1.3.1, 3.3.2
❌
Button has no accessible name
Buttons without visible text, aria-label, or value are invisible to screen readers — WCAG 4.1.2
❌
Link has no accessible text
Links without text content or aria-label cannot be understood by screen reader users — WCAG 2.4.4
❌
Broken ARIA reference (aria-labelledby / aria-describedby / aria-controls)
ID referenced in ARIA attribute does not exist in the DOM — silently breaks screen reader associations — WCAG 4.1.2
❌
Data table has no <th> header cells
Tables without headers leave screen reader users unable to understand column/row relationships — WCAG 1.3.1
❌
Video autoplays with sound
Autoplay with audio is disorienting for screen reader users and those with cognitive/vestibular conditions — WCAG 1.4.2
❌
Audio element autoplays
Auto-playing audio must be stoppable within 3 seconds — WCAG 1.4.2
❌
:focus outline removed in CSS without alternative
CSS rule sets outline:none on :focus with no replacement (box-shadow / border) — keyboard users cannot see focused element — WCAG 2.4.7
❌
Duplicate element IDs
Duplicate IDs break ARIA label associations and invalidate HTML — WCAG 4.1.1
⚠️
No skip navigation link
Keyboard users must tab through the entire header on every page without a "Skip to main content" link — WCAG 2.4.1
⚠️
No <nav> landmark
Wrapping navigation in <nav> lets screen reader users jump directly to it
⚠️
Multiple <h1> tags
More than one H1 on a page confuses the document outline for assistive technology users
⚠️
Heading levels skipped (e.g. H2 → H4)
Heading levels must be sequential — skipping levels breaks the document outline for screen readers — WCAG 1.3.1
⚠️
Alt text is a filename or generic label
Alt text like "image1.png" or "photo" is meaningless to screen reader users — use descriptive text — WCAG 1.1.1
⚠️
Alt text exceeds 150 characters
Very long alt text is disruptive for screen reader users — keep descriptions concise
⚠️
tabindex > 0 found
Positive tabindex values override the natural DOM tab order and create unpredictable keyboard navigation — WCAG 2.4.3
⚠️
Focusable element with tabindex="-1"
A visible interactive element (button, link, input) removed from tab order may be unreachable by keyboard — WCAG 2.4.3
⚠️
Vague link text ("click here", "read more", "here")
Screen reader users often navigate by listing all links — generic text gives no context about the destination — WCAG 2.4.4
⚠️
<div> or <span> with onclick but no ARIA role
Non-semantic elements acting as buttons must have role="button" and keyboard event handlers — WCAG 4.1.2
⚠️
Table has no caption or aria-label
Tables need a caption or aria-label describing their purpose so screen reader users know what the data represents — WCAG 1.3.1
⚠️
Video autoplays muted — no user control
Muted autoplay is permitted but users should still be able to pause or stop it — WCAG 2.2.2
⚠️
Video has no captions track
Add <track kind="captions"> so deaf or hard-of-hearing users can follow video content — WCAG 1.2.2
⚠️
Possible low-contrast inline color style
Inline color values like #ccc or #999 on a white background may not meet the 4.5:1 contrast ratio requirement — WCAG 1.4.3
⚠️
Animations present but no prefers-reduced-motion rule
Users with vestibular disorders can be harmed by motion — add @media (prefers-reduced-motion) to reduce or disable animations — WCAG 2.3.3
⚠️
Input type="text" collecting email, phone, or URL
Using type="email", type="tel", or type="url" gives mobile users the correct keyboard and enables browser-native validation
✅
Accessibility check passed
Page language set, landmarks present, headings sequential, all images labelled, all inputs labelled, ARIA refs valid, focus indicators intact, no duplicate IDs, reduced motion supported

Exploratory Tester v1.4.8 | 📺 Video Tutorial