7 pages · airbnb.com · shared view
The experience works, but decision-making, accessibility and visual hierarchy need attention in key moments.
Hotel photos are replaced by blank gray blocks
In the “Great hotels for your next trip” row, all seven visible cards show uniform gray image areas while the Virginia Beach cards immediately above display photos.
The Airbnb credit offer lacks decision-making details
The hotel section says “Plus, get Airbnb credit when you stay at a featured hotel,” but the visible section does not state the credit amount, how it is calculated, or indicate terms near the claim.
“Plus, get Airbnb credit when you stay at a featured hotel.”
Several article cards have blank image areas
In the captured full-page state, multiple cards reserve large thumbnail areas but show only white space. This is visible in “Get started as a host,” “Your Airbnb tools,” “Make hosting easier,” and “Grow your business,” while neighboring cards display images or play icons.
The featured fee story has no visible summary
The lead feature presents “Simplifying service fees,” a large product image, and the generic action “Get details,” but no visible sentence explaining what changed, who it affects, or what the article will clarify.
Most topic cards provide only a title
The featured tool cards include short descriptions, but the subsequent topic rows generally show only article titles such as “Preparing your space,” “Reviewing your price,” and “Managing your prices.”
ARIA progressbar nodes must have an accessible name
ARIA progressbar nodes must have an accessible name
WCAG 1.1.1
Most of the page is empty after the first listing rows
The captured full-page desktop view shows the Photography and Chefs rows followed by two nearly entire viewport bands of blank white space. No loading, empty-state, or error message explains the gap.
Ratings omit the number of reviews
Visible service cards show an average such as “5.0,” but none of the displayed cards include a review count. Many cards therefore present the same perfect score without indicating how much feedback supports it.
Service results have no visible way to narrow or sort them
The Services page provides category shortcuts and separate rows, but the captured browse state shows no visible filters or sorting for price, rating, booking unit, or minimum spend. Photography alone presents prices from $60 to $600 using both per-guest and per-group units.
Page has no h1
Page has no h1
“Services in Leesburg”
ARIA hidden element must not be focusable or contain focusable elements
ARIA hidden element must not be focusable or contain focusable elements
WCAG 4.1.2
AI introduction blocks the Help Center on arrival
The initial desktop state is covered by a large modal that dims the question field, suggested topics, and article navigation. It promotes the same AI question experience already visible underneath and requires either “Try it now” or the small close control before users can access the page.
Visible page title is not a semantic heading
Visible page title is not a semantic heading
“Get answers, instantly”
The video pushes the article’s purpose below the fold
The desktop page opens with a very large video occupying most of the first viewport. The article title, summary, author, and explanation begin below it, so the page initially looks more like a video landing page than a time-sensitive service-fee guide.
“Simplifying service fees on Airbnb”
The deadline omits the year and expired-date status
The article says the deadlines are “September 15” and “October 13” without a year. As captured on September 16, 2026, the first date has passed, but the copy still presents both as upcoming deadlines and the CTA remains generic.
“Get started” hides the action it will open
After explaining that hosts need to adjust prices, the only primary action is labeled “Get started.” Its label does not say that it opens the price-adjustment flow or distinguish it from starting to host.
“Get started”
The pricing example rounds away a meaningful payout difference
The article says a $115 price with a 15.5% fee leaves the host earning $97. A later VAT example shows cents precisely as $97.60, but the initial calculation does not explain that its $97 result is rounded.
The audience figures overstate the evidence for service demand
Under “Welcome a world of new customers,” the page highlights 390 million guests and $81 billion spent. The small footnote clarifies that the spending figure covers stays and experiences, not Airbnb Services specifically.
“$81 billion”
Nail services disappear from the category showcase
The visual category grid shows Catering, Chefs, Hair styling, Makeup, Massage, Personal training, Photography, Prepared meals, and Spa treatments, but no Nails category. Elsewhere in the supplied page content, Nails is listed as an included service.
The top signup action appears before key application conditions
A prominent “Get started” action appears at the top, while the review timeline, possible waitlist, licensing requests, insurance requirement, and 15% service fee are disclosed much later in the FAQ.
ARIA progressbar nodes must have an accessible name
ARIA progressbar nodes must have an accessible name
WCAG 1.1.1
The main search field does not say what it searches
The prominent header field uses only the placeholder “Start your search,” without naming jobs or suggesting searchable criteria such as role, team, or location.
The department browser is squeezed into a narrow strip
In the “Open the door to your next role” section, the department links occupy a much narrower column than the neighboring cards. Only six department names are visibly readable in the captured area even though the card headline says there are 25 departments, and the navigation controls sit at the section’s lower edge.
Runtime failures on page load
Runtime failures on page load
Text is difficult to read
Text is difficult to read
WCAG 1.4.3