On pages that utilize certain background block layouts, the floating “Back to top” button is partially obscured by other page content due to an incorrect stacking order (z-index). This reduces the button’s visibility and may make it more difficult for users to recognize or activate the control.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 1.1.1: Non-text Content (A)

WCAG 2.4.7: Focus Visible (AA)

Example(s)

About Us

A screenshot of the end of a page depicting a back to top button being partially obscured by the page content.

Remediation

For this issue to be remediated and marked Fixed, all the items from the selected Method below must be addressed.

Method

  1. Ensure the Back to Top button remains on top of other content

The page contains multiple elements using the same id value (legend-one-one), which is referenced by in-page anchor links. Duplicate IDs create ambiguous navigation targets, causing browsers and assistive technologies to potentially navigate to the wrong location or behave inconsistently when users activate reference links.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 4.1.1 – Parsing

Example(s)

Transgender people and law enforcement interactions: Rights and Realities

Remediation

For this issue to be remediated and marked Fixed, all the items from the selected Method below must be addressed.

Method

  1. Assign a unique id value to each element on the page and update any corresponding reference links so they point to the intended destination. In-page anchors should always resolve to a single, unambiguous target.

The Event pages contain multiple elements identified as the primary main landmark. A page should expose a single primary content region so assistive technologies can reliably identify and navigate to the main content. Multiple main landmarks create ambiguity and reduce the effectiveness of landmark navigation.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 1.3.1: Info and Relationships (A)

WCAG 4.1.2: Name, Role, Value (A)

Example(s)

All Event templates (Events)

Theme content wrapper:

<div id="fl-main-content" class="fl-page-content" itemprop="mainContentOfPage" role="main">

Nested Tribe template inner wrapper:

<div class="tribe-common tribe-events tribe-events-view tribe-events-view--list tribe-common--breakpoint-xsmall tribe-common--breakpoint-medium tribe-common--breakpoint-full" data-js="tribe-events-view" data-view-rest-nonce="" data-view-rest-url="https://elevatepfs.com/wp-json/tribe/views/v2/html" data-view-rest-method="GET" data-view-manage-url="1" data-view-breakpoint-pointer="47841c46-b0c6-4f11-a5b7-3a19570e59fd" role="main">

Single event pages also have multiple main landmarks.

Remediation

For this issue to be remediated and marked Fixed, all the items from the selected Method below must be addressed.

Method

  1. Remove or replace additional main landmarks within embedded templates or plugin output.

An image is used as the sole content of a link, but the image does not provide alternative text or another accessible equivalent. Additionally, the link points to the current page rather than a meaningful destination, causing it to simply reload the page when activated. Together, these issues create an unlabeled interactive element that provides little or no value to users.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 1.1.1: Non-text Content (A)

WCAG 2.4.4: Link Purpose (In Context) (A)

WCAG 4.1.2: Name, Role, Value (A)

Example(s)

Global, footer (Home)

A screenshot of a cluster of logos, outlining one to indicate it is problematic.

The image link contains no accessible name and navigates to the current page (meaning clicking it just refreshes the page)

Remediation

For this issue to be remediated and marked Fixed, all the items from the selected Method below must be addressed.

Method

  1. Provide descriptive alternative text for the linked image or another equivalent accessible name on the link.
  2. Update the link destination so it navigates to meaningful content related to the badge, or remove the link entirely if no destination is intended.

Inline links within body content are not sufficiently distinguished from surrounding text. While the links include an underline, the underline does not provide adequate visual contrast against the background in its default state. Additionally, the link text color is only subtly darker than the surrounding body text, making the links difficult to identify without relying primarily on color perception. Together, these styling choices reduce the discoverability of interactive content.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 1.4.1: Use of Color (A)

WCAG 1.4.11: Non-Text Contrast (AA)

Example(s)

Wishlist (not logged in)

A screenshot of a sentence that says "Wishlist is not saved permanently yet. Please log in or Create Account to save it", outlining "log in" and "create account" as links.

The underline color (#A9A9A9) provides 2.35:1 contrast against the white background, which does not satisfy the minimum 3:1 contrast requirement for visual indicators identifying interactive components. Additionally, the link text color (#111111) differs only slightly from the surrounding body text (#212529), making the links difficult to distinguish without relying primarily on color.

Remediation

For this issue to be remediated and marked Fixed, all the items from the selected Method below must be addressed.

Method

  1. Switch the hover state underline colors so it is underlined by default and seems to disappear when switching to the low contrast color

Link text should clearly communicate its purpose so users can understand where the link leads or what action it performs. Generic phrases such as “Learn more,” “Read more,” or “Click here” can become ambiguous when encountered out of context, particularly for users who navigate by lists of links or buttons provided by assistive technologies.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 2.4.4: Link Purpose (In Context) (A)

Example(s)

Contact

A screenshot of 4 sections, each with a "Learn more" link.

The “Learn More” links lack context.

Remediation

For this issue to be remediated and marked Fixed, all the items from the selected Method below must be addressed.

Method 1

  1. Add screen reader text that provides context (eg, “Learn more [about our Services]”)

Method 2

  1. Change the visible text to something that indicates the destination

Resources

Multiple elements on the page share the same id value, resulting in duplicate IDs within the document. Duplicate IDs create ambiguous references within the Document Object Model (DOM) and can interfere with assistive technologies, client-side scripting, and any functionality that relies on unique element identifiers.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 1.3.1: Info and Relationships (A)

WCAG 4.1.2: Name, Role, Value (A)

Example(s)

Revenue Cycle Analytics

Strategic Pricing Analytics:

<div id="medicaid" class="fl-row fl-row-full-width fl-row-bg-none fl-node-zx3uml92o5tp fl-row-default-height fl-row-align-center two-col-icon-wrapper" data-node="zx3uml92o5tp">

Charge Accuracy:

<div id="medicaid" class="fl-row fl-row-full-width fl-row-bg-none fl-node-2wimtadfhjvr fl-row-default-height fl-row-align-center two-col-icon-wrapper" data-node="2wimtadfhjvr">

Remediation

For this issue to be remediated and marked Fixed, all the items from the selected Method below must be addressed.

Method

  1. Update the id attributes to be unique and more accurately represent the subjects they are pertaining to.

The table of contents contains nested unordered lists that are not placed within list items. As a result, the list hierarchy is not represented using valid HTML structure, which may prevent assistive technologies from accurately conveying the relationships between parent and child navigation items.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 1.3.1: Info and Relationships (A)

Example(s)

Notice with tables of contents (June Monthly Notice (#808))

<ul class="ez-toc-list ez-toc-list-level-1 ">
    <ul class="ez-toc-list-level-2">
        ...
    </ul>
    ...
</ul>

Remediation

For this issue to be remediated and marked Fixed, all the items from the selected Method below must be addressed.

Method

  1. Ensure all nested unordered lists are contained within their parent <li> elements. Each <ul> should have only <li> elements as its direct children, with additional nested lists placed inside the appropriate list item to preserve a valid hierarchical structure.

The primary navigation menu uses text with insufficient contrast against its white background. Because the contrast ratio falls below the minimum required for normal-sized text, users with low vision, reduced contrast sensitivity, or certain color vision deficiencies may have difficulty reading and distinguishing the navigation items.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 1.4.3: Contrast Minimum (AA)

Example(s)

Global (Home)

A screenshot of the main menu using a medium grey font on a white background and 14-pixel font size.

Remediation

For this issue to be remediated and marked Fixed, all the items from the selected Method below must be addressed.

Method

  1. Increase the contrast between the navigation text and its background so that all normal-sized menu items achieve at least a 4.5:1 contrast ratio against the background.

A phone number formatting script is incorrectly identifying non-phone-number text as a telephone number. This changes the link destination and accessible name, which may cause users to receive incorrect information about the link’s purpose.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 2.4.4: Link Purpose (In Context) (A)

WCAG 4.1.2: Name, Role, Value (A)

Example(s)

How Flame Resistant Clothing Saved an Army Apache Pilot

A screenshot highlighting a link that says "1200-degree" and also showing the inspector showing the link being interpreted as phone number.

The visible link text appears to reference “1200-degree”, but the script treats it as a telephone number and generates a tel: destination and phone-style aria-label.

Remediation

For this issue to be remediated and marked Fixed, all the items from the selected Method below must be addressed.

Method 1 (Recommended)

  1. Refine the phone number regex logic so it only converts text that clearly matches valid phone number patterns.

Method 2

  1. Avoid triggering the regex by punctuating numbers in similar contexts (eg, “1,200-degree”).