Frequently Asked Questions

Frequently asked accessibility questions

Some questions come up often from people that are starting out to learn digital accessibility best practices, in fact, you don't necessarily have to be new to the field, as there's so much to learn and that willingness to continue learning makes digital media and websites much easier to use for everybody, especially people that rely on assistive technology to access digital content.

We've put together some of our FAQs here, it may be a useful place to start, especially if you're just starting out on this journey, if you are just starting out, welcome to the digital accessibility community.

How do I create accessible content?

Specific guidance depends on what content you are trying to make accessible but there are always things you can do to be more inclusive with your content.

We have produced a range of guidance to help and support accessible content creation including Microsoft Office documents, PDFs, images and graphics, maps, videos and more.

There are also excellent guides and videos available from Microsoft, Adobe and LinkedIn Learning.

What needs to be digitally accessible?

Websites need to be digitally accessible, as well as the content published on websites. This content includes “online estates” including Blackboard resources, blogs, online guides, website text, digital brochures, audio and video resources, Microsoft Office and PDF documents, social media content.

All these types of digital content need to be accessible for all audiences. This means public facing, student facing and staff facing content all must be accessible.

What is the most accessible format?

If possible, it is always good to provide your content as an HTML web page. Obviously this is not a solution for all content types and there are other actions you can take to improve Microsoft office and PDF accessibility as well.

What is the legislation and what does it say?

The Public Sector Bodies Accessibility Regulations (2018) say that a public sector body must make sure that websites and mobile apps are accessible. International web standards called Web Content Accessibility Guidelines (WCAG 2.1 AA) define what is needed for accessibility.

Public sector bodies must also publish an accessibility statement on each of their websites which tells users how accessible the website is, what problems are know about and how to contact for help if they have a problem with accessibility.

How is digital accessibility assessed?

According to the WCAG 2.1 AA guidelines. These are international recommendations for improving web accessibility and contain standards which need to be met to be classified as accessible.

WCAG focus on principles of accessibility and emphasise the need to think about the different ways that people interact with content:

For example, users might:

  • use a keyboard instead of a mouse
  • change browser settings to make content easier to read
  • use a screen reader to ‘read’ (speak) content out loud
  • use a screen magnifier to enlarge part or all of a screen
  • use voice commands to navigate a website

This means you need to do things like:

  • provide captions for video
  • make sure content is structured logically and can be navigated and read by a screen reader - this also helps if stylesheets are disabled
  • not use colour as the only way to explain or distinguish something
  • use text colours that show up clearly against the background colour
  • make sure everything works for keyboard-only users
  • let people play, pause and stop any moving content
  • provide a ‘skip to content’ link
  • use descriptive titles for pages and frames.

Does the legislation only apply to public websites?

No, the legislation applies to all websites. This includes internal websites which are available to staff and/or students only, as well as public websites.

What about websites supplied by an external supplier?

These are still subject to the legislation. We must work with the supplier to make sure they are improving accessibility of their website. We need to improve accessibility of the aspects we have control over eg content.

Site preferences

Please feel free to display our site, your way by finding the preferences that work best for you. We do not track any data or preferences at all, should you select any options in the groups below, we store a small non-identifiable token to your browser's Local Storage, this is required for your preferencesto persist across pages accordion be present on repeat visits. You can remove those tokens if you wish, by simply selecting Unset, from each preference group.


Code block theme

Code theme help

Code block themes can be changed independent of the site theme.

  • Default: (Unset) Code blocks will have the same theme as the site theme.
  • Light 1: will be default for users viewing the light theme, this maintains the minimum 7:1 (WCAG Level AAA) contrast ratio we have used throughout the site, it can be quite difficult to identify the differences in colour between various syntax types, due to the similarities in colour at that contrast ratio
  • Light 2: drops the contrast for syntax highlighting down to WCAG Level AA standards (greater than 4.5:1)
  • Dark: Syntax highlighting has a minimum contrast of 7:1 and due to the dark background differences in colour may appear much more perceivable


Motion & animation

Motion & animation help

  • Default (Unset): Obeys device settings, if present. If no preference is set, there are subtle animations on this site which will be shown. If you have opted for reduce motion, smooth scrolling as well as expanding and collapsing animations will no longer be present, fading transtitions and micro animations will still be still present.
  • None: All animations and transitions are completely removed, including fade transitions.


Underline all links

Underline all links help

  • Default (Unset): Most links are underlined, with a few exceptions such as: the top level links in the main navigation (on large screens), cards, tags and icon links.
  • Yes: Will add underlines to the exceptions outlined above, resulting in every link being underlined

Text and paragraphs

Font size (main content)

Font size help

This setting does not apply to the site's header or footer regions

  • Default (Unset): Font sizes are set to site defaults
  • Selecting Large or Largest will increase the font size of the main content, the size of the increase depends on various factors such as your display size and/or zoom level. The easiest way to determine which option suits you best would be to view this text after clicking either size's button
Letter spacing

Letter spacing help

  • Default (Unset): Default letter spacing applies
  • Increased: Multiplies the font size by 0.12 and adds the sum as spacing between each character
Line height

Line height help

  • Default (Unset): all text has a minimum line height of 1.5 times the size of the text
  • Increased: all text has a line height of twice the size of the text
Line width

Line width help

  • Default (Unset): all text has a maximum line width of 80 REM units (this averages around 110 characters per line)
  • Decreased: all text has a maximum line width of 55 CH units (this averages around 80 characters per line)
Paragraph spacing

Paragraph spacing help

  • Default (Unset): The space between paragraphs is equivalent to 1.5 times the height of the paragraph's text
  • Increased: The space between paragraphs is equivalent to 2.25 times the height of the paragraph's text
Word spacing preference

Word spacing help

  • Default (Unset): No modifications to word spacing are present
  • Increased: Spaces between words are equivalent to 0.16 times the font size