|Videos on the site do not have captions. This may prevent users from adapting the material through any sensory modality (for example, visual, auditory or tactile) to match their needs.
||This fails WCAG 1.2.1 (Audio-Only and Video-Only (Prerecorded)), 1.2.2 (Captions), 1.2.3 (Audio Description or Media Alternative (Prerecorded)) and 1.2.5 (Audio Description (Prerecorded)).
|A number of PDF/word documents are not fully accessible to screen reader software.
||This fails WCAG 1.1.1 (Non-text Content).
|Some images on the site do not have a text alternative. Alternative text is not available for images on the Homepage, this includes images; FQAS Online Payments, Market Information, Industry Development and Promotion. New images uploaded to the site from September 2020 will have a text alternative.
||This fails WCAG 1.1.1 (Non-text Content). People with sight loss may not see an image clearly on a page. You need to use a text alternative to share the information. The alternative text must describe the information or function represented by the image. Screen readers can share the alternative text with the user. In PDF documents you must ensure that images are tagged correctly with alternative text.
|There are a number of pages with lists which may not be adequately structured. This may result in a loss of meaning for users of screen readers.
||This fails WCAG 1.3.1 (Info and Relationships).
|The slider screen on the homepage is not readable using a screen reader and cannot be paused.
||This fails 1.3.1 (Info and Relationships) and 2.2.2 (Pause, Stop, Hide). Content that moves, flashes or updates automatically can be a severe distraction for certain users, making it difficult to use the page. It can also cause problems for assistive technologies like screen readers.For any moving, flashing or scrolling information that:
- starts automatically;
- lasts more than five seconds; and
- is presented in parallel with other content
there must be a method to allow the user to pause, stop, hide or control the frequency for content that automatically begins ‘auto-updating’ in parallel with other content unless it is essential to an activity.
|Form fields for payment card information are not accessible using a screen reader as it is a third party site. The form field (recaptcha button) on the contact page is not accessible. Select element must have an accessible name.
||This fails 1.3.1 (Info and Relationships), 2.4.6 (Headings and Label), 3.2.2 (Labels or instructions), 4.1.2 (Name, role, value). Form labels help assistive technologies to understand what input is expected in a form field. Adding a label reduces confusion and enlarges the clickable area which helps users with limited motor control. Labels should be used for inputs such as:
- Text entry fields
- Radio buttons
- Select menus
|Focus is not visible on multiple pages including: Contact Us, Market Information button, submit buttons, read more buttons, arrows on slider screen and click here buttons. Focus is not clear on links across FQAS Online Payments, Market Information, Industry Development and Promotion.
||This fails 2.4.7 (Focus Visible). A visible focus helps users know which element has keyboard focus and where they are on the page. When an element gets focus there should be a visible border around it. Highlighting the element that has keyboard focus or is hovered over can provide information like whether the element is interactive or the scope of that element. Operating systems have a native indication of focus, which is available in many browsers. The default display of the focus indicator is not always highly visible and may even be difficult to see especially on coloured backgrounds.
|Text is unable to be resized up to 200 percent without loss of content or function.All webpages – At 200% and 400%, the browsealoud and text toggles cover content on the webpage.
Homepage – At 200%, content within the feature image is cut off.
Contact page – At 400%, privacy recaptcha button is covered.
|This fails 1.4.4 (Resize Text). Visual text, including text-based controls can be scaled so that they can be read directly by users with visual impairments without using assistive technology such as a screen magnifier.
|Content cannot be presented without loss of information or functionality, and without requiring scrolling in two dimensions.For example:
Homepage- in mobile view, Livestock wording on the slider screen overlaps on Coronavirus public message.
News – in mobile view and at 400% number of pages at the bottom of the page does not reflow to fit the page correctly and the word Last is cut off and numbers overlap.
|This fails 1.4.10 (Reflow). Reflow or ‘responsive web design’ helps users with low vision who may need to enlarge text on a webpage and read it in a single column without scrolling in more than one direction. It also helps users who are viewing the page on a mobile device. If a page does not support reflow it can appear smaller and more difficult to use or content may be cut off. Navigation menus often collapse into fewer items or into a single menu button to take up less space. All content and functionality must still be fully available.
|Some images of text are used. Images of text should not be used unless text cannot be formatted to the same effect, for example logos or branding.
||This fails 1.4.5 (Images of Text). Images of text cause problems for users who need to adjust how visual content like font size, spacing or colours are displayed. The image quality can reduce and become blurry when users increase page magnification. Text may be used in images where the text is part of an image that contains a lot of other visual content like graphs or diagrams that give important information through more than just text.
|There is poor colour contrast on the site.All webpages
Poor colour contrast of green background on blue text when using keyboard along the top menu
Green text on green background has poor colour contrast. This is the Home> And the page the user is on
White text on green background for the buttons does not have sufficient colour contrast
All text within the slider image cannot be determined because element contains an image node
Pale blue text on white background does not have sufficient colour contrast for menus along the bottom, including ‘Click here to join and benefit from being a FQAS member.’
Contact page, Homepage
White text on green background for ‘Read more’ buttons does not have sufficient colour contrast
Green links on white background within the content does not have sufficient colour contrast
Green ‘Click here’ does not have sufficient colour contrast
Industry Development, Promotion
White text on green button for ‘Membership checker’ has poor colour contrast
The green text on white background at the bottom of the page for the number of news pages does not have sufficient colour contrast.
|This fails 1.4.3 Contrast (Minimum). Poor colour contrast makes it difficult for someone with sight loss to see the content properly. If there is a big difference between the background and foreground colours it should be much easier to see the difference between them.