Skip to content

Accessibility Statement

We want everyone to be able to use logdart.com. That includes people who use screen readers, keyboards, magnification or voice control, and people browsing on small or old phones.

Our commitment

We work to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the international standard published by the W3C. We don’t always get everything right, so this page also explains what we know isn’t working yet and how to tell us about a problem.

What we've done

  • Pages use proper headings, so screen reader users can jump between sections.
  • Images that carry meaning have text descriptions. Decorative images are hidden from screen readers.
  • Body text meets a contrast ratio of at least 4.5 to 1 against its background.
  • You can reach every link, button and form field with a keyboard, and you can always see where you are.
  • Buttons and links are large enough to tap, at least 24 by 24 pixels.
  • Form fields have visible labels, and error messages say what went wrong and how to fix it.
  • Text can be enlarged to 200% without breaking the layout.
  • Animations calm down if your device asks for reduced motion.

Accessibility options

The round button with the figure of a person, at the right edge of every page, opens a panel of choices. With a keyboard it is the second stop on every page, straight after “Skip to content”. Your choices are remembered in your browser and apply to every page.

  • Text size: normal, larger or largest. The whole page grows together, and nothing is cut off.
  • More spacing: more room between lines, words and letters.
  • Plain typeface: a simple, open typeface in place of the website’s own.
  • Stronger contrast: darker text and lines, and no coloured glow behind the page.
  • No colour: the whole page in shades of grey.
  • Underline links: every link in the text is underlined, so links do not depend on colour.
  • Thick focus ring: a heavy ring around whatever the keyboard or a click has chosen.
  • Large pointer: a pointer about twice the usual size.
  • Reading line: a line across the screen that follows the pointer, to keep your place while reading.
  • Stop movement: nothing on the page moves or changes by itself. The website also follows the “reduce motion” setting of your device without being asked.
  • Listen to this page: reads the main part of the page aloud with the voice built into your browser, saying what each thing is as well as what it says (a heading and its level, a link, a button, a picture and its description, a list and how many items it has, a form field and its name). The passage being read is marked on the page. You can pause, go back or on a passage, stop, and choose a slower or faster voice; a click on any text carries on from there.
  • Speak what I point at: the speaker says whatever the pointer rests on or the Tab key reaches, anywhere on the page. On a touch screen, a touch says it.
  • Both are a help for reading and listening, not a replacement for a screen reader.
  • Reset puts everything back as it was.

The sun-and-moon button in the header switches between a light and a dark page, and the website follows your device’s own setting until you choose.

Using a keyboard

  • Tab and Shift + Tab move forwards and backwards through links, buttons and form fields. The place you are at is marked with a clear ring.
  • Enter follows a link or presses a button. Space presses a button or ticks a box.
  • Skip to content is the first stop on every page and jumps over the menu.
  • Escape closes whatever is open: the services menu, the phone menu, a filter menu, the accessibility options.
  • In the client reviews, the left and right arrow keys move between people, and Home and End go to the first and the last. The reviews stop changing by themselves while the keyboard is on them, and the Pause button stops them for good.

Screen readers

The website is written so that a screen reader can describe it properly:

  • Every page has one main heading, and the headings below it are in order, so a page can be read as an outline or jumped through heading by heading.
  • Every page is divided into named regions (the header with the main menu, the main content, the footer, quick actions), so you can jump from one to the next.
  • Every form field has a name, required fields say “required”, and an error is read out as soon as it appears.
  • Buttons that show only an icon have a spoken name, and a link that opens a new tab says so.
  • When something on the page changes because of what you did (a review, a form being sent, a filter), the change is announced.

These are the screen readers people use most. Several are free or already on your device:

How well the site meets the standard

Every kind of page is checked with an automated accessibility checker, in its light and dark versions and at phone size, and by keyboard.

Automated tools catch only some problems, which is why we also test by hand.

Known issues

These are the problems we know about and what we’re doing about them.

IssueWherePlan
The site has been checked with automated tools and by keyboard, but not yet by people who use a screen reader every dayWhole siteIf you use a screen reader, we'd value hearing how the site works for you
The embedded map can be hard to use with a keyboardContact page, where a map is shownThe address and directions are also given as text beside the map
Text from the translation button comes from Google Translate and may not be accurateEvery pageThe English text is the original

Content from other services

Some parts of the site come from other companies, such as Google Maps, embedded videos and the WhatsApp chat button. We choose these services with accessibility in mind, but we can’t fully control how they work. If one of them causes you a problem, tell us and we’ll help you another way.

Tell us about a problem

If you find something on this site hard to use, or you need information in another format, please let us know:

Tell us the page and what went wrong. We’ll reply within one working day, and we’ll get you the information you need in a way that works for you, even before the page is fixed.

Accessibility in the sites we build

We design and build client websites to WCAG 2.2 level AA as standard, and check them before launch. Accessible sites reach more customers, are easier to use on phones and are easier for search engines to understand. Ask us about an accessibility review of your own website.

About this statement

We review it whenever we make a large change to the website. Questions about it go to the contact details above.

Still have a question?

Ask us directly. A person on our team replies within one working day.