Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DForm AccessibilityAction4 of 12 controls have issuesFIX
| Control | Type | Label | Method |
|---|---|---|---|
| #et_pb_contact_name_0 | text | Name | for/id |
| #et_pb_contact_email_0 | text | Email Address | for/id |
| #et_pb_contact_phone_0 | text | Phone Number | for/id |
| #et_pb_contact_message_0 | textarea | Message | for/id |
| #contact-form-name | text | Name | none |
| #contact-form-phone | tel | Phone | none |
| #contact-form-email | none | ||
| #contact-form-message | textarea | Message | none |
| full-name-maspik-hp | text | (Leave this field empty) | placeholder only |
| full-name-maspik-hp | text | (Leave this field empty) | placeholder only |
| #stickyelements-submit-form | submit | (none) | none |
| #g-recaptcha-response-100000 | textarea | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" name="contact-form-submit" id="stickyelements-submit-form">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
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="text" name="full-name-maspik-hp">; <input type="text" name="full-name-maspik-hp">
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 & 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
CLandmark StructureAction3 landmarksREVIEW
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
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
BIframe Accessibility2/3 iframe(s) missing title; 0 placeholder(s)REVIEW
C404 Error PageActionCould not testREVIEW
404 page quality check not available.
CColor Contrast (Screenshot)Action20 text elements analyzed, 7 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
3 contrast failures on background images/gradients
These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 ROOFING & REPAIR | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Request Info | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Welcome to Manhattan… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Reliable & Honest Wo… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 New Roof Installatio… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Roof Repairs | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Roof Maintenance Pla… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Roof & Attic Inspect… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Replacement Roofs | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Residential Re-Roofi… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Manhattan Roofing Co… | 3.29:1 | 4.5:1 | #000000 | #C20000 | Fail |
| span Call Us Now: | 3.29:1 | 4.5:1 | #000000 | #C20000 | Fail |
| a (212) 495-9840 | 3.29:1 | 4.5:1 | #000000 | #C20000 | Fail |
| a Home | 3.29:1 | 4.5:1 | #000000 | #C20000 | Fail |
| a About Us | 5.65:1 | 4.5:1 | #000000 | #85857D | Pass |
| a Services | 6.27:1 | 4.5:1 | #000000 | #8E8D80 | Pass |
| a Flat Roofs | 5.90:1 | 4.5:1 | #000000 | #898880 | Pass |
| a Roof Installation | 2.84:1 | 4.5:1 | #000000 | #555653 | Fail |
| a Roof Repair | 3.27:1 | 4.5:1 | #000000 | #605F56 | Fail |
| a Service Areas | 1.58:1 | 4.5:1 | #000000 | #30302C | 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.
BLighthouse Accessibility AuditsScore 83/100 — 4 failing, 17 passedREVIEW
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.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
SEND div.et_pb_contact > form.et_pb_contact_form > div.et_contact_bottom_container > button.et_pb_contact_submit |
These are opportunities to improve the legibility of your content.
Names and labels
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.et_pb_column > div.et_pb_module > div.et_pb_code_inner > iframe div.et_pb_column > div.et_pb_module > div.et_pb_code_inner > iframe |
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
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Source: MDN Permissions-Policy
| Failing Elements |
|---|
head > meta head > meta |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.js html.js |
These items highlight common accessibility best practices.
AHeading Hierarchy10 headingsPASS
- H1 ROOFING & REPAIR
- H2 Welcome to Manhattan Roofing
- H2 Reliable & Honest Work
- H3 New Roof Installation
- H3 Roof Repairs
- H3 Roof Maintenance Plans
- H3 Roof & Attic Inspection
- H3 Replacement Roofs
- H3 Residential Re-Roofing
- H1 Request Info duplicate H1
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
A+Heading Text Quality1 heading-text-quality issue(s) detectedPASS
A+Alt Text QualityAll 7 images OKPASS
ALink & Button Quality1 issue(s) across 35 links and 2 buttonsPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://manhattanroofs.com/about-us | Read More | generic text | Replace with descriptive text |
Before: Read More Suggested: About Us | |||
| https://royalmarketingstar.com | Royal Marketing Star® | new tab | Add '(opens in new tab)' to text |
Generic link text like 'click here' doesn't describe the destination.
https://manhattanroofs.com/about-us ("Read More")
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
Add '(opens in new tab)' to link text or aria-label.
https://royalmarketingstar.com
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP