Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 REVIEW 7 FIX

Landmark Structure

Action

2 landmarks

FIX

2 landmarks

No <main> landmark found

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

No <nav> landmark found

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

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

Heading Hierarchy

Action

127 headings, 2 skip(s)

FIX

127 headings, 2 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

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.

H2 Explore Categories
H2 Master DSA Topics - April, 2026
H3 DSA Learning
H3 AI ResumeBuilder
H3 Online SQLEditor
H3 CodingGround
H3 Top InterviewQuestions
H3 Cheetsheet NEW
H3 Python
H3 Linked List
H3 Tree
H3 Graph Algorithms
H3 Sorting Algorithms
H3 Recursion
H4 Array
H4 String
H4 Hash Table
H4 Dynamic Programming
H4 Sorting
H4 Greedy
H4 Depth-First Search
H4 See All Topics
H4 Array
H4 String
H4 Hash Table
H4 Math
H4 Dynamic Programming
H4 Sorting
H4 Greedy
H4 Depth-First Search
H4 Database
H4 Binary Search
H4 Matrix
H4 Tree
H4 Bit Manipulation
H4 Breadth-First Search
H4 Two Pointers
H4 Prefix Sum
H4 Heap (Priority Queue)
H4 Simulation
H4 Binary Tree
H4 Stack
H4 Graph
H4 Counting
H4 Sliding Window
H4 Design
H4 Enumeration
H4 Backtracking
H4 Union Find
H4 Linked List
H4 Number Theory
H4 Ordered Set
H4 Monotonic Stack
H4 Segment Tree
H4 JavaScript
H4 Trie
H4 Combinatorics
H4 Bitmask
H4 Recursion
H4 Divide and Conquer
H4 Queue
H4 Memoization
H4 Binary Indexed Tree
H4 Geometry
H4 Binary Search Tree
H4 Hash Function
H4 String Matching
H4 Topological Sort
H4 Shortest Path
H4 Rolling Hash
H4 Game Theory
H4 Interactive
H4 Data Stream
H4 Monotonic Queue
H4 Brainteaser
H4 Doubly-Linked List
H4 Randomized
H4 Merge Sort
H4 Counting Sort
H4 Iterator
H4 Concurrency
H4 Line Sweep
H4 Probability & Statistics
H4 Suffix Array
H4 Quickselect
H4 Minimum Spanning Tree
H4 Bucket Sort
H4 Pandas
H4 Reservoir Sampling
H4 Shell
H4 Eulerian Circuit
H4 Strongly Connected Component
H4 Radix Sort
H4 Collapse
H2 All Coding Problems
H2 Tutorials Library
H4 Python Tutorial skipped
H4 Java Tutorial
H4 JavaScript
H4 C++ Tutorial
H4 C# Tutorial
H4 Go Tutorial
H4 Rust Tutorial
H4 TypeScript
H4 Swift Tutorial
H4 Kotlin Tutorial
H4 Ruby Tutorial
H4 PHP Tutorial
H4 C Tutorial
H4 Scala Tutorial
H4 Perl Tutorial
H4 R Tutorial
H4 Dart Tutorial
H4 Lua Tutorial
H4 MATLAB
H4 Haskell
H2 Developer Toolbox
H4 AI Resume Builder skipped
H4 JS Minifier
H4 Whiteboard
H4 Image Editor
H4 Doc Viewer
H4 LaTeX Editor
H4 JSON Editor
H4 QR Generator
H4 View All
H2 Start Coding in Seconds

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

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.

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.

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 ✗

Alt Text Quality

4 of 25 images have issues

REVIEW

4 of 25 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image(s) with generic alt text

21 image(s) with good alt text

25 images 21 good alt text 2 generic 2 missing

Issue	Count
missing	2 image(s)
generic	2 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

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

1 control(s) without accessible label

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

Got: <select id="topicFilter">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" id="problemSearch">

2 controls

0 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#problemSearch	text	(Search problems...)	placeholder only
#topicFilter	select	(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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

Action

3 issue(s) across 220 links and 13 buttons

REVIEW

3 issue(s) across 220 links and 13 buttons

1 link(s) with no accessible text

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

Got: /company/all/2

17 link(s) open in new tab without warning

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

Got: https://www.facebook.com/tutorialspointindia; https://x.com/tutorialspoint; https://www.youtube.com/channel/UCVLbzhxVTiTLiVKeGV7WEBg; https://www.linkedin.com/company/tutorialspoint/; https://www.instagram.com/tutorialspoint_/; /online_java_compiler.php; /online_java_compiler.php; /online_python_compiler.php; /compile_cpp_online.php; /online_html_editor.php (+7 more)

2 button(s) with no accessible text

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

Got: button.tp-theme-toggle (#73 on page); button.tp-categories-close (#123 on page)

202 link(s) with descriptive text

220 links

1 empty

0 generic text

17 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/tutorialspointi…	Facebook	new tab	Add '(opens in new tab)' to text
https://x.com/tutorialspoint	X	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCVLbzhx…	YouTube	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/tutoria…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/tutorialspoint…	Instagram	new tab	Add '(opens in new tab)' to text
/company/all/2	(empty)	empty	Add link text or aria-label
/online_java_compiler.php	Edit & Run	new tab	Add '(opens in new tab)' to text
/online_java_compiler.php	Java Compiler	new tab	Add '(opens in new tab)' to text
/online_python_compiler.php	Python Compiler	new tab	Add '(opens in new tab)' to text
/compile_cpp_online.php	C++ Compiler	new tab	Add '(opens in new tab)' to text
/online_html_editor.php	HTML Editor	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/tutorialspointi…	Follow us on Facebook	new tab	Add '(opens in new tab)' to text
https://x.com/tutorialspoint	Follow us on X	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCVLbzhx…	Follow us on Youtube	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/tutoria…	Follow us on LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/tutorialspoint…	Follow us on Instagram	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Download Android App	new tab	Add '(opens in new tab)' to text
https://itunes.apple.com/us/app/tutorial…	Download IOS App	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

213 links and buttons have descriptive text

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

/company/all/2

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://www.facebook.com/tutorialspointindia; https://x.com/tutorialspoint; https://www.youtube.com/channel/UCVLbzhxVTiTLiVKeGV7WEBg; https://www.linkedin.com/company/tutorialspoint/; https://www.instagram.com/tutorialspoint_/; /online_java_compiler.php; /online_java_compiler.php; /online_python_compiler.php; /compile_cpp_online.php; /online_html_editor.php (+7 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.tp-theme-toggle (#73 on page); button.tp-categories-close (#123 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

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 Page Not Found - Tutorialspoint ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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 1 pass AA only

h3 AI Resume

1.09:1

#FFFFFF

#F5F5F5

needs 3.0:1 (large text)

19px · bottom of viewport · over background image/gradient

h3 Builder

1.09:1

#FFFFFF

#F5F5F5

needs 3.0:1 (large text)

19px · bottom of viewport · over background image/gradient

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Explore	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 Master	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 All	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 Tutorials	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 Developer	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 DSA Learning	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 AI Resume	1.09:1	3.0:1	#FFFFFF	#F5F5F5	Fail
h3 Builder	1.09:1	3.0:1	#FFFFFF	#F5F5F5	Fail
h3 Online SQL	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Editor	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 CodingGround	3.48:1	3.0:1	#E65100	#F5F5F5	Pass
h3 Top Interview	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Questions	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Cheetsheet	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Python	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Linked List	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Tree	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Graph Algorithms	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Sorting Algorithms	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Recursion	19.26:1	3.0:1	#000000	#F5F5F5	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.

Lighthouse Accessibility Audits

Action

Score 73/100 — 8 failing, 23 passed

REVIEW

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