Skip to content
https://avma.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Heading Hierarchy
Action
52 headings, 3 skip(s)
FIX
52 headings, 3 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Our website uses cookies and similar technologies to improve your experience.
  • H2 Header Menu
  • H2 Membership Column 1
  • H2 Directories
  • H2 Communities
  • H2 Get Involved
  • H2 New Members
  • H2 Advocacy - Column 1
  • H2 Take Action
  • H2 Top Priorities
  • H2 Education/Career - Column 1
  • H2 Accreditation & certification
  • H2 Education
  • H2 Continuing education (CE)
  • H2 Leadership development
  • H2 Jobs
  • H2 Resources & Tools Column 1
  • H2 Journals & research
  • H2 Public resources
  • H2 Featured events
  • H2 Calendar of events
  • H2 Featured events
  • H2 Featured news
  • H2 Publications
  • H2 Media relations
  • H2 Follow us
  • H2 AVMA Information
  • H2 AVMA Family
  • H2 Organization
  • H2 Contact
  • H2 Together for animal health
  • H4 Building a strong profession together skipped
  • H3 Veterinary technicians oppose midlevel role
  • H3 Tips to address vaccine hesitancy
  • H3 Preventing workplace injuries
  • H3 Tracking and combating New World screwworm
  • H3 National Dog Bite Prevention Week
  • H5 April 12-18 skipped
  • H3 Combating avian influenza
  • H3 Become a mentor—Get a mentor
  • H3 Explore the Journey for Teams
  • H3 Upcoming events
  • H2 AVMA Career Center
  • H5 FEATURED CE skipped
  • H3 Caring for poultry
  • H2 AVMA News
  • H3 FDA grants emergency use authorization for spray to prevent, treat screwworm
  • H2 AVMA@Work blog
  • H3 Chart of the month: Work hours near pre-pandemic levels
  • H2 Footer: AVMA Family
  • H2 Footer menu
  • H2 Social Media

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
2 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

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.

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
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 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" id="edit-submit-acquia-search">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search">
Info::
1 control(s) properly labeled
3 controls
1 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#edit-searchtextSite searchfor/id
searchtext(Search AVMA.org)placeholder only
#edit-submit-acquia-searchsubmit(none)none

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

<input type="submit" id="edit-submit-acquia-search">

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="text" name="search">

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
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title multiple-users-1 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: AVMA.org
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name AVMA.org ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name AVMA.org Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h2 Header Menu
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Membership Column 1
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Directories
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Communities
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get Involved
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 New Members
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Advocacy - Column 1
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Take Action
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Top Priorities
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Education/Career - Column 1
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Accreditation & certification
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Education
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Continuing education (CE)
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Leadership development
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Jobs
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resources & Tools Column 1
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Journals & research
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Public resources
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured events
1.58:1
#000000
on
#00305E
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Our website uses coo…19.95:13.0:1
#000000
#F9F9F9
Pass
h2 Header Menu1.58:13.0:1
#000000
#00305E
Fail
h2 Membership Column 11.58:13.0:1
#000000
#00305E
Fail
h2 Directories1.58:13.0:1
#000000
#00305E
Fail
h2 Communities1.58:13.0:1
#000000
#00305E
Fail
h2 Get Involved1.58:13.0:1
#000000
#00305E
Fail
h2 New Members1.58:13.0:1
#000000
#00305E
Fail
h2 Advocacy - Column 11.58:13.0:1
#000000
#00305E
Fail
h2 Take Action1.58:13.0:1
#000000
#00305E
Fail
h2 Top Priorities1.58:13.0:1
#000000
#00305E
Fail
h2 Education/Career - C…1.58:13.0:1
#000000
#00305E
Fail
h2 Accreditation & cert…1.58:13.0:1
#000000
#00305E
Fail
h2 Education1.58:13.0:1
#000000
#00305E
Fail
h2 Continuing education…1.58:13.0:1
#000000
#00305E
Fail
h2 Leadership developme…1.58:13.0:1
#000000
#00305E
Fail
h2 Jobs1.58:13.0:1
#000000
#00305E
Fail
h2 Resources & Tools Co…1.58:13.0:1
#000000
#00305E
Fail
h2 Journals & research1.58:13.0:1
#000000
#00305E
Fail
h2 Public resources1.58:13.0:1
#000000
#00305E
Fail
h2 Featured events1.58:13.0:1
#000000
#00305E
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+
Alt Text Quality
All 14 images OK
PASS
All 14 images OK
Info::
14 image(s) with good alt text
14 images 14 good alt text
All images have appropriate alt text.
A
Favicon & Branding
8 icon(s) detected
PASS
8 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 25 passed
PASS
95

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Join / Renew div.field > p > a.link > span.text-teal-a11y
National Dog Bite Prevention Week® p > a > span.text-teal > strong.text-weight-medium
Comments due: CVTEA educational standards p > a > span.text-teal > strong.text-weight-medium
Biomedical Research Awareness Day p > a > span.text-teal > strong.text-weight-medium
Animal Welfare Assessment Contest p > a > span.text-teal > strong.text-weight-medium
AVMA COE site visit: Lincoln Memorial University p > a > span.text-teal > strong.text-weight-medium

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Building a strong profession together  div.avma-hero-banner__content__row > div.avma-hero-banner__content > div.field > h4.mb-0
APRIL 12-18 div.avma__component > div.avma__wysiwyg--content > div.field > h5
FEATURED CE div.avma__component > div.avma__wysiwyg--content > div.field > h5.text-align-center

These are opportunities to improve keyboard navigation in your application.

○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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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.
●Links have a discernible name
●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
●Touch targets have sufficient size and spacing.
●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
○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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback