new update in Velobet: account blocked and £11,965 held for an investigation with no reason given · 11 hours ago
Thanks for the update, Velobet. As the player says, please use my email for anything you want to send.
Read the threadFruitMachineCritic should work for everyone, including people who use a keyboard, a screen reader or a phone. This statement explains the standard we work to, what we found when we checked the site and how to tell us about a problem.
+Read more

Information about online gambling, its risks and where to get help should be easy to reach for everyone in the UK. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We checked the pages listed under Compliance Status ourselves, as described there. Where the site doesn’t meet the standard yet, we say so in the list of known issues below.
Under the Equality Act 2010, which applies in England, Scotland and Wales, a person providing a service to the public, for payment or not, must not discriminate against a person who needs the service, and must make reasonable adjustments for disabled people; for information, that includes providing it in an accessible format. We aim to meet those duties.
WCAG is the international standard for accessible web content, published by the World Wide Web Consortium (W3C). Version 2.2 extends WCAG 2.1, and content that meets 2.2 also meets 2.0 and 2.1. The guidelines rest on four principles:
Perceivable: you can see, hear or otherwise take in the content, for example through text alternatives for images and enough colour contrast.
Operable: you can use every menu, button and link, including with a keyboard alone.
Understandable: text is readable and the site behaves in ways you can predict.
Robust: the code works with browsers and assistive technologies such as screen readers.
Under these principles sit 13 guidelines, each with testable success criteria at three levels:
| Level | What it means |
|---|---|
| A | The minimum level: a page meets every Level A criterion. |
| AA | A page meets every Level A and Level AA criterion. This is our target. |
| AAA | A page also meets every Level AAA criterion. The W3C itself doesn’t recommend requiring AAA for whole sites, because some content can’t meet all of it. |
WCAG 2.2 added new criteria, such as Focus Not Obscured (Minimum), Target Size (Minimum) and Accessible Authentication (Minimum), and removed one old criterion, 4.1.1 Parsing.
Accessible design matters for people with:
Low vision or blindness: pale text, images without descriptions and pages that only make sense visually.
Limited movement: controls that only work with a mouse, or targets too small to tap.
Deafness or hearing loss: video or audio without captions or transcripts.
Cognitive or learning disabilities: long, complex wording and layouts that change from page to page.
Older or simpler devices: layouts that break on small screens or when text is enlarged.
Every page has the same layout: menu at the top, one main heading, sections with clear subheadings, and the footer with contacts and help lines at the bottom.
Pages use standard header, navigation, main and footer areas, so screen reader users can jump between them.
Images have text alternatives: our check of 22 pages found no image without one.
The layout adapts to narrow screens and zooming is not blocked. At phone width (390 pixels) none of the pages we checked scrolled sideways.
Phone numbers for help services are tap-to-call links.
Each page declares its language as British English, so screen readers use the right pronunciation.
Links, buttons and form fields have names that screen readers can announce.
Our log-in and sign-up forms have a visible label for every field.
We write in plain English with short sentences.
Key facts such as help lines and legal limits are written as text, not shown only in images.
We don’t publish video or audio at the moment. If we add video or audio, we aim to include captions or a transcript.
FruitMachineCritic is partially conformant with WCAG 2.2 Level AA. Under WCAG, a page conforms to a level only if it meets every criterion of that level. In our check, 1 of the 22 pages we checked had no automated failures. The remaining failures are mostly small grey text with too little contrast on our tools and forum pages.
How we checked: we ran the automated checker axe-core 4.10.2 at desktop width (1366 pixels) and phone width (390 pixels) on these 22 pages:
all six tools: Casino Sign-up Bonuses, Highest RTP Slots, Casino Calculators, Find My Casino, Compare All Casinos and Compare 2 Casinos;
the forum main page and the sign-up and log-in pages;
our author page and our policy pages: Advertising Disclosure, Editorial Principles, How We Rate Casinos, Privacy Policy, Security Policy, Comments and Community Policy, Cookies Policy, Terms and Conditions and this Accessibility Statement.
An automated checker can’t test everything. We have not yet tested with screen reader users or other people with disability, and we have not yet done a full keyboard-only review of every page.
| Where | Problem | WCAG criterion |
|---|---|---|
| Every page except Log in (the forum teaser above the footer) | The “Visit the forum” link (4.45:1) and the grey “new update in …” line (3.43:1) have too little contrast, where 4.5:1 is needed. | 1.4.3 Contrast (Minimum) (AA) |
| Tools: Casino Sign-up Bonuses, Highest RTP Slots, Casino Calculators, Compare All Casinos, Compare 2 Casinos | Small grey text has too little contrast (2.99:1 to 3.43:1): result counts, provider names, field labels and the unselected calculator tabs. | 1.4.3 Contrast (Minimum) (AA) |
| Forum main page | Grey column headings (2.99:1) and some small grey text have too little contrast. | 1.4.3 Contrast (Minimum) (AA) |
| Sign-up page | The password hint “At least 8 characters.” has too little contrast (3.43:1). | 1.4.3 Contrast (Minimum) (AA) |
| Highest RTP Slots, on phones | The wide slots table can’t be reached or scrolled with a keyboard. | 2.1.1 Keyboard (A) |
| Home page, Compare All Casinos | One column heading in a table is empty, so screen readers announce nothing for that column. | Best practice |
| Compare All Casinos | Each casino logo repeats the casino’s name as its text alternative, so a screen reader may read the name twice. | Best practice |
| Casino Sign-up Bonuses, forum main page | Heading levels skip a step (for example, a level 3 heading straight after the page title). | Best practice |
| About Us, How We Rate Casinos, and other pages with the author card | The author card heading (“Meet …”) is a level 4 heading straight after a level 2 heading. | Best practice |
| Pages with the “Would you recommend this page?” box | The box sits outside the page’s main areas, so screen reader users jumping between areas can miss it. | Best practice |
We track these issues and update this page when they change.
If any part of FruitMachineCritic is hard to use for you, please tell us. The way to report a problem is by email to [email protected]. If you can, include:
the address of the page,
what you were trying to do and what went wrong,
the device, browser and any assistive technology you use (for example, a screen reader or magnifier).
If you can’t use a page, ask us and we can email you the text of that page. If you are not satisfied with our response, see the questions below for who else you can contact.
Web Content Accessibility Guidelines (WCAG) 2.2 (W3C): the full standard, with each success criterion.
Equality Act 2010, section 29 (legislation.gov.uk): services and public functions.
Equality Act 2010, section 20 (legislation.gov.uk): the duty to make adjustments.
Equality Advisory and Support Service: free advice on equality and human rights issues in England, Scotland and Wales.
Not yet. The site is partially conformant with WCAG 2.2 Level AA. In our check, the main remaining problem was small grey text with too little contrast on our tools, forum and sign-up pages. Every known issue is listed in the Compliance Status section, and we update this page when they change.
In England, Scotland and Wales, the Equality Act 2010 says that a person providing a service to the public, for payment or not, must not discriminate against someone who needs the service, and must make reasonable adjustments for disabled people, including providing information in an accessible format where that is reasonable. It does not name a technical standard; WCAG is the standard we choose to work to.
Email [email protected] with the page address, what went wrong and the device or assistive technology you use.
You can ask the Equality Advisory and Support Service for advice. It advises and assists individuals on issues relating to equality and human rights across England, Scotland and Wales, and does not provide legal advice.
Our pages use standard HTML structure, headings, page areas and text alternatives, which screen readers rely on. We have not yet tested the site with screen reader users, so if something doesn’t work for you, please let us know.
We checked the facts on this page against these sources:
Would you recommend this page?
No votes yet — be the first to rate this page
Only members can vote. Log in or create a free account.
Thanks for the update, Velobet. As the player says, please use my email for anything you want to send.
Read the thread