Information Services

Creating Accessible Online Content for Websites and Blogs

Guidance on creating accessible online content for websites and blogs.

Although creating accessible websites and blogs can be a complex issue, the following guidance is aimed at providing a brief and helpful overview. There are official guidelines available that cover this issue in depth. We would recommend you create your University websites using the University's content management system (EdWeb) which will ensure most aspects of accessibility are covered. However, if you are creating a website or blog outwith EdWeb we would recommend you contact Viki Galt (details below) to discuss. If you create a site outside EdWeb, you will need to manually test, and subsequently add an Accessibility Statement, on an annual basis.  This is a legal requirement under the Public Sector Bodies (Websites and Mobile Applications) (No.2) Accessibility Regulations 2018.

The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018

In 2018 The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 were passed into UK Law.

The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018

Building on the Equality Act 2010, Scottish Specific Duty Regulations 2012 and a European Union Directive on the Accessibility of Public Sector Websites and Mobile Applications, this legislation requires all public sector bodies to ensure their websites and applications, including web-based and mobile applications, are accessible.

The regulations cover both internal and external facing websites and applications.

The definition of ‘accessible’ is based on that set by the World Wide Web Consortium (W3C), which is the Web Content Accessibility Guidelines (WCAG) version 2.2 AA 

It also requires all websites, applications and mobile applications to have accessibility statements.

In 2022 a subsequent amendment was made in the:

The Public Sector Bodies (Websites and Mobile Applications) Accessibility (Amendment) (EU Exit) Regulations 2022.

This amendment does not make any change to the current expectations of public sector bodies and the accessibility of its websites and mobile applications, whereby the regulations, exemptions and enforcement process all remain the same as the original European Union legislation adopted into UK law during 2018. The need for the change relates to the UK no longer receiving updates to regulations made in the EU, including that of technical standards. This update will mean the UK government will be able to update the definition of accessibility with the latest version of the Web Content Accessibility Guidelines.

Accessibility Statements 

Accessibility statements must be published in an HTML format and linked to from the footer of each page within the site. They must also strictly follow the government template.

Government Sample Accessibility Statement Template

To write an accessibility statement you must test the website or application manually and not just use automated testing. In addition, it is a requirement that you test with various pieces of assistive software including screen readers such as JAWS/NVDA, voice recognition software such as Dragon and mobile accessibility features such as voice over/talk back.  

Accessibility Statements must be published in a web browser or application using the Hyper Text Markup Language (HTML) format, and linked via the footer of each page within the system.

The Disability Information team runs training on both constituent parts, namely on how to undertake the testing and write an Accessibility Statement. If you would like to attend this training please contact Viki Galt, Head of Disability Information at the contact details given at the bottom of this page.

  • Website and Application Accessibility Testing Training;
  • Accessibility Statement Writing Training.

British Standards Institute Code of Practice

For other standards of compliance, please refer to the British Standards Institute (BSI) Code of Practice BS8878, which can be ordered via telephone on (+44) 20 8996 9001, or by emailing

General Website Accessibility Considerations


  • Ensure the standard font colour and background colour have a good contrast ratio e.g. a ratio of at least 4.5:1, and ideally a dark text on a light background.
  • Ensure the font is in a sans serif font and large enough (minimum font size 12).
  • Provide transcripts for audio clips and captions for videos.
  • Provide alternative text for all images, charts and graphs e.g. make sure all images have a meaningful written description. 
  • Ensure users can magnify the content to at least 200% without the use of assistive software, and that the pages reflow (users only have to scroll vertically and not horizontally as well).
  • Ensure the site can be viewed in landscape and portrait modes
  • Ensure text is not displayed as images
  • Customisation - ensure the site is compatible with browser functionality so it is easy for people to change font size, colour and contrast and there is no loss of content. For more information on how to do this each various browsers visit   

Using browsers to customise webpages


  • Ensure all content can be navigated to and interacted with using a keyboard only (without a mouse) and there are no keyboard traps.
  • Avoid flashing, scrolling or moving images or text. If there is any movement, ensure the user can stop this, and that no images or text flash more than 3 times per second.
  • Ensure no information is conveyed by colour or sound only e.g. priority items are shown in red.
  • Ensure no content is time limited e.g. users have as long to look at a page as they wish.
  • Alert users when a new window/pop up opens.
  • Ensure link text clearly states what the link is - avoid using URL's in full or "click here"


  • Ensure content and structure is readable, predictable and consistent
  • Ensure navigation is consistent
  • Add a 'skip to main content' option for keyboard and screen reader users.
  • Ensure pages are clearly structured using style sheets, text is broken up by sub-headings, and edit text to be simple and direct.
  • Ensure there is data validation for any input boxes, and that these error messages are accessible. Moreover, messages should give a clear description of how to fix the problem and identify the error location.


  • Ensure the compatibility of the website with assistive technology such as screen readers and voice recognition software. Plain HTML is easy for such technologies to convert. 
  • Ensure you have an Accessibility Statement published and that this is up to date.
  • Wherever possible we would encourage you to involve disabled people in the creation of your website to provide feedback and advice.


If you have any further queries or would like an accessibility audit report on your website please contact Viki Galt, Head of Disability Information, contact details below.

Alternative Formats

If you require this document in an alternative format please contact Viki Galt, Head of Disability Information.

Viki Galt

Head of Disability Information

  • Information Services

Contact details



Argyle House
Floor F West
3 Lady Lawson Street

Post Code

BSL users can contact me via Contact Scotland BSL, the on-line British Sign Language interpreting service. Find out more on the Contact Scotland BSL website.