Pricing exploration

A button has no clear name

Text is difficult to read

Interactive controls must not be nested

Link text does not describe its destination

Interactive controls must not be nested

List structure may confuse screen readers

Text is difficult to read

Heading levels skip a rank

Page content has no main landmark

The form requests first name, last name, work email, company website, job level, job function, and country/region before offering the 10-page report.

Immediately below the fields, the form says “You may receive marketing communications from Stripe. You can opt out at any time,” but no marketing preference control is visible in the captured form.

The empty form fields display realistic values such as “Jane,” “Diaz,” “jane@example.com,” and “example.com” on filled gray backgrounds. Even when the first field receives focus, “Jane” remains presented like field content rather than an explicitly labeled example.

The hero action is labeled “Download Report,” but the page later shows a required business-information form before the report can be requested.

Text is difficult to read

List structure may confuse screen readers

Text below 12px

Small tap target

Page content has no main landmark

Heading levels skip a rank

The download form presents seven fields without visible required markers or an upfront note explaining which ones must be completed. The captured markup marks the fields as required.

The first desktop view asks for detailed contact and company information, while the concrete guide contents and outcomes—600+ stores and a 37% order-value increase—appear in the following section below it.

The visible form says, “You may receive marketing communications from Stripe. You can opt out at any time,” but the captured state does not show a visible checkbox or other choice beside that message.

The guide form shows realistic placeholders—“Jane,” “Diaz,” “jane@example.com,” and “example.com”—inside gray-filled inputs. The focused first-name state still makes “Jane” resemble existing field content.

Text is difficult to read

List structure may confuse screen readers

Text below 12px

Page content has no main landmark

The page presents many guides across numerous topic sections, but the captured desktop page shows no visible search, topic filter, or audience filter for narrowing the collection.

Visible cards generally show only a category and title. They do not expose concise comparison details such as content format, publication date, or estimated reading time in the captured card grids.

In the opened Products menu, the top row of column headings—including “Payments,” “Revenue,” and “Money management”—is partially hidden by the header boundary, while the links below remain visible.

Across the captured card grids, guide tiles show category and title but no persistent visible “Read” action, arrow, or other explicit cue that the card opens content.

Control without a label

A link has no clear destination

Text is difficult to read

List structure may confuse screen readers

Page content has no main landmark

The form asks for a password without displaying any length, character, or other acceptance guidance beside the field.

No show-password control appears in or beside the password field in the captured form.

The account-creation dialog is presented over a blurred Stripe dashboard containing navigation, charts, balances, and other account-like information.

Field exposes an internal accessible name

Elements must only use permitted ARIA attributes

Visible page title is not a semantic heading

The results section highlights figures such as “$70M,” “6 months faster,” and “10%,” but the visible summaries do not state the comparison period, baseline, measurement method, or link each result to supporting detail.

The building-together section calls Stripe “the fastest-evolving payments platform” without a visible definition, comparison, timeframe, or supporting evidence.

Several customer-story cards extend beyond the right edge of the captured desktop viewport, while other cards continue below the first screen. The clipped Figma and Lovable cards show only part of their artwork and content.

The Goodtill overview lists Connect and Payments under “Products used,” then collapses another product into the label “1 more.”

The Goodtill case-study summary says “3 weeks” of development work to go live, while the adjacent story card describes onboarding 400+ restaurants in “under 4 weeks.” The visible layout does not explain whether these are the same milestone or separate measures.