Skip to content
https://studyguidemaker.net

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
85
GRADE
B
FIX
3
REVIEW
4
PASS
17
INFO
0
Checks
24
17 PASS 4 REVIEW 3 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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
No navigation patterns
FIX
No navigation patterns
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
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
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Warning::
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
BANNER (missing!) NAV MAIN CONTENTINFO footer

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

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

B
Mobile-Readable Font Sizes
97% of visible text renders at >= 12 CSS px (8 below threshold)
REVIEW
97% of visible text renders at >= 12 CSS px (8 below threshold)
Info::
8 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: <span> 11.0px ("Plus / Pro"); <span> 11.0px ("p. 1"); <span> 11.0px ("p. 1"); <span> 11.0px ("p. 2"); <span> 11.0px ("p. 2").
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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.

A+
Heading Hierarchy
45 headings
PASS
45 headings
Info::
Single H1 present
  • H1 AI Study Guide Maker
  • H2 See what your study guide looks like
  • H3 Cellular Respiration
  • H4 1. Overview of cellular respiration
  • H4 2. Glycolysis
  • H4 3. Krebs (citric acid) cycle
  • H4 4. Electron transport chain
  • H2 One complete guide for every exam
  • H2 How to make a study guide with AI in 3 steps
  • H3 Add your material
  • H3 Generate your guide
  • H3 Study, print, or share
  • H2 Why students and teachers choose Study Guide Maker
  • H3 No sign-up and no paywall to get started.
  • H3 Cited directly to your pages.
  • H3 Print-ready PDF & Word exports.
  • H3 Active recall built in.
  • H3 Teacher mode.
  • H3 Honest, straightforward pricing.
  • H2 Create a study guide from any material
  • H2 Who it's for
  • H2 AI study guide maker vs. manual study vs. general chatbots
  • H2 What students and teachers say
  • H2 Simple, transparent pricing
  • H3 Student Plus
  • H3 Student Pro
  • H3 Semester Pass
  • H2 More study tools
  • H2 Start from your subject or file
  • H2 From the blog
  • H3 AP Biology Study Guide: How to Build One Unit by Unit (May 2027 Exam)
  • H3 Best AI Study Guide Makers in 2026: An Honest Comparison
  • H3 How to Make a Study Guide from a PDF (Textbook Chapters, Slides & Readings)
  • H2 AI study guide maker FAQ
  • H3 What is an AI study guide maker?
  • H3 Is it really free? Do I need to sign up?
  • H3 What files can I make a study guide from?
  • H3 Can I make a study guide from a PDF or PowerPoint?
  • H3 How is a study guide different from a summary?
  • H3 Can I print it or download it as a PDF or Word file?
  • H3 How accurate is it? Does it cite sources?
  • H3 Can teachers use it to make study guides for students?
  • H3 Is my uploaded content private?
  • H3 Is using an AI study guide maker cheating?
  • H2 Your next exam, organized in one place.
A+
Heading Text Quality
All 45 heading(s) have substantive, well-formed text
PASS
All 45 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 8 images OK
PASS
All 8 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
7 image(s) with good alt text
8 images 7 good alt text
IssueCount
too long1 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#sgm-filefileDrop a file to get startedPDF, PPTX, DOCX, or TXT · up to 3 files · up to 20 pages free (combined). Nothing here yet — upload your material, or tap an example below to see a complete sample guide.Multiple files are merged in order into one study guideChoose filesnone
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Study Guide Maker
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Study Guide Maker ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Study Guide Maker Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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)
ElementRatioRequiredFGBGResult
h1 Maker20.41:13.0:1
#000000
#FFFBF8
Pass
h2 See what your study …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 One complete guide f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 How to make a study …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why students and tea…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Create a study guide…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Who it's for21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AI study guide maker…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What students and te…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Simple, transparent …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 More study tools21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Start from your subj…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 From the blog21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AI study guide maker…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your next exam, orga…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cellular Respiration21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Add your material21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Generate your guide21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Study, print, or sha…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 No sign-up and no pa…21.00:13.0: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 97/100 — 1 failing, 30 passed
PASS
97

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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Study Tips div.relative > div.absolute > div.flex > span.text-xs
Study Tips div.relative > div.absolute > div.flex > span.text-xs
Study Tips div.relative > div.absolute > div.flex > span.text-xs

These are opportunities to improve the legibility of your content.

○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
●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
●`[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
●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
●Document has a `<title>` element
●`<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.
●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
●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.
○`[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 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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback