RCGP accessibility statement

This website is run by the Royal College of General Practitioners. 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’re also making the website text easy to understand.

Help adjusting your device or browser

AbilityNet shows ways you can make your device and browser easier to use. It covers how to:

  • use your keyboard instead of a mouse
  • talk to your device or make it talk to you
  • make text larger
  • change your colours

How accessible is this website?

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

  • some content is not compatible with screen readers
  • some parts of the website are difficult to navigate using just a keyboard
  • most of our PDFs are not fully accessible
  • some of our link text is not clear and can be confusing if you’re using a screen reader
  • a lot of our video content needs titles and captions
  • some images and media don’t have alternative text
  • you need to scroll horizontally when looking at some content on a small phone
  • there is low colour contrast in some sections of the website 

How we’re improving accessibility

We do automated accessibility testing twice a week. This helps us to understand what issues there are and how to fix them. It also ensures we can stay on top of any new issues that arise. 

We are also improving accessibility by:  

  • making content easier to read and navigate
  • rolling out an accessible PDF template

Tell us about an accessibility problem

We are always looking for ways to improve the website. Please contact us to report an accessibility problem that isn’t listed on this page.

You can also request website content in a different format like accessible PDF, large print, easy read, audio recording or braille.

Email: website@rcgp.org.uk

Phone: 020 3188 7573

We’ll respond to your request within 3 working days.

Technical information about this website’s accessibility

We’re committed to making the RCGP website accessible. Our aim is to be fully compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. We are partially compliant due to the non-compliances listed below.

Website navigation and readability

Some form fields don’t change appearance when they are selected. This fails WCAG 2.1 success criterion 2.4.7. 

Some link text needs to be improved so it is unique to that page and clearly explains the destination. This fails WCAG 2.1 success criterion 2.4.4.

The ‘Skip to content’ link doesn’t work and titles need to be added to iframes. This fails WCAG 2.1 success criterion 2.4.1.

Some pages and tables are missing headings and some navigation needs to be coded semantically as a list. This fails WCAG 2.1 success criterion 1.3.1.

Some links can’t be selected by screen readers as they contain no content inside the link or href. This fails WCAG 2.1 success criterion 4.1.2.

Every page should specify what language it is written in, within the HTML. This fails WCAG 2.1 success criterion 3.1.1.

All media and images need to have alternative text. This fails WCAG 2.1 success criterion 1.1.1.

Some sections of text don’t have good contrast with the background. This fails WCAG 2.1 success criterion 1.4.3.

Ensure links are distinguished by more than just colour. This fails WCAG 2.1 success criterion 1.4.1.

Mobile design

On small phones, some content scrolls horizontally. This fails WCAG 2.1 success criterion 1.4.10.

Pinch-to-zoom needs to be enabled so users can easily magnify content on a mobile device. This fails WCAG 2.1 success criterion 1.4.4.

Forms

All form controls and dialogs need labels. This fails WCAG 2.1 success criterion 1.3.1.

Form fields must identify what their purpose is programmatically to allow browsers to autocomplete known information. This fails WCAG 2.1 success criterion 1.3.5.

Some forms don’t have a submit button which can prevent people who use assistive technologies from submitting the form. This fails WCAG 2.1 success criterion 3.2.2.

PDFs

Some PDFs need to be made machine readable. This fails WCAG 2.1 success criterion 1.1.1.

Many PDFs need to be tagged, have the correct heading structure and clearly defined titles. This fails WCAG 2.1 success criterion 1.3.1 and 2.4.2. 

Some long PDFs need to include bookmarks. This fails WCAG 2.1 success criterion 2.4.5.

Code validation

Some pages have duplicate ID attributes. This fails WCAG 2.1 success criterion 4.1.1.

Preparation of this accessibility statement

This statement was prepared on 23 September 2020. It was last reviewed on 30 September 2020.

This website was tested in-house on 23 September 2020 using Silktide.

The item has been added to your basket.

Continue shopping

Go to basket

This item is out of stock.

Continue shopping

The item is out of stock.

Yes Continue shopping

An error occured adding your item to the basket:

Continue shopping