Skip to main content

Accessibility at Send A Cake

Everyone should be able to browse, personalize and order a cake from us. This page shows how we check our online store for accessibility barriers, what we found, what we fixed and when.

Our commitment

Our goal is for the Send A Cake online store to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. This covers the pages customers use: the home page, product lists, product pages, the cart, checkout and our forms. It is a goal we keep working toward, not a certificate. Automated tools find only part of the possible barriers, so we also test keyboard use and screen reader output by hand when we build a feature.

About WCAG 2.2

Standard
WCAG 2.2, level AA
Automated scan
Every day, at four screen widths
Latest entry in the log
Status of the latest entry
Fixed. A new scan of every page and width is pending; we will add its result to this log.

How we monitor accessibility

We do not wait for complaints. Several checks run on a fixed schedule, and a customer report adds one more.

  • Daily automated scan

    Every day, a scanning tool checks our storefront pages against the WCAG 2.2 A and AA rules. It checks each page at four widths, so phone, tablet and desktop layouts are all covered. Any barrier it finds opens a work item for our web team.

  • Check before release

    Before a storefront change goes live, we scan the page it changes. A new feature must work with the keyboard, show where the focus is, have readable text contrast and respect reduced-motion settings before it is released.

  • Full quarterly scan

    Once per quarter, and after every major storefront redesign, we scan the home page, a category page, a product page, the cart and every checkout step.

  • Shared building blocks

    Menus, lists, tabs and other widgets get their keyboard behavior from one shared accessibility component, so every page behaves the same way.

How we handle an issue

  1. Collect. A scan, an employee or a customer reports a barrier. Each one is tracked as a work item.
  2. Rate. Our web team reproduces the problem and rates it by how much it limits browsing, personalizing and checking out. Barriers that block a purchase are fixed first.
  3. Fix. The fix follows our written accessibility rules and, where the behavior is scripted, comes with an automated test.
  4. Scan again and record. After release we scan again and add the result to the log below, with its date. Entries are added, not rewritten, so the history stays checkable.
  5. Offer another way. If a barrier cannot be fixed at once, we help you finish your order another way, for example by e-mail or phone, and list it under known limitations.

Accessibility log

Newest first. Each entry gives the date, the tool, what was checked, what was found and what we did about it.

– Storefront scan at four screen widths

Barriers fixed after the check of 2026-11-18
What was wrong Where What we did WCAG 2.2 criterion
The cart link in the header had no name that a screen reader could announce on narrow screens. All pages The link now announces "Shopping cart" together with the number of items in it. The cart icon is hidden from screen readers. 2.4.4 Link Purpose, 4.1.2 Name, Role, Value
The name announced for star ratings and for the review count link did not contain the text shown on screen, which makes the links hard to use with voice control. Product lists and product pages The announced names are built from the text that is shown, for example "Rated 4.8 out of 5 stars from 12 reviews". 2.5.3 Label in Name
The small dots under product carousels were smaller than 24 by 24 pixels and hard to tap. Pages with product carousels Every dot now has a 24 by 24 pixel touch area. The dots look the same, and the dot that has keyboard focus shows a ring. 2.5.8 Target Size (Minimum)
Some small texts were too light against their background: the price per piece, the placeholder of select boxes, the review count on the Reviews tab and two hints on the photo upload form. Product lists, select boxes, product pages and the review form The texts use the dark text color of our theme, and the review count uses a dark badge. Every combination now reaches the required 4.5 to 1. 1.4.3 Contrast (Minimum)
The row of thumbnails below a product photo contained elements that screen readers could not announce as part of the list. Product pages Every thumbnail is announced as one list option, and wrapper elements are hidden from screen readers. 1.3.1 Info and Relationships
The photo upload area of the review form was a button that contained another button, which screen readers may not announce correctly. Review and photo upload form The upload area is now a labeled group. The "Select files" button opens the file picker with the keyboard, and dragging photos into the area still works. 4.1.2 Name, Role, Value

– Product page scan

Barriers fixed after the check of 2026-11-17
What was wrong Where What we did WCAG 2.2 criterion
The delivery date field announced features that a plain text field does not have, and the star rating links claimed to be images. Product pages Only the "Choose date" button announces the calendar, and the rating links are announced as links with their rating. 4.1.2 Name, Role, Value
The product photo gallery was announced as a list, but its content was not made of list items. The "Product tags" heading skipped a heading level, and the product info column was announced as a separate page region. Product pages The gallery is a labeled group, the tags heading follows the heading levels of the page, and the info column is no longer a separate region. 1.3.1 Info and Relationships
The current page in the breadcrumb, the active product tab, the tag counts, the prices and the cart badge were too light against their background. Product pages The texts use darker brand colors that reach at least 4.5 to 1. 1.4.3 Contrast (Minimum)

– Home page scan

Barriers fixed after the check of 2026-11-17
What was wrong Where What we did WCAG 2.2 criterion
The slides of the promotion slider and the links over them had no names, and the slide images had no alternative text. Home page Every slide and its link has a name, and the slide images have matching alternative text. 1.1.1 Non-text Content, 2.4.4 Link Purpose
The compare price and the user name and labels of the Instagram feed were too light. Home page The texts use the dark text color of our theme. 1.4.3 Contrast (Minimum)

Known limitations

These items are open or outside our control. We list them so you know where to expect problems.

  • Customer reviews widget. A third party provides the reviews widget and shows it in a frame. Its content is outside our control and our scans cannot read it. We raise issues we find with the provider.