Skip to content

Accessibility statement

We want everyone responsible for a rollout to be able to read this site and judge the toolkit, whatever device or assistive technology they use.

In short

  • The site aims to meet WCAG 2.2 at level AA.
  • Everything works with a keyboard, and nothing depends on animation.
  • Nothing moves by itself if you ask your system for less motion, and the one thing that repeats has a pause button.
  • If something gets in your way, tell us and we will fix it or get you the content another way.

1The standard we aim for

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, for every page of the site. We treat it as a floor that each change has to keep, not as a finished state, and we do not claim that every page meets every criterion.

This statement is our own assessment, made from how the site is built and tested. It is not the result of an independent audit.

2What the site does

  • Keyboard: every link, button, filter, menu and pop-up can be reached and used with the keyboard alone, in the order it is read. A “Skip to content” link is the first stop on every page.
  • Focus: the element that has keyboard focus is outlined with a 3-pixel ring in ink, or in light blue on the dark footer. Headings you jump to stop clear of the bar at the top instead of under it.
  • Structure: each page has one main heading, one banner, one main region and one footer, and every navigation has a name. The current page is marked for assistive technology.
  • Pop-ups: the menu, the filter sheet, the sample pop-up and the checkout are native dialogs. Focus moves into them, Escape closes them, and focus goes back to where you were.
  • Contrast: body and heading text is at least 4.5 to 1 against its ground, and the borders of controls at least 3 to 1. The light blue is never the only sign of a state; it always carries ink as well.
  • Forms: each field of the checkout has a visible label and says in words when it is optional. An error is tied to its field and starts with “Error:”, and a list of the errors at the top of the step leads to each one.
  • Typeface: running text is set in Atkinson Hyperlegible Next, a typeface drawn so that letters and figures that look alike are easy to tell apart.
  • Text size: sizes are set relative to your browser’s own text size, so your setting is respected, and pages reflow to a 320-pixel-wide window without scrolling sideways.
  • Targets: on phones and tablets, buttons and stand-alone links are at least 44 pixels tall.
  • Colour modes: when you ask your system for more contrast, or use forced colours, shadows become solid lines.
  • Without JavaScript: pages are sent complete from the server, so their content can be read, their links work and the free samples open.
  • Language: pages are marked as English so screen readers pronounce them correctly.

3Motion

  • If your system is set to reduce motion, nothing on the site moves by itself: the opening animation does not play and content does not animate in.
  • The first visit to the home page opens with a short animation of the logo, about three seconds long. Any key, press, tap or turn of the wheel ends it at once.
  • A locked template in the catalog shakes for about half a second when it is pressed, to say it is locked. With reduced motion it does not move, and a line of text says the same thing.
  • On the home page, the last word of the headline turns every few seconds, like a departures board, through the blanks a rollout starts from. It turns only while it is in view and the tab is showing, and the Pause button under the headline stops it until you press Play. A screen reader is given the first word alone, and with reduced motion it stands still and the button is not shown.
  • Apart from that word, no animation on the site repeats, and none flashes.

4Known limitations

We know about these gaps and would rather say so than have you find them:

  • The toolkit’s files are Word, PowerPoint, Excel and PDF documents meant to be edited. We have not checked each one against a document accessibility standard, and how accessible your adapted versions are depends on the changes you make.
  • We have not tested every page with every combination of screen reader, browser and voice control software, so a fault may exist that our checks did not find.
  • The covers of templates in the catalog are small pictures of a page. Their content is decoration; each template’s title, description and details are given as text beside the cover.
  • Without JavaScript, controls that open a panel, such as the phone menu and the catalog’s filter sheet, may not respond. The pages and their links still work.
  • The site is in English only.
  • The checkout does not take payment yet. The payment step that a processor will add is not built, and will be held to the same standard and covered by this statement when it is.

5How we check

Accessibility is checked as the site is built, not afterwards. Automated tests run in desktop and phone browsers. Among other things they check for one main heading per page, visible focus rings, target sizes, pages that fit windows from 320 pixels wide up to large monitors, and that the site is complete and still with reduced motion, with more contrast and without JavaScript.

A further check stops colours from being written outside the one set whose contrast has been measured.

6Report a barrier

If any part of the site is hard or impossible for you to use, or you need something from it in another form, write to hello@advanta365.com or use the Contact page. It helps to tell us:

  • the address of the page;
  • what you were trying to do and what happened;
  • the browser and any assistive technology you were using.

A barrier that stops someone from using the site is treated as a fault to fix, not as a request.

7About this statement

This statement covers the Advanta365 website. It is reviewed when the site changes in a way that affects it, and the date at the top of the page shows when it last changed.

See also the Privacy policy, the Terms of use and licence and the Refund policy.