Skip to content
https://nar.realtor

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
3
REVIEW
7
PASS
3
INFO
0
Checks
13
3 PASS 7 REVIEW 3 FIX
D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header MAIN CONTENTINFO footer

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

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

B
Heading Hierarchy
17 headings
REVIEW
17 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 1,200
  • H3 117 Years
  • H3 200,000+
  • H3 5,000+
  • H3 Building Unity in the Fight Against Hunger
  • H3 Tempering a Community's Trauma
  • H3 Feeding Hearts and Bellies in New Jersey
  • H3 Empowering Hope by Transforming Kids’ Lives
  • H3 The Power of Good(s)
  • H3 Family Homes Are the Family Business
  • H3 Fighting Breast Cancer Together
  • H3 Changing Lives With Hope
  • H3 Seeing Beyond Their Horizons
  • H3 Bridge to a Purpose-filled Life
  • H3 Turning Teens Into Champions
  • H3 From Hunger to Happiness
  • H2 Stay Current on Emerging Market Trends & News

Every page should have one H1 that describes the page content.

Why this matters

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

C
Form Accessibility
Action
4 of 4 controls have issues
REVIEW
4 of 4 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="keywords">; <input type="search" name="keywords">; <input type="text" name="email">
4 controls
0 labeled
3 placeholder only
1 unlabeled
ControlTypeLabelMethod
keywordssearch(Search)placeholder only
keywordssearch(Search)placeholder only
emailtext(Email Address)placeholder only
inputsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit">

Why this matters

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="keywords">; <input type="search" name="keywords">; <input type="text" name="email">

Why this matters

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

B
Favicon & Branding
8 icon(s) detected
REVIEW
8 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

3 pass 17 fail WCAG AA 1 pass AA only
h2 Stay Current on Emerging Market Trends &…
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Building Unity in the Fight Against Hung…
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Tempering a Community's Trauma
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Feeding Hearts and Bellies in New Jersey
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Empowering Hope by Transforming Kids’ …
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The Power of Good(s)
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Family Homes Are the Family Business
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Fighting Breast Cancer Together
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Changing Lives With Hope
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Seeing Beyond Their Horizons
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bridge to a Purpose-filled Life
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Turning Teens Into Champions
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
19px · bottom of viewport
h3 From Hunger to Happiness
1.10:1
#000000
on
#120F09
needs 3.0:1 (large text)
19px · bottom of viewport
span Main menu
3.38:1
#000000
on
#785B43
needs 4.5:1 (normal text)
16px · top of page (header area)
span Close menu
3.99:1
#000000
on
#84664F
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a REALTOR® Store
4.05:1
#000000
on
#88664D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Contact
4.49:1
#000000
on
#926C52
needs 4.5:1 (normal text)
16px · above the fold

2 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)
ElementRatioRequiredFGBGResult
h2 Stay Current on Emer…1.10:13.0:1
#000000
#120F09
Fail
h3 Building Unity in th…1.10:13.0:1
#000000
#120F09
Fail
h3 Tempering a Communit…1.10:13.0:1
#000000
#120F09
Fail
h3 Feeding Hearts and B…1.10:13.0:1
#000000
#120F09
Fail
h3 Empowering Hope by T…1.10:13.0:1
#000000
#120F09
Fail
h3 The Power of Good(s)1.10:13.0:1
#000000
#120F09
Fail
h3 Family Homes Are the…1.10:13.0:1
#000000
#120F09
Fail
h3 Fighting Breast Canc…1.10:13.0:1
#000000
#120F09
Fail
h3 Changing Lives With …1.10:13.0:1
#000000
#120F09
Fail
h3 Seeing Beyond Their …1.10:13.0:1
#000000
#120F09
Fail
h3 Bridge to a Purpose-…1.10:13.0:1
#000000
#120F09
Fail
h3 Turning Teens Into C…1.10:13.0:1
#000000
#120F09
Fail
h3 From Hunger to Happi…1.10:13.0:1
#000000
#120F09
Fail
title National Association…21.00:14.5:1
#000000
#FFFFFF
Pass
div Enable accessibility21.00:14.5:1
#000000
#FFFFFF
Pass
span Main menu3.38:14.5:1
#000000
#785B43
Fail
span Close menu3.99:14.5:1
#000000
#84664F
Fail
a REALTOR® Store4.05:14.5:1
#000000
#88664D
Fail
a Contact4.49:14.5:1
#000000
#926C52
Fail
a Pay Dues4.73:14.5:1
#000000
#957057
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 5 failing, 23 passed
REVIEW
80

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.region-header > div.region-utility > div#block-nar-search-site-search > button#toggle-global-search div.region-header > div.region-utility > div#block-nar-search-site-search > button#toggle-global-search
div#mastheadAdInspectorRef > header.header > div.region-header > button#mobile-menu-btn div#mastheadAdInspectorRef > header.header > div.region-header > button#mobile-menu-btn

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mm-page > div#mastheadAdInspectorRef > div#_10y > img div.mm-page > div#mastheadAdInspectorRef > div#_10y > img

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mm-page > div#mastheadAdInspectorRef > div#_10y > a div.mm-page > div#mastheadAdInspectorRef > div#_10y > a

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Explore Benefits div.field > div.field-items > div.field-item > a
MEMBERSHIP div.group-section-region-second > div.field > div.field-items > div.field-item
Know the Numbers div.field > div.field-items > div.field-item > a
Know the Issues div.field > div.field-items > div.field-item > a

These are opportunities to improve the legibility of your content.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
× div#mastheadAdInspectorRef > div#_10y > div > a

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Input buttons have discernible text.
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Alt Text Quality
All 126 images OK
PASS
All 126 images OK
Info::
52 decorative image(s) correctly marked
Info::
74 image(s) with good alt text
126 images 74 good alt text 52 decorative
All images have appropriate alt text.
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404: Not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: NAR
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name NAR ✓192×192 icon ✓512×512 icon ✓Start URL https://www.nar.realtor ✓Display Mode standalone ✓
Name NAR Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback