Accessibility

F

Heading Hierarchy

Action

292 headings, 8 skip(s)

FIX

292 headings, 8 skip(s)

Multiple H1 headings (21 found)

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

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.

H1 BUILTFOR SCALE.
H2 Custom software engineered to scale your business
H3 SYNEX WEB
H2 How we build your software: from idea to launch
H3 Understand Your Needs
H3 Plan and Design
H3 Build and Test
H3 Launch and Support
H2 Selected projects that showcase our expertise.
H4 Pringles, interactive 3D experience skipped
H4 GoPro, product showcase website
H2 A software development company focused on quality and long-term results
H2 Software solutions for every stage of your project
H3 Custom Software
H3 Update Existing Systems
H3 Testing and Quality Checks
H3 Support and Improvements
H2 Have a project in mind? Let's build it together.
H2 We develop modern and scalable websites.
H3 SYNEX WEB
H2 How we build your website: from idea to launch
H3 Understand Your Goals
H3 Plan the Pages
H3 Build the Website
H3 Launch and Improve
H2 Selected projects that showcase our expertise.
H4 Pringles, interactive 3D web experience skipped
H4 GoPro, responsive product experience
H2 A software development company focused on quality and long-term results.
H2 Website solutions for every stage of your project
H3 Website Design and Development
H3 Improve Your Existing Website
H3 Speed and Accessibility
H3 Website Support
H2 Have a project in mind? Let's build it together.
H2 High-impact application development
H3 NEXA ESTATE AI
H2 How we create your app: from idea to release
H3 Plan the App
H3 Design the Screens
H3 Develop and Test
H3 Publish and Support
H2 Selected projects that showcase our expertise.
H4 VELORA, urban mobility app skipped
H4 VEYRO, finance platform app
H2 A software development company focused on quality and long-term results.
H2 App solutions from the first idea to launch
H3 Plan Your App
H3 Build for iPhone and Android
H3 Test Before Launch
H3 Publish and Keep Improving
H2 Have a project in mind? Let's build it together.
H2 Explore the experience before development begins
H3 LUME
H2 How we plan your product before development
H3 Understand the Idea
H3 Organize the Screens
H3 Make a Clickable Prototype
H3 Review and Deliver
H2 Selected projects that showcase our expertise.
H4 SENDA, fintech experience prototype skipped
H4 NOVARA, architecture website prototype
H2 One design system from concept to handoff
H2 Figma prototypes from idea to final design
H3 Plan the Screens
H3 Create a Clickable Prototype
H3 Refine the Visual Design
H3 Prepare for Development
H2 Have a project in mind? Let's build it together.
H2 Online stores designed to turn visitors into customers
H3 VÉLOAP
H2 How we build your online store: from setup to sales
H3 Plan the Store
H3 Design the Shopping Experience
H3 Set Up Payments and Orders
H3 Launch and Improve
H2 Selected projects that showcase our expertise.
H4 GoPro product commerce experience skipped
H4 SONARA audio commerce concept
H2 A complete commerce experience, beyond the storefront
H2 Online store solutions from setup to sales
H3 Build Your Online Store
H3 Cart and Secure Payments
H3 Orders and Inventory
H3 Improve Shopping and Sales
H2 Have a project in mind? Let's build it together.
H2 Turn repetitive workflows into intelligent operations
H3 RIVALYN AI
H2 How we add AI to your business processes
H3 Find Tasks to Improve
H3 Plan the AI Workflow
H3 Connect and Test
H3 Monitor and Improve
H2 Selected projects that showcase our expertise.
H4 NOVIS AI skipped
H4 Sinovis AI
H2 A software development company focused on quality and long-term results.
H2 AI solutions that make everyday work easier
H3 Automate Repetitive Tasks
H3 AI for Your Business Information
H3 Connect Your Existing Tools
H3 Review and Improve Results
H2 Have a project in mind? Let's build it together.
H2 Interfaces that feel obvious without feeling ordinary
H3 LUMORA
H2 How we design interfaces that are easy to use
H3 Learn About Your Users
H3 Plan the Experience
H3 Design the Interface
H3 Check and Improve the Design
H2 Selected projects that showcase our expertise.
H4 SENDA skipped
H4 NOVIS AI
H2 A software development company focused on quality and long-term results.
H2 UI/UX solutions that make products easier to use
H3 Understand Your Users
H3 Design Clear Screens
H3 Keep the Design Consistent
H3 Test and Improve
H2 Have a project in mind? Let's build it together.
H2 High-impact 3D modeling and rendering
H3 ASTRA · WEARABLE INTELLIGENCE
H2 How we create your 3D experience: from model to website
H3 Plan the Scene
H3 Create the 3D Models
H3 Make It Interactive
H3 Optimize and Launch
H2 Selected projects that showcase our expertise.
H4 Pringles interactive 3D experience skipped
H4 GoPro MAX, interactive 3D product website
H2 A software development company focused on quality and long-term results.
H2 3D solutions for products and websites
H3 3D Models and Realistic Images
H3 Interactive Product Views
H3 3D Animation for Websites
H3 Fast and Smooth 3D
H2 Have a project in mind? Let's build it together.
H1 SYNEX WEB duplicate H1
H2 How SYNEX WEB was built
H3 Discovery
H3 Strategy
H3 Solution
H2 Inside the platform
H2 Have a project in mind? Let's build it together.
H1 ASTRA duplicate H1
H2 Inside the ASTRA experience
H3 Product Modeling
H3 Design Details
H3 Digital Showcase
H2 Explore ASTRA
H2 Have a project in mind? Let's build it together.
H1 LUMORA duplicate H1
H2 Inside the Lumora experience
H3 Visual Identity
H3 Portfolio Experience
H3 Growth Journey
H2 Explore the Lumora website
H2 Have a project in mind? Let's build it together.
H1 SENDA duplicate H1
H2 How SENDA was shaped in Figma
H3 Structure
H3 Visual Direction
H3 Final Prototype
H2 Inside the SENDA prototype
H2 Have a project in mind? Let's build it together.
H1 LUME duplicate H1
H2 How LUME was shaped in Figma
H3 Structure
H3 Visual Direction
H3 Final Prototype
H2 Inside the LUME prototype
H2 Have a project in mind? Let's build it together.
H1 PRINGLES duplicate H1
H2 How PRINGLES was built
H3 Discovery
H3 Strategy
H3 Solution
H2 Inside the experience
H2 Have a project in mind? Let's build it together.
H1 GOPRO duplicate H1
H2 How GOPRO was built
H3 Discovery
H3 Strategy
H3 Solution
H2 Inside the experience
H2 Have a project in mind? Let's build it together.
H1 SONARA duplicate H1
H2 How SONARA was designed
H3 Brand & Community
H3 Collection Design
H3 Product Storytelling
H2 Inside SONARA
H2 Have a project in mind? Let's build it together.
H1 VÉLOAP duplicate H1
H2 How VÉLOAP was shaped
H3 Merchandising
H3 Brand Campaign
H3 Catalog System
H2 Inside VÉLOAP
H2 Have a project in mind? Let's build it together.
H1 VELORA duplicate H1
H2 How VELORA was designed
H3 Product Flow
H3 Mobile Experience
H3 Core Experience
H2 Inside VELORA
H2 Have a project in mind? Let's build it together.
H1 VEYRO duplicate H1
H2 How VEYRO was designed
H3 Financial Flow
H3 Mobile Experience
H3 Core Product
H2 Inside VEYRO
H2 Have a project in mind? Let's build it together.
H1 NOVIS AI duplicate H1
H2 How NOVIS AI was designed
H3 Workflow Experience
H3 Operational Intelligence
H3 Cross-Platform Product
H2 Inside NOVIS AI
H2 Have a project in mind? Let's build it together.
H1 SINOVIS AI duplicate H1
H2 How Sinovis AI was designed
H3 Operations Dashboard
H3 Workflow Control
H3 Insights & Reporting
H2 Inside Sinovis AI
H2 Have a project in mind? Let's build it together.
H1 RIVALYN AI duplicate H1
H2 Inside the Rivalyn AI platform
H3 Competitor Intelligence
H3 Market Signals
H3 Alerts & Creative Research
H2 Rivalyn AI product views
H2 Have a project in mind? Let's build it together.
H1 ATELIER NORTH duplicate H1
H2 How ATELIER NORTH was built
H3 Discovery
H3 Strategy
H3 Solution
H2 Inside the experience
H2 Have a project in mind? Let's build it together.
H1 NOVARA duplicate H1
H2 How NOVARA was shaped in Figma
H3 Wireframe
H3 Visual Direction
H3 Final Prototype
H2 Inside the NOVARA prototype
H2 Have a project in mind? Let's build it together.
H1 NEXA ESTATE AI duplicate H1
H2 Designing the NEXA Estate AI experience
H3 Personalized Discovery
H3 Property Exploration
H3 AI-Guided Decisions
H2 Inside NEXA Estate AI
H2 Have a project in mind? Let's build it together.
H1 Our Craft, Your Vision. duplicate H1
H2 SOFTWARE & AI SYSTEMS
H3 Rivalyn AI, competitor intelligence platform
H3 SYNEX WEB, modern software experience
H3 NOVIS AI, operations agentification platform
H3 Sinovis AI, workflow operations platform
H2 WEBSITES & E-COMMERCE
H3 LUMORA, creative growth website
H3 SONARA, audio commerce concept
H3 SENDA, fintech landing prototype
H3 Atelier North, architecture website
H2 MOBILE APPS
H3 NEXA Estate AI, intelligent real estate app
H3 VEYRO, finance platform app
H3 VELORA, urban mobility app
H3 VÉLOAP, cycling e-commerce experience
H2 UI/UX & PROTOTYPING
H3 LUME, Figma interface prototyping
H3 NOVARA, architecture Figma prototype
H2 3D & PRODUCT EXPERIENCES
H3 ASTRA, wearable product visualization
H3 Pringles, interactive 3D experience
H3 GoPro, interactive 3D product website
H2 Have a project in mind? Let's build it together.
H2 What do you need?
H2 Budget & timeline
H2 Tell us about you & the idea
H1 Let's build something great. duplicate H1
H2 Contact Us
H1 The people building your software. duplicate H1
H2 Software Engineering Lead
H2 AI & Automation Lead
H2 Founder & CEO
H2 Software Architect
H2 Infrastructure & DevOps Lead
H2 Prefer to read this in Spanish?

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

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

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

3 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 3 <nav> element(s)

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

Landmark Structure

18 landmarks

REVIEW

18 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

3 <nav> landmark(s) found

1 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

B

Mobile Keyboard & Autofill

2/9 eligible field(s) missing autocomplete or inputmode

REVIEW

2/9 eligible field(s) missing autocomplete or inputmode

2 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email">, <input type="email" name="email">

C

Mobile-Readable Font Sizes

Action

89% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

89% of visible text renders at >= 12 CSS px (3 below threshold)

3 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <button> 11.2px ("EN"); <button> 11.2px ("ES"); <textpath> 8.8px ("SCROLL DOWN ✶ SCROLL DOWN ✶ SCROLL DOWN ...").

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | Sinvec Systems ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

C

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

B

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: dark

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #080808

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta dark ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

h1 BUILT

1.28:1

#000000

on

#211F1D

needs 3.0:1 (large text)

32px · mid-page

h1 FOR SCALE.

1.28:1

#000000

on

#211F1D

needs 3.0:1 (large text)

32px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 BUILT	1.28:1	3.0:1	#000000	#211F1D	Fail
h1 FOR SCALE.	1.28:1	3.0:1	#000000	#211F1D	Fail
h1 SYNEX WEB	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 ASTRA	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 LUMORA	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 SENDA	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 LUME	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 PRINGLES	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 GOPRO	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 SONARA	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 VÉLOAP	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 VELORA	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 VEYRO	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 NOVIS AI	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 SINOVIS AI	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 RIVALYN AI	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 ATELIER NORTH	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 NOVARA	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 NEXA ESTATE AI	9.30:1	3.0:1	#000000	#B0ACA6	Pass
h1 Our Craft,	9.30:1	3.0:1	#000000	#B0ACA6	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+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

34 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: 34 all-caps heading(s)

A+

Alt Text Quality

All 16 images OK

PASS

All 16 images OK

16 image(s) with good alt text

16 images 16 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 40 controls labeled

PASS

All 40 controls labeled

40 control(s) properly labeled

40 controls

40 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	checkbox		none
#briefSelectAll	checkbox		none
service	checkbox		none
service	checkbox		none
service	checkbox		none
service	checkbox		none
service	checkbox		none
service	checkbox		none
service	checkbox		none
service	checkbox		none
budget	radio		none
budget	radio		none
budget	radio		none
budget	radio		none
budget	radio		none
timeline	radio		none
timeline	radio		none
timeline	radio		none
timeline	radio		none
timeline	radio		none
name	input	Name *	none
email	email	Email *	none
company	input	Company	none
dialCode	select	Country code	none
phone	tel	Phone (numbers only)	none
description	textarea	What are you trying to build? *	none
reference	url	Reference link (.com only, optional)	none
privacyConsent	checkbox		none
name	input	Full name	none
company	input	Company	none
email	email	Email	none
dialCode	select	Country code	none
phone	tel	Phone (digits)	none
interest	checkbox		none
interest	checkbox		none
interest	checkbox		none
interest	checkbox		none
interest	checkbox		none
message	textarea	Tell us more about your project!	none
privacyConsent	checkbox		none

A

Link & Button Quality

53 links, 138 buttons — all OK

PASS

53 links, 138 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://www.instagram.com/sinvec_sistems/; https://www.facebook.com/Sinvecsystems/

51 link(s) with descriptive text

53 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.instagram.com/sinvec_sistems…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Sinvecsystems/	Facebook	new tab	Add '(opens in new tab)' to text

189 links and buttons have descriptive text

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

https://www.instagram.com/sinvec_sistems/; https://www.facebook.com/Sinvecsystems/

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

A+

Form Input Types

40 form control(s) checked, no type mismatches

PASS

40 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

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

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

PASS

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

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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+

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

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 27 passed

PASS

100

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.

○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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Elements with visible text labels have matching accessible names.

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

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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

○Identical links have the same purpose.

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