Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DForm AccessibilityAction4 of 4 controls have issuesFIX
| Control | Type | Label | Method |
|---|---|---|---|
| q | search | (Site Search) | placeholder only |
| q | search | (Site Search) | placeholder only |
| email-button | Submit | (none) | none |
| Text | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="Text" name="email">; <input type="Submit" name="email-button">
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Source: WCAG 2.1 SC 3.3.2
Placeholder text disappears on focus and is not a reliable label.
<input type="search" name="q">; <input type="search" name="q">
Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.
Learn more ▾ ▴
Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).
Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman
FFavicon & BrandingAction2 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BLandmark Structure5 landmarksREVIEW
Multiple navigations need aria-label to distinguish them for screen readers.
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.
Learn more ▾ ▴
WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.
Source: WCAG 2.1 SC 2.4.1
CLink & Button QualityAction3 issue(s) across 119 links and 3 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| #menu | Open menu | img no alt | Add alt attribute to the image |
| # | Close menu | img no alt | Add alt attribute to the image |
| /docs.html | here | generic text | Replace with descriptive text |
Before: here Suggested: Docs.Html | |||
| https://twitter.com/nmap | Visit us on Twitter | img no alt | Add alt attribute to the image |
| https://facebook.com/nmap | Visit us on Facebook | img no alt | Add alt attribute to the image |
| https://github.com/nmap/ | Visit us on Github | img no alt | Add alt attribute to the image |
| https://reddit.com/r/nmap/ | Discuss Nmap on Reddit | img no alt | Add alt attribute to the image |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
Generic link text like 'click here' doesn't describe the destination.
/docs.html ("here")
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.
a[href="https://twitter.com/nmap"]; a[href="https://facebook.com/nmap"]; a[href="https://github.com/nmap/"]; a[href="https://reddit.com/r/nmap/"]
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
Source: WCAG 2.1 SC 2.4.4
Icon-only buttons need an aria-label so screen readers can announce them.
button.nst-search-button (#44 on page); button.nst-search-button (#206 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
CColor Contrast (Screenshot)Action20 text elements analyzed, 20 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Nmap: Discover your … | 1.24:1 | 3.0:1 | #000000 | #2A0D45 | Fail |
| h2 News | 1.24:1 | 3.0:1 | #000000 | #2A0D45 | Fail |
| h2 Communication | 1.24:1 | 3.0:1 | #000000 | #2A0D45 | Fail |
| title Nmap: the Network Ma… | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Nmap.org | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Npcap.com | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Seclists.org | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Sectools.org | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Insecure.org | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Download | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Reference Guide | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Book | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Docs | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Zenmap GUI | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a In the Movies | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Get Nmap 7.99 here | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| li Nmap.org has been re… | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Npcap.com | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Seclists.org | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
| a Insecure.org | 1.24:1 | 4.5:1 | #000000 | #2A0D45 | Fail |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
A+Heading Hierarchy8 headingsPASS
- H2 News
- H1 Nmap: Discover your network
- H2 Communication
- H2 Nmap Security Scanner
- H2 Npcap packet capture
- H2 Security Lists
- H2 Security Tools
- H2 About
A+Alt Text QualityAll 9 images OKPASS
A404 Error PageHTTP 404, custom pagePASS
ALighthouse Accessibility AuditsScore 90/100 — 2 failing, 21 passedPASS
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Names and labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
main#nst-content > form > p.center > input main#nst-content > form > p.center > input |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Best practices
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
main#nst-content > form > p.center > input main#nst-content > form > p.center > input |
main#nst-content > form > p.center > input main#nst-content > form > p.center > input |
These items highlight common accessibility best practices.