Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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

Theme color only

FIX

Theme color only

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: #ffffff

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 ModePartial Dark Mode

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 ✗

Landmark Structure

7 landmarks

REVIEW

7 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) 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.

Search landmark present

Page Structure — as a screen reader sees it

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

Form Accessibility

Action

12 of 17 controls have issues

REVIEW

12 of 17 controls have issues

12 control(s) without accessible label

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

Got: <input type="image">; <input type="image">; <input type="image">; <input type="image">; <input type="image">; <input type="image">; <input type="image">; <input type="image">; <input type="image">; <input type="image"> (+2 more)

5 control(s) properly labeled

17 controls

5 labeled

0 placeholder only

12 unlabeled

Control	Type	Label	Method
input	image	Search	aria-label
#bq-search-input	text	Search on BrainyQuote	aria-label
input	image	Search	aria-label
#bq-search-input-mbl-por	text	Search on BrainyQuote	aria-label
#hmSearch	text	Search on BrainyQuote	aria-label
input	image	(none)	none
input	image	(none)	none
input	image	(none)	none
input	image	(none)	none
input	image	(none)	none
input	image	(none)	none
input	image	(none)	none
input	image	(none)	none
input	image	(none)	none
input	image	(none)	none
input	image	(none)	none
input	image	(none)	none

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

<input type="image">; <input type="image">; <input type="image">; <input type="image">; <input type="image">; <input type="image">; <input type="image">; <input type="image">; <input type="image">; <input type="image"> (+2 more)

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

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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

title Inspirational Quotes at BrainyQuote

2.27:1

#000000

#2F418E

needs 4.5:1 (normal text)

16px · top of page (header area)

div Site

2.27:1

#000000

#2F418E

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Inspirational Quotes…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Popular Topics	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Popular Authors	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 In the News	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Today's Birthdays	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Picture Quotes -	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Explore Inspirationa…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Quote Of The Day Fee…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Site	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 About	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Apps	18.76:1	3.0:1	#000000	#F2F2F2	Pass
title Inspirational Quotes…	2.27:1	4.5:1	#000000	#2F418E	Fail
div Site	2.27:1	4.5:1	#000000	#2F418E	Fail
a Home	19.77:1	4.5:1	#000000	#F8F8F8	Pass
a Authors	19.09:1	4.5:1	#000000	#F4F4F4	Pass
a Topics	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a Quote Of The Day	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a Top 100 Quotes	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a Professions	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a Birthdays	18.76:1	4.5:1	#000000	#F2F2F2	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 Hierarchy

11 headings

PASS

11 headings

Single H1 present

H1 Inspirational Quotes at BrainyQuote
H2 Popular Topics
H2 Popular Authors
H2 In the News
H2 Today's Birthdays
H2 Picture Quotes -
H2 Explore Inspirational Quotes by Famous Authors
H3 Quote Of The Day Feeds
H3 Site
H3 About
H3 Apps

A+

Alt Text Quality

All 16 images OK

PASS

All 16 images OK

1 decorative image(s) correctly marked

15 image(s) with good alt text

16 images 15 good alt text 1 decorative

All images have appropriate alt text.

Link & Button Quality

222 links, 1 buttons — all OK

PASS

222 links, 1 buttons — all OK

10 link(s) open in new tab without warning

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

Got: https://www.facebook.com/BrainyQuote; https://twitter.com/brainyquote; https://www.instagram.com/brainyquote/; https://www.facebook.com/BrainyQuote; https://twitter.com/brainyquote; https://pinterest.com/brainyquote/; https://www.facebook.com/BrainyQuote; https://twitter.com/brainyquote; https://pinterest.com/brainyquote; https://instagram.com/brainyquote

212 link(s) with descriptive text

222 links

0 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/BrainyQuote	Follow us on Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/brainyquote	Follow us on X	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/brainyquote/	Follow us on Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/BrainyQuote	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/brainyquote	X	new tab	Add '(opens in new tab)' to text
https://pinterest.com/brainyquote/	Pinterest	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/BrainyQuote	Follow us on Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/brainyquote	Follow us on X	new tab	Add '(opens in new tab)' to text
https://pinterest.com/brainyquote	Follow us on Pinterest	new tab	Add '(opens in new tab)' to text
https://instagram.com/brainyquote	Follow us on Instagram	new tab	Add '(opens in new tab)' to text

213 links and buttons have descriptive text

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

https://www.facebook.com/BrainyQuote; https://twitter.com/brainyquote; https://www.instagram.com/brainyquote/; https://www.facebook.com/BrainyQuote; https://twitter.com/brainyquote; https://pinterest.com/brainyquote/; https://www.facebook.com/BrainyQuote; https://twitter.com/brainyquote; https://pinterest.com/brainyquote; https://instagram.com/brainyquote

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

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 26 passed

PASS

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Facebook `div.homeGridBox > div.homePictureQuotesTitleBlock > p > a`
X `div.homeGridBox > div.homePictureQuotesTitleBlock > p > a`
Pinterest `div.homeGridBox > div.homePictureQuotesTitleBlock > p > a`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Iggy Pop `tr > td > div.bqLn > a.bq_on_link_cl`
Franklin P. Jones `tr > td > div.bqLn > a.bq_on_link_cl`

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-*]` 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

●`<input type="image">` elements have `[alt]` text

●Form elements have associated labels

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

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

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

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