Step by step guide

Accessible web content

This page includes some basic steps to help you get started developing web content that is accessible to people with disabilities.

These tips are good practice to help you meet Web Content Accessibility Guidelines (WCAG) requirements.

Step by step guide

  • AVOID PDFs, they are not accessible, harder to find, use and maintain. In addition, they are not responsive, which means users will not be able to read on smaller screens such as tablets and mobile phones (Over 70% of our users use mobile devices to access our content). You can find more information about why content should be published in HTML and not PDF
 
  • Provide us with a content in a word document ONLY. When creating content keep text clear and brief, use simple language and formatting. Further information for writing for web.
 
  • Make your content in the word document well-structured by using page title, headings, bullet points and body content, further information can be found on structure section.
 
  • Insert links that make sense out of context and avoid ‘click here’, it’s not accessible to visually impaired users that use a screen reader. You can find out more about how to use links on your content on the writing for web webpage.
 
  • Tone of voice isn’t what we say but how we say it. It’s the language we use, the way we build sentences, the sound of our words and the personality we communicate. 
 
  • Tables should be used for data and not used to facilitate page or document layouts. Screen readers will read the content of a table in a linear fashion — left to right, top to bottom. Simple data tables are much easier to navigate. Complex tables that include nested tables or that require two rows in order to explain the information contained in the columns, are not accessible and should be avoided. You can find more information about accessible tables
 
  • Avoid using text within pictures, for example image infographics, this format is NOT accessible. A screen reader cannot recognise the text within the image infographic because it is an image. Further information about the use of images can be found on our website.
 
  • Finally, when your content is ready, please send it to Welsh translation. Once you have received the bilingual content raise a ticket through the Intranet IT Help Desk.

Please make sure to follow the instruction bellow: