Skip to content
https://blackmagicdesign.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
36
GRADE
F
FIX
9
REVIEW
3
PASS
1
INFO
0
Checks
13
1 PASS 3 REVIEW 9 FIX
F
Heading Hierarchy
Action
159 headings, 9 skip(s)
FIX
159 headings, 9 skip(s)
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 New HyperDeck ISO Recorder 100G
  • H3 New HyperDeck records 8 channels of ProRes Ultra HD video to network storage, over redundant 100G SMPTE‑2022‑7 Ethernet links!
  • H4 From $5,495
  • H2 New Blackmagic Cloud Store Ultra
  • H3 Extremely high-performance network storage with 2 independent 100G Ethernet connections, RAID 5 support and Blackmagic Cloud sync!
  • H4 From $9,719
  • H2 New Blackmagic Media Dock Ultra
  • H3 Now you can use Blackmagic Media Modules for extremely high-performance removable network storage! Features 2 independent 100G Ethernet ports.
  • H4 From $3,295
  • H2 New Blackmagic SDI Expander 8x12G
  • H3 Connect all your 12G-SDI gear to 100G Ethernet SMPTE-2110 IP systems. Supports 8 bi-directional connections and SMPTE-2022-7 redundancy!
  • H4 From $3,295
  • H2 New Blackmagic StudioBridge
  • H3 Bridge 8 x 10G Ethernet SMPTE-2110 connections into modern 100G SMPTE-2022-7 redundant systems, with 90W PoE++ on every port!
  • H4 From $2,745
  • H2 New Blackmagic UpDownCross 100G
  • H3 Get 8 channels of Up, Down and Cross conversion over 100G Ethernet SMPTE-2110! Supports SD, HD and Ultra HD and SMPTE-2022-7 redundancy.
  • H4 From $2,679
  • H2 New Blackmagic Ethernet Switch 820
  • H3 Get the high performance 8-port 100G Ethernet switch designed for SMPTE-2110 IP video! Features redundant PTP clock connections.
  • H4 From $2,525
  • H2 New ATEM Monitoring Rack Panels
  • H3 Introducing the SMPTE-2110 IP video to 12G-SDI and HDMI monitoring converter, all built into an ATEM switcher rack mount control panel!
  • H4 From $1,095
  • H2 INTRODUCING DAVINCI RESOLVE 21
  • H4 Download Free skipped
  • H2 Introducing Fairlight Live
  • H3 The world’s most powerful software-based live audio mixer with support for SMPTE-2110 broadcast and immersive workflows!
  • H4 Download Free
  • H2 Introducing the new Fairlight Live Audio Panel
  • H4 From $2,415 skipped
  • H2 Introducing Blackmagic URSA Cine 12K LF 100G
  • H3 Revolutionary digital film camera designed for cinematic live production with 100G Ethernet and SMPTE-2110 output up to 440fps!
  • H4 From $9,895
  • H2 New Blackmagic URSA Cine Studio Viewfinder
  • H3 New live production viewfinder for URSA Cine with bright 7″ touchscreen, camera control, sunshade and adjustable mount.
  • H4 Only $1,645
  • H2 New Blackmagic URSA Cine Immersive 100G
  • H3 World’s first immersive cinema camera for live immersive production with 100G Ethernet, dual 8Kx8K RGBW sensors and 16 stops of dynamic range.
  • H4 $29,145
  • H2 New ATEM 4 M/E Constellation IP
  • H3 New Ultra HD switchers withnative SMPTE-2110 100G Ethernet. Up to 64 inputs and 52 outputs withpowerful ATEM Constellation features!
  • H4 From $8,795
  • H2 New HyperDeck ISO Recorder 100G
  • H3 New HyperDeck records 8 channels of ProRes Ultra HD video to network storage, over redundant 100G SMPTE‑2022‑7 Ethernet links!
  • H4 From $5,495
  • H2 New Blackmagic Cloud Store Ultra
  • H3 Extremely high-performance network storage with 2 independent 100G Ethernet connections, RAID 5 support and Blackmagic Cloud sync!
  • H4 From $9,719
  • H2 New Blackmagic Media Dock Ultra
  • H3 Now you can use Blackmagic Media Modules for extremely high-performance removable network storage! Features 2 independent 100G Ethernet ports.
  • H4 From $3,295
  • H2 New Blackmagic SDI Expander 8x12G
  • H3 Connect all your 12G-SDI gear to 100G Ethernet SMPTE-2110 IP systems. Supports 8 bi-directional connections and SMPTE-2022-7 redundancy!
  • H4 From $3,295
  • H2 New Blackmagic StudioBridge
  • H3 Bridge 8 x 10G Ethernet SMPTE-2110 connections into modern 100G SMPTE-2022-7 redundant systems, with 90W PoE++ on every port!
  • H4 From $2,745
  • H2 New Blackmagic UpDownCross 100G
  • H3 Get 8 channels of Up, Down and Cross conversion over 100G Ethernet SMPTE-2110! Supports SD, HD and Ultra HD and SMPTE-2022-7 redundancy.
  • H4 From $2,679
  • H2 New Blackmagic Ethernet Switch 820
  • H3 Get the high performance 8-port 100G Ethernet switch designed for SMPTE-2110 IP video! Features redundant PTP clock connections.
  • H4 From $2,525
  • H2 New ATEM Monitoring Rack Panels
  • H3 Introducing the SMPTE-2110 IP video to 12G-SDI and HDMI monitoring converter, all built into an ATEM switcher rack mount control panel!
  • H4 From $1,095
  • H2 INTRODUCING DAVINCI RESOLVE 21
  • H4 Download Free skipped
  • H2 Introducing Fairlight Live
  • H3 The world’s most powerful software-based live audio mixer with support for SMPTE-2110 broadcast and immersive workflows!
  • H4 Download Free
  • H2 Introducing the new Fairlight Live Audio Panel
  • H4 From $2,415 skipped
  • H2 Introducing Blackmagic URSA Cine 12K LF 100G
  • H3 Revolutionary digital film camera designed for cinematic live production with 100G Ethernet and SMPTE-2110 output up to 440fps!
  • H4 From $9,895
  • H2 New Blackmagic URSA Cine Studio Viewfinder
  • H3 New live production viewfinder for URSA Cine with bright 7″ touchscreen, camera control, sunshade and adjustable mount.
  • H4 Only $1,645
  • H2 New Blackmagic URSA Cine Immersive 100G
  • H3 World’s first immersive cinema camera for live immersive production with 100G Ethernet, dual 8Kx8K RGBW sensors and 16 stops of dynamic range.
  • H4 $29,145
  • H2 New ATEM 4 M/E Constellation IP
  • H3 New Ultra HD switchers withnative SMPTE-2110 100G Ethernet. Up to 64 inputs and 52 outputs withpowerful ATEM Constellation features!
  • H4 From $8,795
  • H2 New HyperDeck ISO Recorder 100G
  • H3 New HyperDeck records 8 channels of ProRes Ultra HD video to network storage, over redundant 100G SMPTE‑2022‑7 Ethernet links!
  • H4 From $5,495
  • H2 NAB 2026 Update
  • H3 Watch the video to learn about Fairlight Live, DaVinci Resolve 21, Blackmagic URSA Cine 12K LF 100G, Blackmagic 2110 IP converters and more!
  • H4 Watch Video!
  • H2 Introducing Fairlight Live
  • H3 The world’s most powerful software-based live audio mixer with support for SMPTE-2110 broadcast and immersive workflows!
  • H4 Download Free
  • H2 INTRODUCING DAVINCI RESOLVE 21
  • H4 Download Free skipped
  • H2 Introducing the new Fairlight Live Audio Panel
  • H4 From $2,415 skipped
  • H2 Introducing Blackmagic URSA Cine 12K LF 100G
  • H3 Revolutionary digital film camera designed for cinematic live production with 100G Ethernet and SMPTE-2110 output up to 440fps!
  • H4 From $9,895
  • H2 New Blackmagic URSA Cine Studio Viewfinder
  • H3 New live production viewfinder for URSA Cine with bright 7″ touchscreen, camera control, sunshade and adjustable mount.
  • H4 Only $1,645
  • H2 New Blackmagic URSA Cine Immersive 100G
  • H3 World’s first immersive cinema camera for live immersive production with 100G Ethernet, dual 8Kx8K RGBW sensors and 16 stops dynamic range.
  • H4 $29,145
  • H2 Introducing ATEM 4 M/E Constellation IP
  • H3 New Ultra HD switchers with native SMPTE-2110 100G Ethernet. Up to 64 inputs and 52 outputs with powerful ATEM Constellation features!
  • H4 From $8,795
  • H2 New HyperDeck ISO Recorder 100G
  • H3 New HyperDeck records 8 channels of ProRes Ultra HD video to network storage, over redundant 100G SMPTE-2022‑7 Ethernet links!
  • H4 From $5,495
  • H2 New Blackmagic Cloud Store Ultra
  • H3 Extremely high-performance network storage with 2 independent 100G Ethernet connections, RAID 5 support and Blackmagic Cloud sync!
  • H4 From $9,719
  • H2 New Blackmagic Media Dock Ultra
  • H3 Now you can use Blackmagic Media Modules for high-performance removable network storage! Features 2 independent 100G Ethernet ports.
  • H4 From $3,295
  • H2 Blackmagic SDI Expander 8x12G
  • H3 Connect all your 12G‑SDI gear to 100G Ethernet SMPTE‑2110 IP systems. Supports 8 bi-directional connections and SMPTE‑2022‑7 redundancy!
  • H4 From $3,295
  • H2 New Blackmagic StudioBridge
  • H3 Bridge 8 x 10G Ethernet SMPTE-2110 connections into modern 100G SMPTE-2022-7 redundant systems, with 90W PoE++ on every port!
  • H4 From $2,745
  • H2 New Blackmagic UpDownCross 100G
  • H3 Get 8 channels of Up, Down and Cross conversion over 100G Ethernet SMPTE‑2110! Supports SD, HD and Ultra HD and SMPTE‑2022‑7 redundancy.
  • H4 From $2,679
  • H2 New Blackmagic Ethernet Switch 820
  • H3 Get the high performance 8-port 100G Ethernet switch designed for SMPTE-2110 IP video! Features redundant PTP clock connections.
  • H4 From $2,525
  • H2 New ATEM Monitoring Rack Panels
  • H3 Introducing the SMPTE-2110 IP video to 12G-SDI and HDMI monitoring converter, all built into an ATEM switcher rack mount control panel!
  • H4 From $1,095
  • H2 Latest Videos
  • H2 NAB 2026 Update!
  • H2 DaVinci Resolve 20.2
  • H2 NAB 2025 Update!
  • H2 What's New in Blackmagic Camera for iOS 2.1
  • H2 Customer Stories
  • H4 January 19, 2026 skipped
  • H2 Avatar; Fire and Ash Graded with DaVinci Resolve
  • H3 Learn how colorist Tashi Trieu used DaVinci Resolve Studio to deliver 16 theatrical masters while maintaining consistency of Director James Cameron's aesthetic vision.
  • H2 Netflix’s Las Muertas Graded with DaVinci Resolve
  • H2 Media Storm Stops Time with Blackmagic Camera
  • H2 Gibson Goes Back to the Future with DaVinci Resolve
  • H1 The Latest Stories from Splice
  • H4 Products skipped
  • H4 (empty)
  • H4 Support
  • H4 Community
  • H4 Company
  • H4 Please select your Country or Territory
  • H1 Products duplicate H1
  • H1 Support duplicate H1
  • H1 Community duplicate H1
  • H1 Company duplicate H1
  • H4 Please select your Country or Territory skipped

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

D
Alt Text Quality
Action
2 of 117 images have issues
FIX
2 of 117 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
27 decorative image(s) correctly marked
Info::
88 image(s) with good alt text
117 images 88 good alt text 27 decorative 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 64/100 — 7 failing, 13 passed
FIX
64

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.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.col-xs-10 > div.content > div.owl-dots > button.owl-dot div.col-xs-10 > div.content > div.owl-dots > button.owl-dot
div.col-xs-10 > div.content > div.owl-dots > button.owl-dot div.col-xs-10 > div.content > div.owl-dots > button.owl-dot
div.col-xs-10 > div.content > div.owl-dots > button.owl-dot div.col-xs-10 > div.content > div.owl-dots > button.owl-dot
div.col-xs-10 > div.content > div.owl-dots > button.owl-dot div.col-xs-10 > div.content > div.owl-dots > button.owl-dot
div.col-xs-10 > div.content > div.owl-dots > button.owl-dot div.col-xs-10 > div.content > div.owl-dots > button.owl-dot
div.col-xs-10 > div.content > div.owl-dots > button.owl-dot div.col-xs-10 > div.content > div.owl-dots > button.owl-dot
div.col-xs-10 > div.content > div.owl-dots > button.owl-dot div.col-xs-10 > div.content > div.owl-dots > button.owl-dot
div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot
div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot
div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot
div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot
div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot
div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot
div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot
div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot
div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot
div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot
div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot
div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot div.home-splice > div.home-splice-tiles > div.owl-dots > button.owl-dot

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.sub-content > div.submenu-cloud-login > a > img div.sub-content > div.submenu-cloud-login > a > img
a.content > div.tile-text > div.tile-cta > img.cta-image a.content > div.tile-text > div.tile-cta > img.cta-image

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.sub-content > label.sub-menu-location-dropdown > span.sub-menu-location-product > a.subnav-location-changer-link div.sub-content > label.sub-menu-location-dropdown > span.sub-menu-location-product > a.subnav-location-changer-link

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
Log In div.sub-content > div.submenu-cloud-login > a > span
Watch Video! a.content > div.tile-text > div.tile-cta > h4.tile-action
January 19, 2026 a.content > div.col-xs-10 > div.content > h4.date
Learn how colorist Tashi Trieu used DaVinci Resolve Studio to deliver 16 theatr… a.content > div.col-xs-10 > div.content > h3
January 16, 2026 a.content > div.col-xs-12 > div.content > p.date
Find out how DaVinci Resolve Studio was used to create a dark and rich aestheti… a.content > div.col-xs-12 > div.content > p

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
Download Free div.plate-text > div.col-xs-10 > div.plate-wrappper > h4.plate-status
From $2,415 div.plate-text > div.col-xs-10 > div.plate-wrappper > h4.plate-status
Download Free div.plate-text > div.col-xs-10 > div.plate-wrappper > h4.plate-status
From $2,415 div.plate-text > div.col-xs-10 > div.plate-wrappper > h4.plate-status
Download Free div.col-xs-10 > a.content > div.tile-text > h4.tile-status
From $2,415 div.col-xs-10 > a.content > div.tile-text > h4.tile-status
January 19, 2026 a.content > div.col-xs-10 > div.content > h4.date
Please select your Country or Territory div.gf-baseline > div.gf-actions > div.gf-countries > h4

These are opportunities to improve keyboard navigation in your application.

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.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot
div.grid > div.owl-nav > div.owl-dots > button.owl-dot div.grid > div.owl-nav > div.owl-dots > button.owl-dot

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.english html.english

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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.
○No element has a `[tabindex]` value greater than 0
○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.
○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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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 (missing!) NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="gn-menu-state">; <input type="checkbox" id="sub-menu-location-state">; <input type="checkbox" id="countries-state">
3 controls
0 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#gn-menu-statecheckbox(none)none
#sub-menu-location-statecheckbox(none)none
#countries-statecheckbox(none)none

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

<input type="checkbox" id="gn-menu-state">; <input type="checkbox" id="sub-menu-location-state">; <input type="checkbox" id="countries-state">

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

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 Blackmagic Design: Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The Latest Stories f…20.12:13.0:1
#000000
#FAFAFA
Pass
h1 Products20.12:13.0:1
#000000
#FAFAFA
Pass
h1 Support20.12:13.0:1
#000000
#FAFAFA
Pass
h1 Community20.12:13.0:1
#000000
#FAFAFA
Pass
h1 Company20.12:13.0:1
#000000
#FAFAFA
Pass
h2 New20.12:13.0:1
#000000
#FAFAFA
Pass
h2 HyperDeck ISO20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Recorder 100G20.12:13.0:1
#000000
#FAFAFA
Pass
h2 New Blackmagic Cloud…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 New Blackmagic Media…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 New Blackmagic SDI E…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 New Blackmagic Studi…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 New Blackmagic UpDow…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 New Blackmagic Ether…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 New ATEM Monitoring …20.12:13.0:1
#000000
#FAFAFA
Pass
h2 INTRODUCING20.12:13.0:1
#000000
#FAFAFA
Pass
h2 DAVINCI RESOLVE 2120.12:13.0:1
#000000
#FAFAFA
Pass
h2 Introducing Fairligh…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Introducing the new20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Fairlight Live Audio…20.12:13.0:1
#000000
#FAFAFA
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback