{"id":162,"date":"2022-06-14T06:21:23","date_gmt":"2022-06-14T06:21:23","guid":{"rendered":"http:\/\/www.big-sandbox.uk\/kb\/?p=162"},"modified":"2023-09-22T13:39:28","modified_gmt":"2023-09-22T13:39:28","slug":"162","status":"publish","type":"post","link":"https:\/\/bigbluecomms.com\/kb\/162\/","title":{"rendered":"Making readability and accessibility guidelines a non-negotiable requirement"},"content":{"rendered":"\n

Plain language and clear structure help everyone, including people with disabilities. Readability is a primary goal that guides all digital productions, from reports to social media content to presentations.<\/p>\n\n\n\n

Readable, accessible content is particularly necessary in public-facing communication.<\/p>\n\n\n\n

Plain language with common words helps more people to understand and make informed decisions. Clear structure and navigation enable faster scanning and retention.<\/p>\n\n\n\n

How to achieve readable, accessible content: \u2018Write for age 9\u2019<\/h2>\n\n\n\n

A low reading level assists readers who do not speak English as a first language, who may be reading in challenging conditions, or who may face impairments related to reading, comprehension, or attention. Below are some guidelines to ensure the majority are able to read your work:<\/p>\n\n\n\n

    \n
  1. Write for age 9<\/li>\n\n\n\n
  2. Always use shorter, plain English words, terms, sentences, and paragraphs over longer alternatives<\/li>\n\n\n\n
  3. Our 80:20 rule: Max 80 words per paragraph, 20 words per sentence<\/li>\n\n\n\n
  4. Use an active voice, instead of a passive one<\/li>\n\n\n\n
  5. Avoid jargon, abbreviations, and acronyms wherever possible<\/li>\n\n\n\n
  6. Avoid unfamiliar text that slows reading, understanding, and confidence<\/li>\n\n\n\n
  7. Minimise punctuation except for full stops<\/li>\n\n\n\n
  8. Write in first-person and second-person perspectives to engage readers<\/li>\n\n\n\n
  9. Remember that plain language also helps specialist audiences and does not diminish or dumb down reading experiences<\/li>\n\n\n\n
  10. Remember that specialist audiences may include readers with impairments and language barriers, and who are reading in challenging conditions<\/li>\n<\/ol>\n\n\n\n
    \n

    \u201cDifficult or complex text may be appropriate for most members of the intended audience… But there are people with disabilities, including reading disabilities, even among highly educated users with specialized knowledge of the subject matter.<\/p>\n\u2014 www.w3.org<\/cite><\/blockquote>\n\n\n\n

    Text choices and typography to improve readability<\/h3>\n\n\n\n
      \n
    1. Consider larger fonts of 14-point or above with large line spacing of 1.5x<\/li>\n\n\n\n
    2. Use left-justified text because it is easiest to read<\/li>\n\n\n\n
    3. Use numbered lists and bullet lists often<\/li>\n\n\n\n
    4. Use bold for emphasis, and use all formatting such as italics, bold, and uppercase lettering with caution because they can slow reading<\/li>\n\n\n\n
    5. Use \u2018style headings\u2019 in software like Microsoft Word to create ordered headings, formatting, and tables of contents<\/li>\n\n\n\n
    6. For headings, use a font size that is at least 20% larger than the normal text. If further emphasis is required, then use bold<\/li>\n\n\n\n
    7. Use sufficient contrast levels between background and text<\/li>\n\n\n\n
    8. Provide clear descriptions of hyperlinks rather than only a URL<\/li>\n<\/ol>\n\n\n\n
      \n

      \u201cMany people with cognitive disabilities have a great deal of trouble with blocks of text that are justified (aligned to both the left and the right margins). The spaces between words create \u201crivers of white\u201d running down the page, which can make the text difficult for some people to read… The best way to avoid this problem is not to create text layout that is fully justified.<\/p>\n<\/blockquote>\n\n\n\n

      \u2014 www.w3.org<\/p>\n\n\n\n

      Accessible navigation and structure: design for readability and accessibility<\/h2>\n\n\n\n

      Digital productions should start with navigation and structure that are designed to assist readability and accessibility.<\/p>\n\n\n\n

        \n
      1. Focus on navigation and structure first<\/li>\n\n\n\n
      2. Design for scanning because people generally scan first and then read what is relevant to them<\/li>\n\n\n\n
      3. Include a table of contents<\/li>\n\n\n\n
      4. Use relevant \u2018style headings\u2019, whether using Microsoft Word, Google Docs, XD, InDesign, or WordPress<\/li>\n\n\n\n
      5. Use heading levels based on hierarchy, not appearance<\/li>\n\n\n\n
      6. Use H1 style headings for page headings, then H2 for sub-headings within pages, and then occasional H3 headings beneath H2 sub-headings<\/li>\n<\/ol>\n\n\n\n
        \n

        \u201cIf you created a new public sector website on or after 23 September 2018, you must now meet accessibility standards and publish an accessibility statement. You need to review and update your statement regularly.<\/p>\n\u2014 https:\/\/www.gov.uk<\/cite><\/blockquote>\n\n\n\n

        Questions to ask<\/h2>\n\n\n\n