Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 6 REVIEW 6 FIX

Landmark Structure

Action

No landmarks

FIX

No 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

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Document Language

Action

Missing <html lang> attribute (WCAG 3.1.1)

FIX

Missing <html lang> attribute (WCAG 3.1.1)

Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.

Favicon & Branding

Action

3 icon(s) detected

FIX

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

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

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

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 ✗

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Link & Button Quality

Action

5 issue(s) across 17 links and 0 buttons

REVIEW

5 issue(s) across 17 links and 0 buttons

5 link(s) with no accessible text

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

Got: ./#hero; https://wa.me/919326549168; https://Instagram.com/studiopravahamumbai; mailto:studiopravaha@gmail.com; https://www.facebook.com/studiopravaha/

3 link(s) open in new tab without warning

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

Got: https://maps.app.goo.gl/qijDSxo4VeQnN8HcA; ./#features-facilities; ./#gallery

9 link(s) with descriptive text

17 links

5 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://maps.app.goo.gl/qijDSxo4VeQnN8Hc…	Track on maps	new tab	Add '(opens in new tab)' to text
./#hero	(empty)	empty	Add link text or aria-label
./#features-facilities	Facilities	new tab	Add '(opens in new tab)' to text
./#gallery	Gallery	new tab	Add '(opens in new tab)' to text
https://wa.me/919326549168	(empty)	empty	Add link text or aria-label
https://Instagram.com/studiopravahamumba…	(empty)	empty	Add link text or aria-label
mailto:studiopravaha@gmail.com	(empty)	empty	Add link text or aria-label
https://www.facebook.com/studiopravaha/	(empty)	empty	Add link text or aria-label

9 links and buttons have descriptive text

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

./#hero; https://wa.me/919326549168; https://Instagram.com/studiopravahamumbai; mailto:studiopravaha@gmail.com; https://www.facebook.com/studiopravaha/

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://maps.app.goo.gl/qijDSxo4VeQnN8HcA; ./#features-facilities; ./#gallery

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found | Framer ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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 Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA 1 pass AA only

title Studio Pravaha

3.21:1

#000000

#6B5C36

needs 4.5:1 (normal text)

16px · top of page (header area)

p Find Your Flow

3.11:1

#000000

#695A35

needs 4.5:1 (normal text)

16px · top of page (header area)

p Space to create

3.09:1

#000000

#6A5934

needs 4.5:1 (normal text)

16px · top of page (header area)

p Room to breathe

3.11:1

#000000

#6C5933

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title Studio Pravaha	3.21:1	4.5:1	#000000	#6B5C36	Fail
p Find Your Flow	3.11:1	4.5:1	#000000	#695A35	Fail
p Space to create	3.09:1	4.5:1	#000000	#6A5934	Fail
p Room to breathe	3.11:1	4.5:1	#000000	#6C5933	Fail
p A versatile studio w…	18.12:1	4.5:1	#000000	#EFEEED	Pass
p Explore Facilities	19.30:1	4.5:1	#000000	#F6F5F5	Pass
p Book Your Session	20.65:1	4.5:1	#000000	#FDFDFD	Pass
a About	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Facilities	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Gallery	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Testimonials	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Contact	19.25:1	4.5:1	#000000	#F5F5F4	Pass
p The Pravaha Philosop…	14.02:1	4.5:1	#000000	#D3D3D2	Pass
p Welcome to Studio Pr…	16.52:1	4.5:1	#000000	#E4E4E4	Pass
p As the name suggests…	19.25:1	4.5:1	#000000	#F5F5F4	Pass
span flow	17.44:1	4.5:1	#000000	#EAEAE9	Pass
p without limits. Whet…	19.08:1	4.5:1	#000000	#F4F4F3	Pass
p Equipped with profes…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Our aim is to provid…	6.03:1	4.5:1	#000000	#D66B3D	Pass
p We believe every pro…	10.19:1	4.5:1	#000000	#E6A68B	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 72/100 — 5 failing, 11 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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
div.framer-ekaazv > div.framer-3whdvs > div.framer-1f046o > a.framer-kpwz4k `div.framer-ekaazv > div.framer-3whdvs > div.framer-1f046o > a.framer-kpwz4k`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Book Your Session `a.framer-1jqdh3n > span.framer-1s62riu > div.framer-7q5q6d > p.framer-text`

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.framer-3whdvs > div.framer-1uouahp > div.framer-yncrk5 > a.framer-1lpvjk0 `div.framer-3whdvs > div.framer-1uouahp > div.framer-yncrk5 > a.framer-1lpvjk0`
div.framer-3whdvs > div.framer-1uouahp > div.framer-yncrk5 > a.framer-26eobx `div.framer-3whdvs > div.framer-1uouahp > div.framer-yncrk5 > a.framer-26eobx`
div.framer-3whdvs > div.framer-1uouahp > div.framer-yncrk5 > a.framer-i7j43i `div.framer-3whdvs > div.framer-1uouahp > div.framer-yncrk5 > a.framer-i7j43i`
div.framer-3whdvs > div.framer-1uouahp > div.framer-yncrk5 > a.framer-qichi1 `div.framer-3whdvs > div.framer-1uouahp > div.framer-yncrk5 > a.framer-qichi1`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

●`button`, `link`, and `menuitem` elements have accessible names

●Document has a `<title>` element

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

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

●The page contains a heading, skip link, or landmark region

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○ARIA attributes are used as specified for the element's role

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

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

○Heading elements appear in a sequentially-descending order

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

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

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

A+

Heading Text Quality

No headings to evaluate -- check is N/A

PASS

No headings to evaluate -- check is N/A

Alt Text Quality

12 of 22 images have issues

PASS

12 of 22 images have issues

12 image(s) with generic alt text

10 decorative image(s) correctly marked

22 images 10 decorative 12 generic

Issue	Count
generic	12 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Tabindex Anti-Patterns

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

PASS

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

No tabindex anti-patterns detected

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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

All 72 visible text node(s) render at >= 12 CSS pixels

PASS

All 72 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

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.

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