BETA

You're viewing an updated version of this site - your feedback will help us to improve it.

Accessibility statement for Business Wales

This accessibility statement applies to information on the Business Wales website and associated specialist business support sections of the website.

Each specialist service has its own accessibility page. It outlines how accessible the service is, how to report problems and how to request information in an alternative format. You can access these pages from the footer inside the individual service’s web pages.

Using this website

This website is run by Business Wales. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 400% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • navigate most of the website using speech recognition software
  • use most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website are not fully accessible:

  • some pages and document attachments are not clearly written
  • some hyperlinks won’t reflow above 300%
  • some tables do not have row headers
  • some heading elements are not consistent
  • some page titles are not unique
  • some form labels are not unique
  • some images do not have good alternative text
  • some link text does not describe the purpose of the link
  • many documents are in PDF format and are not accessible

Business Wales specialist services

Each specialist service has its own accessibility page, with details of how accessible the service is, how to report problems and how to request information in an alternative format. You can access these pages from the footer inside the individual service’s web pages.

Request information in a different format

If you need information on this website in a different format like plain text, braille, BSL, large print, easy read or audio recording:

We'll need you to tell us:

  • the web address (URL) of the information you need
  • your email address and name
  • the format you would like to receive - for example, plain text, braille, BSL, large print or audio CD
  • which assistive technologies you use

You can request a PDF in an accessible format from its page. Select ‘Request an accessible format’ to contact the organisation that published the document.

We’ll review your request and get back to you in 7 working days.

Feedback and contact information

We’re always looking to improve the accessibility of this website. If you find any problems that are not listed on this page or think we’re not meeting the requirements of the accessibility regulations, contact us on one of the ways below:

We'll need you to tell us:

  • the web address (URL) of the page you think we’re not meeting accessibility requirements
  • why you think we’re not meeting accessibility requirements

We’ll review your request and get back to you in 7 working days.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, please contact the Equality Advisory and Support Service (EASS).

Contacting us by phone or visiting us in person

Ofcom requires all landline and mobile telephone companies to provide a number of services for customers with disabilities. You can use the text relay service of your choice to contact Business Wales.

Our offices have audio induction loops, or if you contact us before your visit, we will make every effort to arrange a British Sign Language (BSL) interpreter. Just contact us on one of the ways below:

We'll need you to tell us:

  • who you are
  • how we can help you

We’ll review your request and get back to you in 7 working days.

Technical information about this website’s accessibility

Business Wales is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons: Non-compliance with the accessibility regulations.

Some alt text contains placeholders like ‘picture’ or ‘spacer’. This does not convey the actual content or function of the image, making it less useful for users who rely on screen readers. This fails success criterion WCAG 2.2 A 1.1.1 and 1.2.1 F30. We plan on resolving this by July 2024.

Some image alt text includes ASII art (Including smileys). Using ASCII art in alt text can be confusing and unhelpful for users who rely on alternative text to understand the meaning of the image. This fails success criterion WCAG 2.2 A 1.1.1 F72. We plan to resolve this by July 2024.

Some figures and images in PDF documents have blank ALT text. This fails success criterion WCAG 2.2 A 1.1.1 F65. We plan to resolve this by July 2024.

Some Word documents contain a graphic without Alt text. Alt text is required to convoy the information or purpose of the image to individuals using screen readers. This fails success criterion WCAG 2.2 A 1.1.1. We plan to resolve this by July 2024.

Some image elements do not have an accessible name. Without an accessible name, screen reader users may encounter difficulties in comprehending the meaning or function of an image on a webpage. This fails success criterion WCAG 2.2 A 1.1.1 F65. We plan to resolve this by July 2024.

Some pages use alt text as an image file name. Using alt text as a file name provides insufficient context to users. This fails success criterion WCAG 2.2 A 1.1.1 and 1.2.1 F30. We plan to resolve this by July 2024.

Some pages contain empty headings. Empty headings can confuse screen readers and make it difficult for them to understand the layout and organization of the content. This fails success criterion WCAG 2.2 A 1.3.1. We plan to resolve this by July 2024.

Some pages use CSS ‘font-weight’ property instead of using semantic markup like ‘strong’. CMS ‘font-weight’ does not interpret and convoy content as well as semantic markup, such as ‘strong’. This fails success criterion WCAG 2.2 A 1.3.1 F2. We plan to resolve this by July 2024.

Some PDF’S are not tagged, this prevents them from being accessible by screen readers. This fails success criterion WCAG 22 A 1.3.1. We plan to resolve this by July 2024.

Some Word documents contain a non-inline graphic or object. Non-inline graphics or objects may not adapt well to different screen sizes or user preferences. This fails success criterion WCAG 2.2 A 1.3.2. We plan to resolve this by July 2024.

Some documents titles are blank or missing. A title is essential for navigation and organization for those who have cognitive disabilities or rely on screen readers. This fails succession criterion WCAG 2.2 A 2.4.2 F25. We plan to resolve this by July 2024.

Some links uses general text like ‘Click here’ with no surrounding text explain the link purpose. This may affect users using screen readers as they may announce unhelpful information such as “click here’”, which doesn’t convoy the purpose or destination of the link. This fails success criterion WCAG 2.2 A 2.4.4 F63. We plan to resolve this by July 2024

Some pages contain several links that share the same link text and surrounding context, However, lead to different destinations. This makes selecting the relevant link difficult to those who rely on assistive technologies as they often navigate web pages by listening to a list of links. This fails success criterion WCAG 2.2 A 2.4.4 F63. We plan to resolve this by July 2024.

Some links do not have an accessible name. If multiple links have the same accessible name but lead to different places, it can lead to confusion for users, especially those who rely on screen readers. This fails success criterion WCAG 2.2 A 2.4.9, 4.4.4 and 4.1.2 F89. We plan to resolve this by July 2024.

Some paged to not use the lang attribute to identify the language of the page. This affects how content is presented. This fails succession criterion WCAG 2.2 A 3.1.1 (Language of page). We plan to resolve this by July 2024

Some pages contain element labels that appear as a descendant of the bottom element. This can lead to confusion in how assistive technology interprets and convoys content. This fails success criterion WCAG 2.2 A 4.1.2. We plan to resolve this by July 2024

Some pages use aria-lable or aria-labelldby on elements and roles that prohibit naming. This fails success criterion ARIA 1.2. We plan to resolve this by July 2024.

Some visual labels do not appear in the accessible name of links and controls. This is important to ensure users of assistive technology hear the same information the sighted users see. This fails success criterion WCAG 2.2 A 4.1.2 F96. We plan to resolve this by July 2024.

Some pages contain large images that flash more than three times in aby one second period. People with photosensitive epilepsy can experience seizures triggered by rapidly flashing lights or patters. This fails success criterion WCAG 2.2 A 2.3.1. We plan to resolve this by July 2024.

Some pages have set colours on some bodies and ‘a’ element, however, should be set on all. The idea is to ensure that there is sufficient contrast between text and background, making the content more readable for users with visual impairment. This fails success criterion WCAG 2.2 AA 1.4.3 F24. We plan to resolve this by July 2024.

Non-compliance with the accessibility regulations

The technologies listed below is non-accessible for the following reasons: Non-compliance with the accessibility regulations.

Some pages contain text and background colours that do not have enough contrast. This effects people with visual impairments. This fails success criterion WCAG 2.2 AA 1.4.3. We plan re resolve this by April 2024.

On some pages the CSS outline or border style on this element makes it difficult or impossible to see the link focus outline. The focus outline is important for users who navigate the website using a keyboard. This fails success criterion WCAG 2.2 AA 1.4.11 F78. We plan to resolve this by April 2024.

Some pages contain animated images over 5 seconds long that can’t be paused or stopped. Users with cognitive and attention-related disabilities may find it challenging to focus when faced with continuous, uncontrolled animations. This fails success criterion WCAG 2.2 A 2.2.2 F7. We plan to resolve this by April 2024.

Some pages require amending to ensure the user can identify row and column headers in data tables suing <th> elements, and mark layout tables with role=presentation. This fails success criterion WCAG 2.2 A 1.3.1 F91. We plan to resolve this by April 2024.

Some pages that contain data tables that have two or more logical levels of row or collum headers, do not use markup to associate data cells and header cells. This fails success criterion WCAG 2.2 A 1.3.1. We plan to resolve this by April 2024.

Some iframe and frame elements do not have a title attribute. The requirement for iframe and frame elements to have title attributes is aimed at ensuring those with disabilities can understand the purpose of the content of the embedded frame. This fails success criterion WCAG 2.2 A 4.1.2. We plan to resolve this by April 2024.

Some fieldset elements are not labelled with legend elements. Associating both elements is important for accessibility because it provides context about the group of form controls contained within the fieldset. This is sufficient to meet success criterion WCAG 2.2 A 1.31 and WCAG 2.2 A 3.3.2 H71. We plan to resolve this by April 2024.

Some pages contain images with a null alt attribute, these should not have a title, aria-label or aria-labelled by attributes. This fails success criterion WCAG 2.2 A 1.1.1 F39. We plan to resolve this by April 2024.

Some phrases in a different language are not in a <span> or <div> with a language attribute. This can lead to punctuation errors, misinterpretations or confusion for users who depend on assistive technologies. This fails success criterion WCAG 2.2 AA 3.1.2. We plan to resolve this by April 2024.

Some pages do not contain the following: Elements with role=tablist must contain or own an element with role=tab and must not contain elements with other roles. The specified structure ensures consistent experience for users, including those who rely on assistive technologies. This fails success criterion ARIA 1.2 WCAG 2.2 A 1.3.1. We plan to resolve this by April 2024.

Some pages contain a figure with a figcaption that has a role attribute. This can lead to confusion and my result on conflicting information for assistive technologies. This fails success criterion ARIA 1.2. We plan to resolve this by April 2024.

Interactive tools and transactions

Some HTML form control do not have an accessible name. An accessible name of a form control is essential to users who rely on assistive technologies to navigate and interact with web content. This fails success criterion WCAG 2.2 A 4.1.2 F68. We plan to resolve this by April 2024.

Some clickable controls do not have an ARIA role. ARIA roles provide important information to as assistive technologies about the type and purpose of an element. This fails success criterion WCAG 2.1.1 F54. We plan to resolve this by April 2024.

PDFs and other documents

New documents we publish to access our services should be fully accessible.

However, we know that some of our older documents (published before 23 September 2018) are not accessible. For example, some of them:

  • are not marked up in a way that allows screen reader users to understand them
  • are not tagged up properly, for example they do not contain proper headings
  • are not written in plain English

Some of these are historic documents and are not essential to providing our services. These types of documents are exempt from the regulations. We do not currently have any plans to make them accessible.

If you need to access information in one of these document types, please contact us on one of the ways below and ask for an alternative format.

We'll need you to tell us:

  • the web address (URL) of the information you need
  • the format you would like to receive
  • which assistive technologies you use

We’ll review your request and get back to you in 7 working days.

Preparation of this accessibility statement 

This statement was prepared on 8 January 2024 to replace the previous accessibility statement. The statement was last reviewed on 8 January 2024.

How we tested the website

This website was last tested on 15 December 2023. The test was carried out by S8080.

On the 15 January 2023 S8080 used SortSite Desktop to scan over 8700 of our pages for compliancy to level A and AA of the Web Content Accessibility Guidelines Version 2.2. The scan included a combination of core pages, commonly used templates and complex templates.

We tested our main website platform, available at https://businesswales.gov.wales/  

As well as some of our specialist services managed by the Business Wales team including:


Business Wales Helpline

03000 6 03000

Lines are open 10am to 4pm Monday to Friday.

Rydym yn croesawu galwadau’n Gymraeg.
We welcome calls in Welsh.