Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 4 REVIEW 3 FIX

Tabindex Anti-Patterns

Action

0 positive, 56 -1-on-focusable

FIX

0 positive, 56 -1-on-focusable

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

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 ✗

Mobile Keyboard & Autofill

Action

1/2 eligible field(s) missing autocomplete or inputmode

REVIEW

1/2 eligible field(s) missing autocomplete or inputmode

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email">

Mobile-Readable Font Sizes

97% of visible text renders at >= 12 CSS px (7 below threshold)

REVIEW

97% of visible text renders at >= 12 CSS px (7 below threshold)

7 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 ("PRO"); <span> 11.0px ("PRO"); <span> 11.0px ("Features"); <span> 11.0px ("Solutions"); <span> 11.0px ("Templates").

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Piccap ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

7 icon(s) detected

REVIEW

7 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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

41 headings

PASS

41 headings

Single H1 present

H2 Cookies and site storage
H1 Visualsthat make your point.
H2 What you can get done in Piccap
H3 Win the deal
H3 Report the quarter
H3 Launch a campaign
H3 Hire and onboard
H3 Keep a project on track
H3 Teach a class
H2 Build the deck.Present it here.
H3 Animate what matters
H3 Carry the story from slide to slide
H3 Present or let it play
H2 A template for every deck, document and post
H2 Never start froma blank page
H3 Templates with real content inside
H3 Your PDF or PowerPoint, editable
H3 The right size from the start
H2 Look like you havea design team.
H3 Make any template your own
H3 Turn a spreadsheet into a chart people get
H3 Explain a process or a plan on one page
H3 Keep everyone on brand
H2 Get it in front of people
H3 Hand over the file they asked for
H3 Send a link, not an attachment
H3 Put it on your website and keep it current
H2 Stop emailing files back and forth
H3 Everyone in the same file
H3 One brand for the whole team
H3 Never lose a good version
H2 Everything you make at work, in one place.
H2 Questions? Fair.
H3 Is Piccap really free?+
H3 What do I get with Pro?+
H3 What can I make with Piccap?+
H3 Can I import my existing files?+
H3 Can I present from Piccap?+
H3 Can my team work on it together?+
H3 Can I cancel anytime?+
H2 Make your point with Piccap

A+

Heading Text Quality

All 41 heading(s) have substantive, well-formed text

PASS

All 41 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 118 images OK

PASS

All 118 images OK

118 image(s) with good alt text

118 images 118 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
email	email	Email	aria-label

A+

Link & Button Quality

181 links, 30 buttons — all OK

PASS

181 links, 30 buttons — all OK

181 link(s) with descriptive text

181 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

211 links and buttons have descriptive text

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

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

All form input semantics look correct

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Piccap

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Piccap ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Piccap Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 4 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Dark Mode Support

Full dark mode support

PASS

Full dark mode support

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light dark

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

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 light dark ✓Dark theme-color #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

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)

Element	Ratio	Required	FG	BG	Result
h1 that make your point…	17.83:1	3.0:1	#000000	#EFECE8	Pass
h2 Cookies and site sto…	20.81:1	3.0:1	#000000	#FEFEFD	Pass
h2 What you can get don…	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h2 Build the deck.	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h2 Present it here.	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h2 A template for every…	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h2 Never start from	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h2 a blank page	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h2 Look like you have	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h2 a design team.	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h2 Get it in front of p…	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h2 Stop emailing files …	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h2 Everything you make …	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h2 Questions? Fair.	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h2 Make your point with…	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h3 Win the deal	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h3 Report the quarter	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h3 Launch a campaign	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h3 Hire and onboard	18.17:1	3.0:1	#000000	#F1EEEB	Pass
h3 Keep a project on tr…	18.17:1	3.0:1	#000000	#F1EEEB	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 100/100 — 1 failing, 29 passed

PASS

100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
For sales teams Win the deal Send a proposal or a pitch deck as a link, and se… `main#main > section#jobs > div.gap-5 > a.group`
For finance teams Report the quarter Paste the figures from your spreadsheet, … `main#main > section#jobs > div.gap-5 > a.group`
For marketing teams Launch a campaign Make the post, the story, the banner and… `main#main > section#jobs > div.gap-5 > a.group`
For HR and people teams Hire and onboard Job posts, handbooks and welcome pack… `main#main > section#jobs > div.gap-5 > a.group`
For product and project teams Keep a project on track Roadmaps and status repo… `main#main > section#jobs > div.gap-5 > a.group`
For teachers and schools Teach a class Lessons and lecture decks you animate, … `main#main > section#jobs > div.gap-5 > a.group`
Piccap `footer.mx-auto > div.flex > div.flex > a.flex`

○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

●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

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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.

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

○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

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