About cookies on this site
We use cookies to collect website performance and usage data, and to enhance and customise content and advertisements.
About cookies on this site
Cookies used on the site are categorized and below you can read about each category and allow or deny some or all of them. When categories than have been previously allowed are disabled, all cookies assigned to that category will be removed from your browser. Additionally you can see a list of cookies assigned to each category and detailed information in the cookie declaration.
Necessary cookies
Some cookies are required to provide core functionality. The website won't function properly without these cookies and they are enabled by default and cannot be disabled.
CookieHub is a Consent Management Platform (CMP) which allows users to control storage and processing of personal information.
Cloudflare is a global network designed to make everything you connect to the Internet secure, private, fast, and reliable.
Preferences
Preference cookies enables the web site to remember information to customize how the web site looks or behaves for each user. This may include storing selected currency, region, language or color theme.
Analytical cookies
Analytical cookies help us improve our website by collecting and reporting information on its usage.
Google Analytics is a web analytics service offered by Google that tracks and reports website traffic.
Vimeo, Inc. is an American video hosting, sharing, services provider, and broadcaster. Vimeo focuses on the delivery of high-definition video across a range of devices.
Clarity is a user behavior analytics tool that helps you understand how users interact with your website.
Marketing cookies
Marketing cookies are used to track visitors across websites to allow publishers to display relevant and engaging advertisements. By enabling marketing cookies, you grant permission for personalized advertising across various platforms.
A piece of code that lets businesses measure, optimise and build audiences for advertising campaigns.
The LinkedIn Insight tag powers conversion tracking, website audiences, and website demographics within the LinkedIn system.
Microsoft Advertising (formerly Bing Ads) is a service that provides pay per click advertising on the Bing, Yahoo!, and DuckDuckGo search engines.
Cookies used on the site are categorized and below you can read about each category and allow or deny some or all of them. When categories than have been previously allowed are disabled, all cookies assigned to that category will be removed from your browser. Additionally you can see a list of cookies assigned to each category and detailed information in the cookie declaration.
Necessary cookies
Some cookies are required to provide core functionality. The website won't function properly without these cookies and they are enabled by default and cannot be disabled.
Name | Hostname | Vendor | Expiry |
---|---|---|---|
cookiehub | .bigfork.co.uk | CookieHub | 365 days |
Used by CookieHub to store information about whether visitors have given or declined the use of cookie categories used on the site. | |||
PHPSESSID | www.bigfork.co.uk | Session | |
Cookie generated by applications based on the PHP language. This is a general purpose identifier used to maintain user session variables. It is normally a random generated number, how it is used can be specific to the site, but a good example is maintaining a logged-in status for a user between pages. | |||
__cf_bm | .vimeo.com | Cloudflare, Inc. | 1 hour |
The __cf_bm cookie supports Cloudflare Bot Management by managing incoming traffic that matches criteria associated with bots. The cookie does not collect any personal data, and any information collected is subject to one-way encryption. | |||
_cfuvid | .vimeo.com | Session | |
Used by Cloudflare WAF to distinguish individual users who share the same IP address and apply rate limits |
Preferences
Preference cookies enables the web site to remember information to customize how the web site looks or behaves for each user. This may include storing selected currency, region, language or color theme.
Name | Hostname | Vendor | Expiry |
---|---|---|---|
lidc | .linkedin.com | LinkedIn Ireland Unlimited Company | 1 day |
Used by LinkedIn for routing. | |||
li_gc | .linkedin.com | LinkedIn Ireland Unlimited Company | 180 days |
Used by LinkedIn to store consent of guests regarding the use of cookies for non-essential purposes | |||
vuid | .vimeo.com | 400 days | |
These cookies are used by the Vimeo video player on websites. |
Analytical cookies
Analytical cookies help us improve our website by collecting and reporting information on its usage.
Name | Hostname | Vendor | Expiry |
---|---|---|---|
_ga_ | .bigfork.co.uk | 400 days | |
Contains a unique identifier used by Google Analytics 4 to determine that two distinct hits belong to the same user across browsing sessions. | |||
_ga | .bigfork.co.uk | 400 days | |
Contains a unique identifier used by Google Analytics to determine that two distinct hits belong to the same user across browsing sessions. | |||
bcookie | .linkedin.com | LinkedIn Ireland Unlimited Company | 365 days |
This is a Microsoft MSN 1st party cookie for sharing the content of the website via social media. | |||
CLID | www.clarity.ms | Microsoft | 365 days |
Identifies the first-time Clarity saw this user on any site using Clarity. | |||
_clck | .bigfork.co.uk | Microsoft | 365 days |
Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. | |||
MUID | .bing.com | Microsoft | 390 days |
Microsoft User Identifier tracking cookie used by Bing Ads. It can be set by embedded microsoft scripts. Widely believed to sync across many different Microsoft domains, allowing user tracking. | |||
MR | .c.bing.com | Microsoft | 7 days |
Used by Microsoft Clarity to indicate whether to refresh MUID. | |||
SM | .c.clarity.ms | Microsoft | Session |
This cookie is installed by Clarity. The cookie is used to store non-personally identifiable information. The cookie is used in synchronizing the MUID (Microsoft unique user ID) across Microsoft domains. | |||
MUID | .clarity.ms | Microsoft | 390 days |
Microsoft User Identifier tracking cookie used by Bing Ads. It can be set by embedded microsoft scripts. Widely believed to sync across many different Microsoft domains, allowing user tracking. | |||
MR | .c.clarity.ms | Microsoft | 7 days |
Used by Microsoft Clarity to indicate whether to refresh MUID. | |||
_clsk | .bigfork.co.uk | Microsoft | 1 day |
Connects multiple page views by a user into a single Clarity session recording. |
Marketing cookies
Marketing cookies are used to track visitors across websites to allow publishers to display relevant and engaging advertisements. By enabling marketing cookies, you grant permission for personalized advertising across various platforms.
Name | Hostname | Vendor | Expiry |
---|---|---|---|
_fbp | .bigfork.co.uk | Meta Platforms | 90 days |
Facebook Pixel advertising first-party cookie. Used by Facebook to track visits across websites to deliver a series of advertisement products such as real time bidding from third party advertisers. | |||
SRM_B | .c.bing.com | Microsoft | 390 days |
This cookie is installed by Microsoft Bing. Identifies unique web browsers visiting Microsoft sites. | |||
ANONCHK | .c.clarity.ms | Microsoft | 1 hour |
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation | |||
AnalyticsSyncHistory | .linkedin.com | LinkedIn Ireland Unlimited Company | 30 days |
Used by LinkedIn to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries | |||
UserMatchHistory | .linkedin.com | LinkedIn Ireland Unlimited Company | 30 days |
Contains a unique identifier used by LinkedIn to determine that two distinct hits belong to the same user across browsing sessions. | |||
bscookie | .www.linkedin.com | LinkedIn Ireland Unlimited Company | 365 days |
Used by the social networking service, LinkedIn, for tracking the use of embedded services. |
Colin Richardson
Digital Design Director
18/07/2024
Accessibility is often overlooked, and is far more important than you realise.
When we built the new Bigfork website, one of my requirements was that we made it as accessible as we could. But what does this mean, and why does it matter?
Most of us can’t imagine living without the web. It’s estimated that 96% of households in Great Britain are online. From social media to online shopping, the web is an important part of our lives. So, it should be available to everyone regardless of ability, shouldn’t it?
There are an estimated 16 million disabled people in the UK. That’s about 1 in 5. Could they be your customers?
‘The total spending power of families with at least 1 disabled person is estimated at £274 billion a year.’
£274 billion is a big number. Even without that, making your website accessible is good practise. It helps make the user experience better which benefits everyone. And in the era of core web vitals, that includes Google.
Accessibility issues are often thought about in relation to disabilities.
For example, someone with blindness or low vision may rely on software called a screen reader. A screen reader is a type of assistive technology, a term you'll see a lot when dealing with accessibility. The screen reader software helps people navigate websites by reading the content aloud. This removes the need for a mouse and relying on visual cues.
Someone with limited motor control may find a mouse hard to use. Or maybe their Apple mouse is out of action while it’s on charge. So, they might navigate with their keyboard. You can try this – visit your favourite website and use the tab key, arrow keys and return key to navigate. Now try again on gov.uk – you should notice the difference.
Let’s take the above examples without disabilities in mind. Vision often starts to deteriorate after age 40 due to presbyopia. The predicated median age of the UK population in 2025 will be 40.5. So, basic accessibility considerations like making text easy to zoom will help a lot of people (WCAG 1.4.4).
And have you ever had a few too many beers, hit a workout a bit hard? Then you will have experienced loss of fine motor control. Big, clear buttons make it a lot easier to order that recovery takeaway from your phone (WCAG 2.5.5).
A set of guidelines called WCAG govern web design accessibility standards. WCAG stands for web content accessibility guidelines, the current version is WCAG 2.2.
There are three levels of accessibility in WCAG from Level A to Level AAA. Each level builds on the previous, so to meet Level AA, your website must meet Level A first.
In broad terms, the more “A”s you need, the greater the impact on design. That’s not to say accessible websites can’t be beautifully designed, there are just more considerations.
As of Sept 2018 all UK public sector websites are required to meet the WCAG 2.2 AA standard. There are no requirements for commercial websites yet, but it doesn’t mean you should ignore it.
The short answer is to work through the WCAG guidelines and resolve any issues. WCAG is very technical and can be hard to understand. WebAIM have created a version that's easier to follow – the WebAIM WCAG2 checklist. This does not replace the WCAG list, it's designed to make it easier to work with.
You can use the list to produce an accessibility audit. Check off each point to see if your website meets that guideline. If it doesn’t, make a note of why. This will give you a list of things that need fixing. Most websites have several templates and elements so be sure to test a variety of pages.
Automated tools such as tota11y or SortSite can spot some issues. Many issues will need manual checks though. The guidelines are quite technical, so you’ll need a strong understanding of websites.
Bigfork often produce accessibility audits for our clients. Below are the most common issues we find, and how you could fix them.
You should never rely on colour alone to convey information. For people with low vision or colour blindness it makes your website hard to use.
Websites usually fail to meet this guideline when they have links in the content. If the link colour is close to the text colour, they can be hard to spot. The very easy fix is to make links underlined. If your links are already underlined, congratulations, you’ve passed WCAG 1.4.1.
Text should also stand out from its background. For body text, it should have a colour contrast of at least 4.5:1. For large text (18pt or bold 14pt) it’s at least 3:1. You can check this with tota11y, or by using a colour picker and a contrast checker. Make sure to check any text that's overlaid on an image. Always test the areas with the lowest contrast i.e., where colours are most similar. Do you have enough contrast? Then you’ve passed WCAG 1.4.3, good job.
Pop quiz – which of these links is more accessible?
The answer is B. But why? Because of WCAG 2.4.4 – link purpose in context. This means a link should make sense without needing any other context.
In example A, the “click here” only makes sense as part of the whole sentence. People using a screen reader will only hear the link as “click here”, which makes no sense on its own.
In example B we make the link text descriptive, so without any context we know it’s “about accessibility”. This has meaning without extra context.
We often see this on news and blog pages – a slew of “read more” links. The easy fix is to remove them and make the article title the link. Congratulations, your site is already more accessible.
‘If it doesn’t say "click here", nobody will know what to do.’
This often comes up when we don’t have “click here” and “read more” links in designs.
The solution is to make the link look like a link, with an underline, or an arrow. Make buttons look like buttons, (but not ghost buttons). People are quite used to poking at things that look like they can be poked. Consider your phone, your computer, ATMs. None of them tell you to click here, the labels are the instructions.
Everyone forgets documents. All those PDF and Word files are part of your website too. We almost always find these three things:
Fixing PDFs is quite simple with Acrobat Pro using the built-in accessibility tools. Microsoft have resources for making accessible Word Documents too.
More complex documents with tables, lists and links may need extra work. There is a good guide on AbilityNet for creating accessible documents.
If you are a public sector body, only documents published after 23 September 2018 need to comply. Unless the document is still relevant, such as a manual for a currently used system.
Documents can be hard to make accessible. At the time of writing this website falls short of Level AA because of the forms in our web design brief. This is not ideal, but the document is still useful without needing to use the form.
You can cover any issues like this in an accessibility statement.
You may have seen accessibility overlays on websites. They usually open a menu with options to make the website easier to use, such as large text or high contrast.
While this sounds like a good idea on paper, a well designed and built website does not need it. The users browser and, if they have it, specialist software will do all these things. So an overlay on an inaccessible website becomes a crutch rather than addressing underlying issues. That’s not to say they don’t have a place, just for most sites they won’t bring much to the table.
The European Disability Forum (EDF) and the International Association of Accessibility Professionals (IAAP) agree in their statement from May 2023: Does accessibility overlay technology live up to the hype?
You can use your accessibility audit to write your accessibility statement. It’s ok if your website doesn’t pass everything, the statement will cover that.
The gov.uk website has a sample accessibility statement that you can work from. This page has very clear instructions and is easy to follow. If you are a public sector body, note that some of the wording is required by law.
One important bit is the “non-accessible content” section. If your accessibility audit found issues, you can explain these issues here, and how you plan to fix them. Then as you work through the issues, re-test your website and update your statement.
What if you can’t fix something? Or don’t have the time or budget right now? You can flag issues as a disproportionate burden. This is not an excuse to ignore issues, some things are just not practical. Any new website should aim to not include disproportionate burdens. It is sometimes necessary though, for example if you rely on legacy content such as old documents.
We’ve created a lot of accessible websites for our customers. Here are some recent examples.
I hope you've learned a bit about why accessibility matters and how to start looking into it. An accessibility audit is the best starting point. Then review your website regularly as developments and new content could reintroduce issues. Your accessibility statement should have a “last amended” date to show it is up to date.
Planning a new website? If you are it's a good idea to include accessibility into your brief. Find out how to write a website brief (includes a free PDF template.)
If you want to redesign your B2B website to make it accessible then we recommend finding a B2B web design agency that is experienced in accessible design.
Would you like to know more about accessible web design? If you have questions or would like an accessibility audit, please feel free to email me
This article was updated on , filed under website design, website content, website development.
Get the latest B2B website news straight to your inbox
We can make your new website a great success.