bugsnag.com Accessibility Report

Accessibility audit of bugsnag.com — scanned on Feb 20, 2026

Technology
0 /100
D Poor

6 issues found across 3 categories

1 Critical 4 Major 1 Minor

WCAG Compliance Overview

Perceivable 1 issues
Operable 2 issues
Understandable 0 issues
Robust 3 issues

Issues Found

Buttons missing accessible name

Critical

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
1 element(s) affected
  • <button>
How to fix

Add text content, aria-label, or title to all <button> elements.

Frames missing title

Major

Iframes must have title attributes describing their content.

WCAG 2.4.1
1 element(s) affected
  • <iframe src="https://www.googletagmanager.com/ns.html?id=GTM-MTQKQW6">
How to fix

Add descriptive title attributes to all <iframe> elements.

Duplicate element IDs

Major

Element IDs must be unique to ensure correct assistive technology behavior.

WCAG 4.1.1
19 element(s) affected
  • id="dropdownNavbar"
  • id="clip0_93_83"
  • id="clip0_273_341"
  • id="clip0_273_353"
  • id="clip0_273_368"
How to fix

Make each id attribute value unique within the page.

Invalid ARIA attributes

Major

ARIA attributes must be valid and used correctly to work with assistive technologies.

WCAG 4.1.2
5 element(s) affected
  • <ul aria-labelledby="menu-button"> (missing ref)
  • <div aria-labelledby="tw-login-modal-title"> (missing ref)
How to fix

Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

Generic link text

Major

Links must have descriptive text that indicates their purpose. Generic text like 'click here' or 'read more' does not help screen reader users understand where the link goes.

WCAG 2.4.4
4 element(s) affected
  • <a href="https://smartbear.com/resources/case-studies/mercado-libre/">read more</a>
  • <a href="https://smartbear.com/resources/case-studies/yelp/">read more</a>
  • <a href="https://smartbear.com/resources/case-studies/square/">read more</a>
  • <a href="https://smartbear.com/resources/case-studies/hoteltonight/?_">read more</a>
How to fix

Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.

Incorrect list structure

Minor

List items must be contained within <ul>, <ol>, or <dl> elements.

WCAG 1.3.1
6 element(s) affected
  • <dt> outside <dl>
  • <dd> outside <dl>
How to fix

Ensure <li> elements are direct children of <ul> or <ol>.

Top Priority Fixes

Here are the most impactful changes bugsnag.com should make to improve accessibility:

  1. #1
    Buttons missing accessible name Critical

    Add text content, aria-label, or title to all <button> elements.

  2. #2
    Duplicate element IDs Major

    Make each id attribute value unique within the page.

  3. #3
    Invalid ARIA attributes Major

    Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

Frequently Asked Questions

Is bugsnag.com accessible?

bugsnag.com scored 50/100 (grade D) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is bugsnag.com WCAG compliant?

Our scan found 6 accessibility issues on bugsnag.com. Full WCAG compliance requires addressing all critical and major issues identified above.

Is bugsnag.com EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see bugsnag.com's compliance status.

What accessibility issues does bugsnag.com have?

See the full issue list above with severity levels, affected elements, and recommended fixes for bugsnag.com.

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing