Accessibility statement

Accessibility statement

This website is run by Tom Tomlinson & Lee Fallin. 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 300% 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
  • listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We have tried to make 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 is the website?
We know some parts of this website are not fully accessible:

  • content is skipped and difficult to navigate using just a keyboard
  • you cannot modify the line height or spacing of text
  • the hyperlink (more info) relating to the “always” guidance is too subtle – They do not obviously indicate their purpose and state.

Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

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

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, in the first instance complete the feedback form on the website. You also have the option to send email to [email protected] or [email protected]

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, contact the Equality Advisory and Support Service (EASS).

Technical information about this website’s accessibility
Tom Tomlinson & Lee Fallin are 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.1 AA standard, due to the non-compliances, listed below.

NON COMPIANCE (10)

  • The page has a logical tab order
  • Interactive controls are keyboard focusable
  • Interactive elements indicate their purpose and state
  • The user’s focus is directed to new content added to the page
  • User focus is not accidentally trapped in a region
  • Custom controls have associated labels
  • Custom controls have ARIA roles
  • Visual order on the page follows DOM order
  • Offscreen content is hidden from assistive technology
  • HTML5 landmark elements are used to improve navigation

 

PASSED AUDITS (15)

  • [aria-*] attributes match their roles
  • [aria-hidden=”true”] is not present on the document <body>
  • [aria-*] attributes have valid values
  • [aria-*] attributes are valid and not misspelled
  • Buttons have an accessible name
  • ARIA IDs are unique
  • Image elements have [alt] attributes
  • [user-scalable=”no”] is not used in the <meta name=”viewport”> element and the [maximum-scale] attribute is not less than 5.
  • The page contains a heading, skip link, or landmark region
  • Background and foreground colours have a sufficient contrast ratio
  • Document has a <title> element
  • <html> element has a [lang] attribute
  • <html> element has a valid value for its [lang] attribute
  • Links have a discernible name
  • Heading elements appear in a sequentially-descending order

Non-compliance with the accessibility regulations
We are aiming to resolve all non-compliance issues on the www.designingfordiverselearners.info by 31st December 2022. Below are the induvial accessibility issues with examples of how we do not meet compliance.

  • The page has a logical tab order
  • Interactive controls are keyboard focusable

Some parts of the website are difficult to navigate using a keyboard. For example, navigating from the top-level headings to body content does not follow a logical order. We want to improve this experience and are planning to resolve before 31st December 2022.

  • Interactive elements indicate their purpose and state

The buttons on the “Always” section checklist are defined as buttons, but not indicate their purpose. We want to improve this by clearly indicating they point to more information. We are planning to resolve before 31st December 2022.

  • The user’s focus is directed to new content added to the page
  • User focus is not accidentally trapped in a region
  • Custom controls have associated labels
  • Custom controls have ARIA roles
  • Visual order on the page follows DOM order
  • Offscreen content is hidden from assistive technology
  • HTML5 landmark elements are used to improve navigation

Content that’s not within the scope of the accessibility regulations
We point to external resources on the www.a11yproject.com website and other sources. We do not host any of this content, nor do we test it thoroughly. The A11y Project runs an issue tracker related to its own content and community resources.

What we’re doing to improve accessibility
We have not yet developed a clear & coherent accessibility roadmap for www.designingfordiverselearners.info. This will be reviewed no later than 01/10/2022.

Preparation of this accessibility statement
This statement was prepared on 01/06/2022. It was last reviewed on 06/06/2022.

This website was last tested on 06/06/2022 – via google Lighthouse and manual tested by visiting the site and working through the success criteria. The test was carried out by Tom Tomlinson.

We used a sampling approach to deciding on a sample of pages to. This includes 5 main page sections;

Two “more information” posts;

were also tested during the audit. During the next phase of testing, we will use different pages and posts for the sample and continue this approach until all pages and posts have been tested.

You can read the lighthouse accessibility report.