The National Search And Rescue Dog Association

Maple Barn, Canterbury Road, Molash, Kent CT4 8HF

01233 800 165

[email protected]

Facebook Twitter Youtube
NSARDA Logo 150x150
Menu

Accessibility

Last Updated On 12-Sep-2023
Effective Date 12-Sep-2023

 

NSARDA are committed to making our website accessible to everyone, regardless of the technology or the ability of the user. We are working to increase the accessibility and usability of our website and adhere to available standards and guidelines.

This website is run by The National Search And Rescue Dog Association [NSARDA].

We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • zoom in up to 400% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • listen to most of the website using a screen reader (including the most recent versions of NVDA and VoiceOver)
  • We’ve also made the language as simple as possible to understand.

 

Please refer to the AbilityNet website which has advice on making your device easier to use if you have a disability.

 

How accessible is this website?

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

  • Forms
    • Error messages are not clear.
    • Error messages do not have sufficient contrast.
    • Error messages are not always linked to the fields with the errors.
    • You cannot check your answers before submitting a form.
    • Forms time out (automatically cancel).
    • Some content cannot be accessed with a keyboard and screen reader.

 

  • Buttons, links and icons
    • Button, link and icon hover states are only indicated by a change in colour.
      Some buttons, video play buttons and some image links do not have a focus state.
    • It is sometimes hard to tell where the focus is when navigating by keyboard, for example: video controls.
    • Some link focus states are only indicated by a change in colour.
    • Link text is not always clear or descriptive.
    • Not all links are clearly identifiable.
    • The same link text might be used on one page with different destinations.
    • Some image links do not have a text alternative.
    • Some labels are not associated with an input element – this is often on currency buttons.
    • Not all icons have alt text.
    • Some element IDs are duplicated. 
  • Search
    • Search and filters use the same icon.
    • The search icon behaves differently in different places.
    • The focus order is not always clear.
  • Videos
    • Some videos contain flashing, flickering or blinking content.
    • Not all videos have captions.
    • Videos do not have audio description.
  • Images
    • Not all images have alt text.
    • There are some images of text.
    • Some content cannot be accessed with a keyboard and screen reader.

 

  • Maps
    • There is no text-based alternative to a map. 

 

  • Page Titles
    • Some pages have duplicate titles.
    • Some page titles are not marked as H1.

 

  • Headers and Text
    • When text is increased to 200% zoom some text becomes cropped, or spacing between lines is not sufficient.
    • Some text does not have enough contrast with the background to be easily read.
    • Headings and labels are not always clear or descriptive.
    • Some headings are not marked up correctly.
    • Some content is harder to use when text is enlarged to or requires horizontal scrolling.

 

  • Featured Slider/Carousels
    • The focus order is not always clear, for example, on featured slider/carousel components.
    • Non-English Content
      Pages are defined as English.

 

  • Filters
    • Filters sometimes use checkboxes and sometimes use radio buttons.

 

  • Other
    • There are some instances where only visual characteristics are used to display information.
    • Tabs do not have a focus state.
    • Some container elements are empty.

 

  • Testing
    • We regularly test new components on our website which may not be fully accessible whilst in the testing stage.
    • If the component is taken forward to be developed for our site we endeavour to make it as accessible as possible.

 

What to do if you cannot access parts of this website.

If you need information on this website in a different format like accessible PDF or large print email [email protected] 
and we’ll consider your request and get back to you as soon as possible.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page, or think we’re not meeting accessibility requirements, contact us using email [email protected]. 

 

Contact us by phone or email

How to contact us.

 

Technical information about this website’s accessibility

NSARDA is committed to making its website accessible, in accordance with the WCAG2.0 guidelines.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.0 AA standard. The non-accessible elements are listed below.

 

Non accessible content

The content listed below is non-accessible for the following reasons.

 

Non compliance with the accessibility regulations

Some images, icons, image links and maps do not have alt text, or alt text could be clearer. This fails WCAG 2.0 success criterion 1.1.1 (Non-text Content).

Not all videos have captions. This fails WCAG2.0 success criterion 1.2.2 (Captions (Prerecorded)).

Videos do not have transcripts. This fails WCAG2.0 success criterion 1.2.1 (Audio-only and Video-only (Prerecorded)).

Videos do not have audio description. This fails WCAG2.0 success criterion 1.2.3 (Audio Description (Prerecorded)). 

Some content is unclear when using a screen reader. This fails WCAG 2.0 success criterion 1.3.1 (Info and Relationships).

Some content cannot be accessed by VoiceOver on mobile.

There are some instances where only colour is used to convey information. This fails WCAG2.0 success criterion 1.4.1 (Use of Colour).

Button, link, icon and dropdown hover states are only indicated by a change in colour. This fails WCAG 2.0 success criterion 1.4.1 (Use of Color).

Some button, link and dropdown focus states are often only indicated by a change in colour. This fails WCAG 2.0 success criterion 1.4.1 (Use of Color).

Some text does not have sufficient contrast. This fails WCAG2.0 success criterion 1.4.3 (Contrast (Minimum)).

When text is increased to 200% zoom some text becomes cropped, or spacing between lines is not sufficient. Some content becomes harder to use when text is enlarged to 200%. This fails WCAG 2.0 success criterion 1.4.4 (Resize text).

There are some images of text. This fails WCAG2.0 success criterion 1.4.5 (Images of Text).

Some parts of the website are not accessible by keyboard. This fails WCAG2.0 success criterion 2.1.1 (Keyboard). 

The search function is a keyboard trap. This fails WCAG2.0 success criterion 2.1.2 (No Keyboard Trap).

Forms time out. This fails WCAG2.0 success criterion 2.2.1 (Timing Adjustable).

Some videos have a flicker. This might fail WCAG2.0 success criterion 2.3.1 (Three Flashes or Below Threshold). 

Some pages have duplicate titles. This fails WCAG2.0 success criterion 2.4.2 (Page Titled).

The focus order is not always clear. This fails WCAG 2.0 success criterion 2.4.3 (Focus Order).

Link text is not always clear or descriptive. This fails WCAG 2.0 success criterion 2.4.4 (Link Purpose (In Context)).

The same link text might be used on one page with different destinations. This fails WCAG2.0 success criterion 2.4.4 (Link Purpose (In Context)). 

Headings and labels are not always clear or descriptive. This fails WCAG2.0 success criterion 2.4.6 (Headings and Labels).

Focus is not always visible. This fails WCAG 2.0 success criterion 2.4.7 (Focus Visible).

Icons and components are not used consistently and do not behave consistently. This fails WCAG2.0 success criterion 3.2.4 (Consistent Identification).

Error messages are not clear. This fails WCAG 2.0 success criterion 3.3.1 (Error Identification). 

You cannot check your answers before submitting a form. This fails WCAG2.0 success criterion 3.3.4 (Error Prevention (Legal, Financial, Data)).

Some headings are not marked up correctly. This fails WCAG 2.0 success criterion 4.1.1 (Parsing).

Error messages are not always linked to the fields with the errors. This fails WCAG 2.0 success criterion 4.1.1 (Parsing).

Form field labels are not always marked up correctly. This fails WCAG 2.0 success criterion 4.1.1 (Parsing).

Not all components have appropriate mark up. This fails WCAG2.0 success criteria 4.1.2 (Name, Role, Value).  

 

How we tested this website 

This website was last tested on September 2023. The test was carried out by NSARDA. 

We chose the sample of pages to include in our audit. We chose a representative sample that captured the variation in content and functionality that NSARDA had as at September 2023. 

 

Our sample included: 

  • our site’s homepage
  • content pages that are mostly text based
  • images, video and audio content
  • interactive tools and transactions, like forms
  • navigation pages, including our sitemap
  • pages with search functionality
  • any pages containing information about accessibility, how to contact us, how to use our site and legal information (for example terms and conditions pages, or things like our Privacy Policy). 

 

We tested: 

  • our main website platform, available at https://nsarda.org.uk/

 

We carried out the audit using a Google Chrome browser and Safari on an iPhone.  

We routinely use automated accessibility checking software to identify issues on parts of our site.

We also routinely check new and existing components in Chrome, Edge, in Safari and on iPhone.

This statement was prepared on September 2023. It has yet to be updated.