This is a collection of helpful accessibility resources compiled from trusted sources, with detail around best practices and the public sector regulations.

If you have any questions about accessibility or would like a chat about what Frank can offer, feel free to contact us.  We can offer bespoke accessibility training or a review on your website. 

What is accessibility?

Watch this short video which explains a bit about web accessibility and why it is important.

Accessibility is...The need to cater to different abilities and situations.

We must try to exclude as few people from our websites as possible and think about the range of users who need to access our content.

“[web accessibility is] essential for developers and organisations that want to create high quality websites and web tools, and not exclude people from using their products and services.”

- W3C, Web Standards Organisation

This is arguably even more important in healthcare than most sectors.

On our web pages all users should be able to:

  • Perceive
  • Understand
  • Interact
  • Navigate

Examples of disabilities which could impact this

  • Blind or partially sighted
  • Arthritis
  • Dyslexia
  • Neurodivergent users

Government Digital Services (GDS) has extensive user profiles for different types of users on their website here.

More than just disability

Accessibility is not simply ‘disability’.  Having accessible websites can be helpful to many people according to the scenario they are in, for example:

  • Situational - Being on slow Wi-Fi, or in a noisy cafe
  • Temporary disability - You could be tired, or have a broken arm
  • Equipment - An old, slow mobile phone or computer
  • Literacy - A low literacy level needs simple, understandable content
  • Older people - May just simply struggle with technology due to arthritis for example

These can all happen to anyone, at any time.

To help ensure that all users can access the same content, the World Wide Web Consortium (W3C) introduced the Web Content Accessibility Guidelines (WCAG).  All public sector websites must meet these guidelines.  The guidelines relate to how information is put on the web (e.g. about content) and how the site is built (e.g. code and mark up).  Clients are responsible for the content (although we can support with training and our Accessible Content Guide) and Frank are responsible for ensuring the code is compliant.  Clients are also required to include an Accessibility Statement on their website 

Regulations

WCAG 2.2

WCAG 2.1

The Guidelines for WCA2.1 still stand, WCAG2.2 is in addition to 2.1

Content

Frank will build your site to be compliant with WCAG 2.2 A/AA standard.  However, it is the responsibility of the client to ensure the content is presented in a way that is also compliant.  Here are some helpful tips, but Frank can also provide dedicated accessibility training for you. 

Documents

Testing

Accessibility Statement

Engagement

Frank's Accessibility Toolbar

  • As part of your website build, Frank usually provides our Accessibility toolbar.  Usually located at the bottom of the page, it is labelled 'Show accessibility tools' which toggles to ‘Hide accessibility tools’ to stop it from being visible.
  • Users can click on the toolbar to view various accessible options, including:
    • Text size - to significantly increase the size of the text without it spilling across the page
    • Contrast - to change the colour contrast on screen to one of four different high contrast colour settings
    • Google translate - to change the language (Frank cannot guarantee the accuracy of the translation)

Read Aloud Technologies

  • Third party apps or plug-ins can be added to the tool bar, including "Read Aloud" support tools such as "ReciteMe" or "BrowseAloud".  However, these services often attract an annual licence fee.  Frank have put together a Guide to Accessing Free Read Aloud Technology which you can include in your Accessibility Statement.  Frank do not take responsibility for the accuracy of this information and therefore recommend that clients check this at the time of publication.