Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FFavicon & BrandingAction1 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BLandmark Structure12 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
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.
Learn more ▾ ▴
Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.
Source: WCAG 2.1 SC 2.4.1
BHeading Hierarchy2 headingsREVIEW
- H2 Recent Posts
- H2 (empty)
Every page should have one H1 that describes the page content.
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Learn more ▾ ▴
The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.
Source: WCAG 2.4.6 / Google Search Central
Empty headings appear in the document outline but provide no information.
Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.
Source: WCAG 2.4.6
BLink & Button Quality2 issue(s) across 22 links and 2 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://machineresponse.com/ | (empty) | empty | Add link text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
Links without text are announced as raw URLs by screen readers.
https://machineresponse.com/
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Icon-only buttons need an aria-label so screen readers can announce them.
button.search-submit (#78 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
A+Heading Text QualityAll 2 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityAll 1 images OKPASS
AForm Accessibility1 of 1 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #search-field | search | (Search …) | placeholder only |
Placeholder text disappears on focus and is not a reliable label.
<input type="search" name="s" id="search-field">
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
A+Form Input Types1 form control(s) checked, no type mismatchesPASS
A+Form Input Quality1 form control(s) checked, no input-semantic issuesPASS
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
A+Document LanguageLang attribute set to "en-GB"PASS
A+Tabindex Anti-PatternsNo explicit tabindex attributes foundPASS
A+Iframe AccessibilityNo iframes on this pagePASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+Mobile-Readable Font SizesAll 32 visible text node(s) render at >= 12 CSS pixelsPASS
A404 Error PageHTTP 404, custom pagePASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
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 |
|---|---|---|---|---|---|
| h2 Recent Posts | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Home - Machine Respo… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Skip to content | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span MENU | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Search | 20.47:1 | 4.5:1 | #000000 | #FCFCFC | Pass |
| span Search for: | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Refrigerator | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span link to How To Cook … | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a How To Cook Artichok… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p How To Cook Artichok… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a View Post | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Are Paper Bowls Micr… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p Are paper bowls micr… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a View Post | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Can You Microwave A … | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p Can You Microwave A … | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a View Post | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span link to How I Make P… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a How I Make Pizza In … | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p See How I Make Pizza… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
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+Lighthouse Accessibility AuditsScore 96/100 — 1 failing, 25 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
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
header#masthead > div.inner-wrap > div.site-branding > a.custom-logo-link header#masthead > div.inner-wrap > div.site-branding > a.custom-logo-link |
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.