Skip to content
https://bookstime.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 header NAV MAIN (missing!) CONTENTINFO footer

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

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
7 of 7 controls have issues
REVIEW
7 of 7 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox">
Warning::
6 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="full_name" id="53193-full_name">; <input type="email" name="email" id="53193-email">; <input type="tel" name="phone" id="53193-phone">; <input type="text" name="full_name" id="1447-full_name">; <input type="email" name="email" id="1447-email">; <input type="tel" name="phone" id="1447-phone">
7 controls
0 labeled
6 placeholder only
1 unlabeled
ControlTypeLabelMethod
#53193-full_nametext(Full Name)placeholder only
#53193-emailemail(Work Email)placeholder only
#53193-phonetel(888-902-6657)placeholder only
#1447-full_nametext(Full Name)placeholder only
#1447-emailemail(Work Email)placeholder only
#1447-phonetel(888-902-6657)placeholder only
inputcheckbox(none)none

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

<input type="checkbox">

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.

<input type="text" name="full_name" id="53193-full_name">; <input type="email" name="email" id="53193-email">; <input type="tel" name="phone" id="53193-phone">; <input type="text" name="full_name" id="1447-full_name">; <input type="email" name="email" id="1447-email">; <input type="tel" name="phone" id="1447-phone">

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | BooksTime ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA
span Industries
1.88:1
#000000
on
#2C3673
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Nonprofits
1.77:1
#000000
on
#24336E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Law Firms
1.56:1
#000000
on
#1E2965
needs 4.5:1 (normal text)
16px · above the fold
a Individuals & Families
1.44:1
#000000
on
#18235D
needs 4.5:1 (normal text)
16px · above the fold
a Real Estate & Property Management
1.53:1
#000000
on
#1E295E
needs 4.5:1 (normal text)
16px · above the fold

1 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)
ElementRatioRequiredFGBGResult
h1 Bookkeeping and Acco…18.31:13.0:1
#000000
#EEEEFF
Pass
h2 Focus On What You Do…18.31:13.0:1
#000000
#EEEEFF
Pass
h2 A Dedicated Bookkeep…18.31:13.0:1
#000000
#EEEEFF
Pass
h2 100% Accuracy Guaran…18.31:13.0:1
#000000
#EEEEFF
Pass
h2 The Trusted Leader18.31:13.0:1
#000000
#EEEEFF
Pass
h2 Client Reviews18.31:13.0:1
#000000
#EEEEFF
Pass
h2 Why Clients Love Boo…18.31:13.0:1
#000000
#EEEEFF
Pass
h2 We Partner With Indu…18.31:13.0:1
#000000
#EEEEFF
Pass
h2 How BooksTime Is Dif…18.31:13.0:1
#000000
#EEEEFF
Pass
h2 Talk To A Bookkeepin…18.31:13.0:1
#000000
#EEEEFF
Pass
h3 Dedicated, Highly Qu…18.31:13.0:1
#000000
#EEEEFF
Pass
h3 Accrual Bookkeeping18.31:13.0:1
#000000
#EEEEFF
Pass
h3 We Do It Your Way18.31:13.0:1
#000000
#EEEEFF
Pass
title BooksTime: Bookkeepi…21.00:14.5:1
#000000
#FFFFFF
Pass
a Services21.00:14.5:1
#000000
#FFFFFF
Pass
span Industries1.88:14.5:1
#000000
#2C3673
Fail
a Nonprofits1.77:14.5:1
#000000
#24336E
Fail
a Law Firms1.56:14.5:1
#000000
#1E2965
Fail
a Individuals & Famili…1.44:14.5:1
#000000
#18235D
Fail
a Real Estate & Proper…1.53:14.5:1
#000000
#1E295E
Fail

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.

B
Lighthouse Accessibility Audits
Score 88/100 — 3 failing, 19 passed
REVIEW
88

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
Inquire Now div.top-line > div.top-line-wrap > div.link-wrap > a.btn-default
PEACE OF MIND GUARANTEED body.home > section.about-wrap > div.about > p.top
Get In Touch section.about-wrap > div.about > div.link-wrap > a.btn-default
Services div.item > div.text-wrap > div.text > a.btn-default
Talk To A BooksTime Bookkeeper div.item > div.text-wrap > div.text > a.btn-default
Read more div.item > div.text-wrap > div.text > a.btn-default
About Us div.item > div.text-wrap > div.text > a.btn-default
bookkeeping div.text-wrap > div.text > p > a
Get A Free Consultation form.cfb-form > div.rendered-form > div.formbuilder-button > button#1447-button-1636626816867
Bookkeeping nav.footer-menu > ul.content-width > li#menu-item-10496 > a
© BooksTime, Inc., 2026. All Rights Reserved. BooksTime is not a CPA firm and d… footer > div.content-width > div.footer-column-1 > div.footer-column-1-desc
Terms and Conditions div.content-width > div.footer-column-1 > div.footer-column-1-links > a.separator-vertical
Privacy Policy div.content-width > div.footer-column-1 > div.footer-column-1-links > a
51 Pleasant St. #740, Malden, MA 02148 div.footer-column-right > div.footer-column-2 > div.footer-column_item > div.footer-column_item-value
2967 Dundas St. W. #613D Toronto, ON M6P 1Z2 div.footer-column-right > div.footer-column-2 > div.footer-column_item > div.footer-column_item-value
learn.more@bookstime.com div.footer-column-right > div.footer-column-2 > div.footer-column_item > div.footer-column_item-value
888-902-6657 div.content-width > div.footer-column-right > div.footer-column-3 > a

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header > div.top-line > div.top-line-wrap > input.icon-menu header > div.top-line > div.top-line-wrap > input.icon-menu

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.js html.js

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>`
●`[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 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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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.
○No element has a `[tabindex]` value greater than 0
○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.
○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 Hierarchy
13 headings
PASS
13 headings
Info::
Single H1 present
  • H1 Bookkeeping and Accounting for Businesses
  • H2 Focus On What You Do Best
  • H2 A Dedicated Bookkeeper Just For You
  • H2 100% Accuracy Guaranteed
  • H2 The Trusted Leader
  • H2 Client Reviews
  • H2 Why Clients Love BooksTime
  • H2 We Partner With Industry Leaders
  • H2 How BooksTime Is Different
  • H3 Dedicated, Highly Qualified Bookkeepers
  • H3 Accrual Bookkeeping
  • H3 We Do It Your Way
  • H2 Talk To A Bookkeeping Expert
A+
Alt Text Quality
All 44 images OK
PASS
All 44 images OK
Info::
44 image(s) with good alt text
44 images 44 good alt text
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback