Interactive controls should provide a sufficiently large target area or enough spacing from neighboring controls so users can activate them accurately. Small or tightly spaced targets can be difficult to use for people with limited dexterity, tremors, reduced fine motor control, or users interacting with touchscreens.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 2.5.8: Target Size (Minimum) (AA) (external link, opens in a new tab)

Example(s)

A screenshot of 3 links in a header, indicating they are the problematic targets with only 15 pixels of height.

These links in the header only have about ~15px of clickable height.

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 clickable area of the links so each target is at least 24 by 24 CSS pixels.
    1. This can be done by either increasing the padding or line-height

Landmark regions should use semantics that accurately describe their purpose and should be uniquely identified when multiple regions of the same type are present. Inappropriate or unnamed landmarks can make page structure less meaningful and more difficult to navigate for screen reader users who rely on landmark navigation to understand and move through a page efficiently.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 1.3.1: Info and Relationships (A) (external link, opens in a new tab)

WCAG 2.4.1: Bypass Blocks (A) (external link, opens in a new tab)

Example(s)

Global, footer (Home (external link, opens in a new tab))

<div class="inside-footer-widgets">
    <div class="footer-widget-1">
        <aside id="nav_menu-2" class="widget inner-padding widget_nav_menu">
            <h2 class="widget-title">Help &amp; Info</h2>
            <div class="menu-help-info-container">
                <ul id="menu-help-info" class="menu">
                    <li id="menu-item-1102813" class="...-1102813"><a href="/my-account/">My Account</a></li>
                    <li id="menu-item-1102814" class="...-1102814"><a href="/cart/">Cart</a></li>
                    <li id="menu-item-1102815" class="...-1102815"><a href="/checkout/">Checkout</a></li>
                    <li id="menu-item-1102816" class="...-1102816"><a href="/faq/">FAQ</a></li>
                    <li id="menu-item-1102817" class="...-1102817"><a rel="privacy-policy" href="/policies/">Privacy Policy</a></li>
                </ul>
            </div>
        </aside>
    </div>
    <div class="footer-widget-2">
        <aside id="nav_menu-3" class="widget inner-padding widget_nav_menu">
            <h2 class="widget-title">Locations</h2>
            <div class="menu-locations-container">
                <ul id="menu-locations" class="menu">
                    <li id="menu-item-1102818" class="...-1102818"><a href="/antique-store-nyc-52nd/">Midtown West NYC</a></li>
                    <li id="menu-item-1184961" class="...-1184961"><a href="/antique-store-grand-ave-los-angeles/">Los Angeles CA</a></li>
                    <li id="menu-item-1102820" class="...-1102820"><a href="/antique-warehouses-scranton-pennsylvania/">Scranton PA</a></li>
                </ul>
            </div>
        </aside>
    </div>
    <div class="footer-widget-3">
        <aside id="nav_menu-4" class="widget inner-padding widget_nav_menu">
            <h2 class="widget-title">Resources</h2>
            <div class="menu-resources-container">
                <ul id="menu-resources" class="menu">
                    <li id="menu-item-1102826" class="...-1102826"><a href="/how-our-farm-tables-are-made/">How Our Farm Tables Are Made</a></li>
                    <li id="menu-item-1102827" class="...-1102827"><a href="/designer-wholesale/">Designer &amp; Wholesale</a></li>
                    <li id="menu-item-1102828" class="...-1102828"><a href="/ogt-purchasing/">Purchasing</a></li>
                    <li id="menu-item-1191067" class="...-1191067"><a href="/wishlist/">Wishlist</a></li>
                    <li id="menu-item-1208057" class="menu-item menu-item-type-post_type menu-item-object-post menu-item-1208057"><a href="/blog/how-to-use-the-wishlist/">How to Use the Wishlist</a></li>
                </ul>
            </div>
        </aside>
    </div>
    <div class="footer-widget-4">
        <aside id="nav_menu-5" class="widget inner-padding widget_nav_menu">
            <h2 class="widget-title">Our Company</h2>
            <div class="menu-our-company-container">
                <ul id="menu-our-company" class="menu">
                    <li id="menu-item-1102821" class="...-1102821"><a href="/about-us/">About Us</a></li>
                    <li id="menu-item-1102824" class="...-1102824"><a href="/contact-us/">Contact Us</a></li>
                    <li id="menu-item-1102823" class="...-1102823"><a href="/we-are-green/">We Are Green</a></li>
                </ul>
            </div>
        </aside>
    </div>
</div>

Because <aside> maps to a complementary landmark, this creates multiple generic complementary landmarks in the accessibility tree even though these regions function as navigation menus.

The individual landmarks also do not provide accessible names, so assistive technology users may encounter several indistinguishable complementary regions.

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. Replace each footer navigation widget’s <aside> element with a semantic <nav> element and associate the existing visible heading with the navigation landmark using aria-labelledby.
<nav aria-labelledby="help-info-heading">
    <h2 id="help-info-heading">Help &amp; Info</h2>
    <ul>
        ...
    </ul>
</nav>

Method 2

  1. Replace the <aside> with <nav> and provide a unique accessible name using aria-label.
<nav aria-label="Help & Info">
    <h2>Help &amp; Info</h2>
    <ul>
        ...
    </ul>
</nav>

IDs in HTML must be unique within a page. When the same ID is used more than once—especially when referenced by ARIA attributes, labels, or anchor links—it creates ambiguity in the DOM. Assistive technologies and browser features may not behave as expected, resulting in unreliable or broken navigation and announcements.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 4.1.1 – Parsing (external link, opens in a new tab)

Example(s)

Extended Business Office (external link, opens in a new tab)

<div id="insurance-follow-up" class="fl-row fl-row-full-width fl-row-bg-none fl-node-1mtlpyjs25bv fl-row-default-height fl-row-align-center two-col-icon-wrapper" data-node="1mtlpyjs25bv">

The insurance-follow-up ID shows up as the container for “A/R Follow-Up”, “Low Balance Insurance Follow Up”, and “Denials Management & Prevention”.

This also breaks “jump to” navigation.

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
    1. When copy/pasting containers, ensure the IDs are updated.

IDs in HTML must be unique within a page. When the same ID is used more than once—especially when referenced by ARIA attributes, labels, or anchor links—it creates ambiguity in the DOM. Assistive technologies and browser features may not behave as expected, resulting in unreliable or broken navigation and announcements.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 4.1.1 – Parsing (external link, opens in a new tab)

Example(s)

Revenue Cycle Analytics (external link, opens in a new tab)

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

The disability ID shows up as the container for “Price Transparency” and “Strategic Pharmacy Pricing Analytics (SPARx)”.

This also breaks “jump to” navigation.

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
    1. When copy/pasting containers, ensure the IDs are updated.

IDs in HTML must be unique within a page. When the same ID is used more than once—especially when referenced by ARIA attributes, labels, or anchor links—it creates ambiguity in the DOM. Assistive technologies and browser features may not behave as expected, resulting in unreliable or broken navigation and announcements.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 4.1.1 – Parsing (external link, opens in a new tab)

Example(s)

Revenue Cycle Analytics (external link, opens in a new tab)

<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">

The medicaid ID shows up as the container for “Strategic Pricing Analytics” and “Charge Accuracy”.

This also breaks “jump to” navigation.

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
    1. When copy/pasting containers, ensure the IDs are updated.

The newsletter modal’s close button does not maintain sufficient contrast against its background. In its default state, the black “X” appears over a dark image and may be difficult to perceive. On hover and keyboard focus, the button background becomes black while the icon remains black, causing the close symbol to effectively disappear.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 1.4.11: Non-Text Contrast (AA) (external link, opens in a new tab)

Example(s)

Global (Home (external link, opens in a new tab))

In the default state, the transparent button places this black icon over a dark photographic background, resulting in poor contrast.

On hover and focus, the button receives a black background while the SVG icon remains black, causing the “X” to lose nearly all visible contrast.

Remediation

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

Provide the close icon with a color that maintains at least a 3:1 contrast ratio against its immediate background in all states.

Method 1

  1. Provide a background for the X with a 3:1 contrast with the X color
  2. Ensure the X still has enough contrast against the hover/focus interactions

Method 2

  1. Make the X a color that has enough contrast against the fuselage
  2. Ensure the X still has enough contrast against the hover/focus interactions

Multiple iframe elements do not have accessible names identifying the content they contain. Screen reader users navigating between frames may encounter unnamed frames, making it difficult to determine their purpose or decide whether to enter and interact with their content.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 4.1.2: Name, Role, Value (A) (external link, opens in a new tab)

Example(s)

Remediation

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

Method

  1. Add a title attribute to describe what the purpose of the embed is.

Post listings contain repeated links whose visible and accessible link text is only “Read More”. When multiple posts use the same generic link text, users navigating links independently from the surrounding page content may be unable to determine which post each link opens.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 2.4.4: Link Purpose (In Context) (A) (external link, opens in a new tab)

Example(s)

Webinar Archive (external link, opens in a new tab)

<a class="fl-post-more-link" href="https://elevatepfs.com/webinar/medicaid-eligibility-enrollment-legislative-changes/">Read More</a>

When multiple posts use vague links, a screen reader link list will just list Read More, Read More, Read More, etc.

Remediation

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

Method

  1. Add screen reader text for context, eg:
    1. <a class="fl-post-more-link" href="https://elevatepfs.com/webinar/medicaid-eligibility-enrollment-legislative-changes/">Read More<span class="sr-only"> about Navigating Medicaid Legislative Changes: Eligibility & Enrollment</span></a>

Remediation methods to avoid

  • Avoid using an aria-label on the link instead. While technically valid, it is not as widely consistent or supported at hidden screen reader text is.

The recurring payment setup guide includes readable instructional text, but screenshots used throughout the document do not include alternative text or equivalent descriptions. The PDF also includes repeated Scribe branding on each page and announces at the beginning that the document is inaccessible because text extraction files could not be downloaded.

Although most procedural steps are conveyed in text, several instructions rely on visual positioning or visual state, such as identifying controls on the left or right side of the screen or confirming that a switch appears green.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 1.1.1: Non-text Content (A) (external link, opens in a new tab)

WCAG 1.3.1: Info and Relationships (A) (external link, opens in a new tab)

WCAG 1.4.1: Use of Color (A) (external link, opens in a new tab)

Example(s)

Point and Pay Online Payments (external link, opens in a new tab)

PDF: Step‑by‑Step Account Registration and Recurring Payments Instructions (external link, opens in a new tab)

Screen reader users can access much of the written procedure and may be able to complete the setup independently. However, they do not receive the same contextual information provided by the screenshots and may have more difficulty locating controls, confirming interface state, or understanding the relationship between the written instructions and the payment portal.

The repeated “Made with Scribe” content and the initial inaccessible-document announcement also create unnecessary screen reader noise and may cause users to believe that the guide cannot be used accessibly.

Additionally, since the PDF is misformatted, it creates disorienting breaks in the content.

The link itself also does not specify this link as a PDF.

Remediation

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

Method

  1. Provide the recurring payment instructions as an accessible HTML webpage and retain the PDF only as a supplemental printable/downloadable version.
  2. If the PDF must remain the primary format:
    1. add meaningful alternative text or adjacent textual descriptions for screenshots
    2. remove or artifact repetitive Scribe branding
    3. remove the initial inaccessible-document error message
    4. ensure headings, lists, reading order, and links are properly tagged
    5. avoid relying on visual location or color alone to identify controls or states
    6. describe confirmation states in functional terms, such as “the Recurring Payments switch will display as On”, rather than relying only on green

Some recommendation cards expose incorrect accessible names because the link’s title attribute was copied from another location and not updated. Although the image alternative text correctly identifies the current business, screen readers announce the outdated link title instead, causing users to hear the wrong destination before activating the link.

User impacts

Follow the links for additional information on user impairments:

WCAG violation(s)

WCAG 1.1.1: Non-text Content (A) (external link, opens in a new tab)

WCAG 2.4.4: Link Purpose (In Context) (A) (external link, opens in a new tab)

WCAG 4.1.2: Name, Role, Value (A) (external link, opens in a new tab)

Example(s)

On Marfa’s page:

<a href="https://www.instagram.com/bigsandycoffee/" title="Big Sandy in Marfa" rel="noopener" target="_blank">
    <img src="https://cdn.shopify.com/s/files/1/1020/2551/files/big-sandy-cafe-in-marfa_e24be59e-89ed-44d3-bbda-fd2630107389_1024x1024.jpg?v=1740585326" alt="Big Sandy Coffee in Marfa, Texas" style="margin-bottom: 16px; float: none;">
</a>
<a href="https://www.instagram.com/wrongmarfa/" title="Big Sandy in Marfa" rel="noopener" target="_blank">
    <img src="https://cdn.shopify.com/s/files/1/1020/2551/files/the-wrong-store-in-marfa-texas-city-guide_1024x1024.jpg?v=1740585095" style="margin-bottom: 16px; float: none;">
</a>

The image alternative text identifies the current location, but the parent link’s title attribute contains the name of a different business. During testing with NVDA, the outdated title was announced as the link name, causing the accessible name to misidentify the destination.

Particularly in this example since “Wrong Store” is missing alt text altogether.

Remediation

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

Method

  1. When duplicating modules, always ensure the attribute information is accurate to the current module