Accessibility

F

Heading Hierarchy

Action

252 headings, 28 skip(s)

FIX

252 headings, 28 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H1 → H4 (missing H2)

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

4 empty heading(s)

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

H4 Previously Visited Products
H4 New and Featured Products
H2 Technology Standards
H2 Amplifiers
H4 Cellular PAs skipped
H4 Gain Block (General Purpose)
H4 Wi-Fi Connectivity
H4 BDS/GPS/GNSS
H4 Low Noise Amplifiers (LNAs)
H4 CATV
H4 Variable Gain Amplifiers (VGAs)
H4 Wireless Infrastructure And Small Cells
H4 Smart Energy - Connected Home And Automation 802.15.4, ISM And Zigbee®
H4 High-Efficiency Small Cell Power Amps For 5G
H2 Technology Standards
H2 Audio And Radio
H4 Audio Gate Drivers skipped
H4 Automotive Tuners
H4 Automotive Digital Data Receivers
H4 Automotive Digital Radio Coprocessors
H4 Consumer Digital Radios
H4 FM Radios
H4 Home Audio Solutions
H4 Multiband Radios
H4 Wireless Gaming
H4 Evaluation Kits
H2 Technology Standards
H2 Attenuators
H4 Digital Attenuators skipped
H4 Voltage Variable Attenuators (VVAs)
H4 Fixed Attenuator Pads (ATN3580)
H4 Fixed Attenuator Pads (ATN3590)
H2 Technology Standards
H2 Clocks And Timing
H4 Automotive Timing skipped
H4 Clock Buffers
H4 PCIe Timing
H4 Clock Generators
H4 Oscillators
H4 Network Synchronization for Data Center and Wireline and Wireless Infrastructure
H4 Jitter Attenuators
H4 RF Synthesizers
H4 Evaluation Kits
H4 Timing Blog
H2 Diodes
H4 Limiter Diodes skipped
H4 PIN Diodes
H4 Schottky Diodes
H4 Varactor Diodes
H4 High reliability Diodes
H4 Limiter Modules
H4 (empty)
H4 (empty)
H2 Technology Standards
H2 Front-End Modules
H4 Cellular skipped
H4 Automotive
H4 Cellular Iot
H4 BDS/GPS/GNSS
H4 Wi-Fi Connectivity
H4 Diversity Receive
H4 Massive-MIMO
H4 Connected Home, Industrial, M2M, Medical, Smart Energy And Wearables
H4 CATV
H2 Technology Standards
H2 Filters and Multiplexers
H4 Antennaplexers skipped
H4 BAW Filters
H2 Technology Standards
H2 Isolation
H4 Automotive Isolation skipped
H4 Digital Isolators
H4 Isolated Gate Drivers
H4 Isolated Analog and ADCs
H4 Industrial I/O
H4 Isolated FET Drivers
H4 Isolated Transceivers
H4 Evaluation Kits
H2 Technology Standards
H2 Modems And DAAs
H4 Data And Voice Modems skipped
H4 Fax Modems
H2 Technology Standards
H2 Optocouplers
H4 Phototransistor Optocouplers skipped
H4 High-Speed Optocouplers
H4 Low Input Current Photodarlington Optocouplers
H4 High-Speed Switching, High CMR, Logic Gate Optocouplers
H4 Schmitt Trigger Optocouplers
H4 Linear Optocouplers
H4 Photovoltaic Optocouplers
H4 High-Speed MOS-FET Driver
H4 Custom Solutions
H2 Technology Standards
H2 Power Management
H4 Display And Lighting skipped
H4 Port Protection And Power Distribution
H4 Voltage Regulation
H2 Technology Standards
H2 Power Over Ethernet
H4 Powered Devices skipped
H4 PSE Controllers - Power Sourcing Equipment
H4 Evaluation Kits
H4 PoE Training Videos
H2 Technology Standards
H2 RF Passives
H4 MIS Silicon Chip Capacitors skipped
H4 Couplers
H2 Technology Standards
H2 Switches
H4 Antenna Swap Switches skipped
H4 Antenna Switch Modules
H4 Antenna Tuning Switches
H4 Carrier Aggregation
H4 Differential Receive Filter Switches
H4 DPDT Antenna Diversity Switches
H4 High Power SPDT And SPST Pin Diode Switches
H4 Smart Coupler
H4 Band Distribution & General Purpose Switches
H2 Technology Standards
H2 TV And Video
H4 Digital TV And Satellite Demodulators skipped
H4 TV Tuners
H4 Evaluation Kits
H2 Technology Standards
H2 Voice
H4 ProSLIC Voice Solutions skipped
H4 Voice DAAs
H4 Evaluation Kits
H2 Technology Standards
H4 Previously Visited Applications skipped
H4 New and Featured Applications
H2 Technology Standards
H2 Aerospace and Defense
H4 Avionics skipped
H4 Communications
H4 Imaging and Radar
H4 Space
H2 Technology Standards
H2 Automotive
H4 Infotainment Digital Cockpit Processing Units skipped
H4 Radio Infotainment
H4 Traction Inverters
H4 Networking Gateways
H4 Battery Management
H4 ADAS And Automated Driving
H4 On-Board Chargers
H4 Lidar, Radar, And Camera Systems
H4 EV Main DC-DC Converter
H4 PTC Heater
H4 Cellular Telematics
H4 Cellular Compensator
H4 Remote Keyless Entry
H4 DSRC And V2X
H2 Technology Standards
H2 Consumer
H4 Audio skipped
H4 Video and Displays
H4 Routers, Gateways and Access Points
H4 Gaming
H4 Set-Top Boxes
H2 Technology Standards
H2 Data Centers
H4 PoE Routers/Switches skipped
H4 Power Supplies
H4 Storage
H4 Servers
H4 Accelerator Cards
H4 Optical Modules
H4 SmartNICs
H4 Spine, Leaf & ToR Switches
H2 Technology Standards
H2 Industrial
H4 Factory Automation skipped
H4 Motor Control
H4 Power and Energy
H4 Power Supplies
H4 Professional Audio/Video
H2 Technology Standards
H2 Wireless Infrastructure
H4 Small Cell skipped
H4 Macro Radio Unit
H4 Massive MIMO
H4 O-RAN
H4 Microwave / MmWave
H4 Baseband / DU
H4 Reference Designs
H2 Technology Standards
H2 Internet of Things (IoT)
H4 Asset Tracking skipped
H4 Connected Home
H4 Cellular IoT & M2M
H4 Home Security / Automation
H4 Industrial IoT
H4 Lighting
H4 Smart Retail
H4 Smart City and Energy
H4 Wearables
H2 Technology Standards
H2 Medical And Healthcare
H4 Hearing Aids skipped
H4 Imaging and Diagnostics
H4 Portable Medical
H4 Biomedical Materials
H4 Ultrasound, X-Rays and CT Scanners
H2 Technology Standards
H2 Mobile
H4 Smartphones skipped
H4 Tablets
H4 Wearables
H2 Technology Standards
H2 Optical Networking
H4 Switch/Router skipped
H4 OTN/PTN
H4 Data Center Interconnect
H4 PON
H4 Campus/Branch Switch
H4 Network Security
H2 Technology Standards
H2 Technical Documents
H2 Reference Designs
H2 Training
H2 Tools
H2 System Solutions
H2 How to Buy
H2 Support & Resources
H2 Training
H2 About
H2 News and Media
H2 Investors
H2 Careers
H2 Contact
H1 Optocouplers
H4 Phototransistor Optocouplers skipped
H4 High-speed Optocouplers
H4 Low Input Current Photodarlington Optocouplers
H4 High-speed Switching, High CMR, Logic Gate Optocouplers
H4 Schmitt Trigger Optocouplers
H4 Linear Optocouplers
H4 Photovoltaic Optocouplers
H4 High-speed MOS-FET Driver
H4 Custom Solutions
H3 Other Resources
H2 Privacy Preference Center
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies
H4 Functional Cookies
H4 Targeting Cookies
H4 Performance Cookies
H3 Performance Cookies
H3 (empty)
H4 (empty)

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

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

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

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

Link & Button Quality

Action

7 issue(s) across 1099 links and 25 buttons

FIX

7 issue(s) across 1099 links and 25 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #; #collapse_

28 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://investors.skyworksinc.com/; https://investors.skyworksinc.com/annual-reports-and-proxies; https://investors.skyworksinc.com/stock-information/dividends-splits; https://investors.skyworksinc.com/events-presentations; https://investors.skyworksinc.com/press-releases; https://investors.skyworksinc.com/financial-information/sec-filings; https://investors.skyworksinc.com/stock-chart-and-quote; https://careers.skyworksinc.com/; https://investors.skyworksinc.com/; https://investors.skyworksinc.com/annual-reports-and-proxies (+18 more)

5 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button (#3278 on page); button (#3290 on page); button (#3306 on page); button (#3322 on page); button.ot-host-box (#3404 on page)

1069 link(s) with descriptive text

1099 links

2 empty

0 generic text

28 new tab

5 empty buttons

Element	Text	Issue	Suggested Fix
https://investors.skyworksinc.com/	Investor Snapshot(opens in a n…	new tab	Add '(opens in new tab)' to text
https://investors.skyworksinc.com/annual…	Annual Reports(opens in a new …	new tab	Add '(opens in new tab)' to text
https://investors.skyworksinc.com/stock-…	Dividends Info(opens in a new …	new tab	Add '(opens in new tab)' to text
https://investors.skyworksinc.com/events…	Investor Events(opens in a new…	new tab	Add '(opens in new tab)' to text
https://investors.skyworksinc.com/press-…	Press Releases(opens in a new …	new tab	Add '(opens in new tab)' to text
https://investors.skyworksinc.com/financ…	SEC Filings(opens in a new tab…	new tab	Add '(opens in new tab)' to text
https://investors.skyworksinc.com/stock-…	Stock Information(opens in a n…	new tab	Add '(opens in new tab)' to text
https://careers.skyworksinc.com/	Job Openings(opens in a new ta…	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
https://investors.skyworksinc.com/	Investor Snapshot(opens in a n…	new tab	Add '(opens in new tab)' to text
https://investors.skyworksinc.com/annual…	Annual Reports(opens in a new …	new tab	Add '(opens in new tab)' to text
https://investors.skyworksinc.com/stock-…	Dividends Info(opens in a new …	new tab	Add '(opens in new tab)' to text
https://investors.skyworksinc.com/events…	Investor Events(opens in a new…	new tab	Add '(opens in new tab)' to text
https://investors.skyworksinc.com/press-…	Press Releases(opens in a new …	new tab	Add '(opens in new tab)' to text
https://investors.skyworksinc.com/financ…	SEC Filings(opens in a new tab…	new tab	Add '(opens in new tab)' to text
https://investors.skyworksinc.com/stock-…	Stock Information(opens in a n…	new tab	Add '(opens in new tab)' to text
https://careers.skyworksinc.com/	Job Openings(opens in a new ta…	new tab	Add '(opens in new tab)' to text
#collapse_	(empty)	empty	Add link text or aria-label
/-/media/SkyWorks/Documents/Products/260…	Gamma_total_dose_radiation_per…	new tab	Add '(opens in new tab)' to text
/-/media/SkyWorks/Documents/Brochures/Op…	Optocouplers-Selection-Guide.p…	new tab	Add '(opens in new tab)' to text
/-/media/SkyWorks/Documents/Products/260…	WP_Optocouplers_for_the_Hybrid…	new tab	Add '(opens in new tab)' to text
/-/media/SkyWorks/Documents/Products/260…	WP_Proton_radiation_graph.pdf …	new tab	Add '(opens in new tab)' to text
/-/media/SkyWorks/Documents/Products/260…	WP_RGA_2017_Feb.pdf …	new tab	Add '(opens in new tab)' to text
https://www.skyworksinc.com/-/media/SkyW…	Aerospace and Defense …	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/skywork…	(opens in a new tab)	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/skyworksinc/	(opens in a new tab)	new tab	Add '(opens in new tab)' to text
https://twitter.com/skyworksinc	(opens in a new tab)	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCVT7P0K…	(opens in a new tab)	new tab	Add '(opens in new tab)' to text
/Articles/Privacy%20Policy	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

1089 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#; #collapse_

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://investors.skyworksinc.com/; https://investors.skyworksinc.com/annual-reports-and-proxies; https://investors.skyworksinc.com/stock-information/dividends-splits; https://investors.skyworksinc.com/events-presentations; https://investors.skyworksinc.com/press-releases; https://investors.skyworksinc.com/financial-information/sec-filings; https://investors.skyworksinc.com/stock-chart-and-quote; https://careers.skyworksinc.com/; https://investors.skyworksinc.com/; https://investors.skyworksinc.com/annual-reports-and-proxies (+18 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button (#3278 on page); button (#3290 on page); button (#3306 on page); button (#3322 on page); button.ot-host-box (#3404 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

F

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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

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

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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

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

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation

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

Form Input Types

4 input(s) using type=text where a specific type would help

REVIEW

4 input(s) using type=text where a specific type would help

Input "product_search_input" should use type="search" (currently type="text")

Field name "product_search_input" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "new_header_search_input_desktop" should use type="search" (currently type="text")

Field name "new_header_search_input_desktop" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "new_header_search_input_mobile" should use type="search" (currently type="text")

Field name "new_header_search_input_mobile" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "vendor-search-handler" should use type="search" (currently type="text")

Field name "vendor-search-handler" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Skyworks | Error 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

A

Landmark Structure

3 landmarks

PASS

3 landmarks

<main> landmark present

No <nav> landmark found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

6 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 6 all-caps heading(s)

A+

Alt Text Quality

All 11 images OK

PASS

All 11 images OK

11 image(s) with good alt text

11 images 11 good alt text

All images have appropriate alt text.

A

Form Accessibility

1 of 11 controls have issues

PASS

1 of 11 controls have issues

1 control(s) without accessible label

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

Got: <input type="text" name="vendor-search-handler" id="vendor-search-handler">

10 control(s) properly labeled

11 controls

10 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#product_search_input	input	Product search input	aria-label
#new_header_search_input_desktop	input	Product search input	aria-label
#new_header_search_input_mobile	input	Product search input	aria-label
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	Switch Label	for/id
#select-all-vendor-groups-handler	checkbox	Switch Label	for/id
#select-all-vendor-leg-handler	checkbox	Switch Label	for/id
#vendor-search-handler	text	(none)	none

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

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

A+

Form Input Quality

11 form control(s) checked, no input-semantic issues

PASS

11 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

60 explicit tabindex attribute(s) checked, no anti-patterns

PASS

60 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

All 2 iframe(s) have descriptive titles

PASS

All 2 iframe(s) have descriptive titles

All 2 iframe(s) have title attributes

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

No visible text nodes measured on the page

PASS

No visible text nodes measured on the page

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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)

Element	Ratio	Required	FG	BG	Result
h1 Optocouplers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Privacy Preference C…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Other Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Manage Consent Prefe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Performance Cookies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Skyworks \| Products …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Site Content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Products	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to Main Content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Products	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Default	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Amplifiers	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Audio and Radio	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Attenuators	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Clocks and Timing	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Diodes	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Front-End Modules	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Filters and Multiple…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Isolation	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Modems And DAAs	21.00:1	4.5:1	#000000	#FFFFFF	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.

A+

Lighthouse Accessibility Audits

Score 99/100 — 2 failing, 27 passed

PASS

99

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.

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
Phototransistor Optocouplers `div.pad_top_50123 > div.col-sm-12 > a.item-prod-family > h4`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookies Policy `div#onetrust-group-container > div#onetrust-policy > p#onetrust-policy-text > a.ot-cookie-policy-link`
and our Privacy Policy. `div#onetrust-group-container > div#onetrust-policy > p#onetrust-policy-text > a.ot-imprint-link`

○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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<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

○`<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.

○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.