{
    "version" : "https://jsonfeed.org/version/1",
    "content" : "resources",
    "type" : "single",
    "title" : "Lessons from the 2021 Federal Plain Language Report Card |Digital.gov",
    "description": "Lessons from the 2021 Federal Plain Language Report Card",
    "home_page_url" : "/preview/gsa/digitalgov.gov/bc-archive-content-3/","feed_url" : "/preview/gsa/digitalgov.gov/bc-archive-content-3/resources/lessons-from-the-2021-federal-plain-language-report-card/index.json","item" : [
    {"title" :"Lessons from the 2021 Federal Plain Language Report Card","deck" : "What we learned from examples of web content that received both high and low scores.","summary" : "This event recap highlights best practices, a short case study video, and examples of federal web content that received both high and low scores in the 2021 Plain Language Report Card.","date" : "2022-03-11T17:26:00-05:00","date_modified" : "2025-01-27T19:42:55-05:00","authors" : {"mara-goldberg" : "Mara Goldberg","gabby-fratanduono-king" : "Gabby Fratanduono-King"},"topics" : {
        
            "accessibility" : "Accessibility",
            "communication" : "Communication",
            "content-strategy" : "Content strategy",
            "design" : "Design",
            "plain-language" : "Plain language",
            "user-experience" : "User experience"
            },"primary_image" : { "uid" : "title-card-2021-plain-language-report-card-slide-7-dhs-foia", "alt" :
  "Graphic for the 2021 Plain Language Report Card resource page is a screen capture of slide number seven from the December 2021 event presentation deck. It shows the Department of Homeland Security (DHS) FOIA request page and accompanying text indicating six ways this is a good example of plain language use.", "width" :
  "1200", "height" :
  "630", "credit" :
  "", "caption" :
  "", "format" :
  "png" },"branch" : "bc-archive-content-3",
      "filename" :"lessons-from-the-2021-federal-plain-language-report-card.md",
      
      "filepath" :"resources/lessons-from-the-2021-federal-plain-language-report-card.md",
      "filepathURL" :"https://github.com/GSA/digitalgov.gov/blob/bc-archive-content-3/content/resources/lessons-from-the-2021-federal-plain-language-report-card.md",
      "editpathURL" :"https://github.com/GSA/digitalgov.gov/edit/bc-archive-content-3/content/resources/lessons-from-the-2021-federal-plain-language-report-card.md","slug" : "lessons-from-the-2021-federal-plain-language-report-card","url" : "/preview/gsa/digitalgov.gov/bc-archive-content-3/resources/lessons-from-the-2021-federal-plain-language-report-card/","weight" : "1","content" :"\u003cp\u003eSince 2011, the \u003ca href=\"https://centerforplainlanguage.org/\"\u003eCenter for Plain Language\u003c/a\u003e has issued a yearly report card to show how well federal agencies follow the \u003ca href=\"https://www.plainlanguage.gov/law/\"\u003ePlain Writing Act\u003c/a\u003e. The report card evaluates these agencies on organizational compliance and writing quality.\u003c/p\u003e\n\u003cp\u003eFor the 2021 Federal Plain Language Report Card, the judges focused on the main Coronavirus pages and the main Freedom of Information Act (FOIA) request pages of 21 executive branch agencies, including all 15 cabinet-level departments. Digital.gov and the Plain Language Community shared the \u003ca href=\"https://digital.gov/event/2021/12/08/results-of-the-2021-federal-report-card/\"\u003eReport Card results\u003c/a\u003e.\u003c/p\u003e\n\u003ch2 id=\"the-dos\"\u003eThe Do’s\u003c/h2\u003e\n\u003cp\u003eDuring this event, speaker David Lipscomb provided some useful tips to make web content meet plain language standards:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eInclude introductory text that explains what users should expect and how they will use the page.\u003c/li\u003e\n\u003cli\u003eWrite any action steps in the correct and logical order.\u003c/li\u003e\n\u003cli\u003eChunk content into manageable, short sections.\u003c/li\u003e\n\u003cli\u003eUse large, visible headings that start with clear action verbs.\u003c/li\u003e\n\u003cli\u003ePut the less actionable information at the bottom.\u003c/li\u003e\n\u003cli\u003eKeep language brief and to the point; don’t include extra information that will slow down users.\u003c/li\u003e\n\u003c/ul\u003e\n\n\n\n\n\n\n\n\u003cdiv class=\"image\"\u003e\n  \u003cimg\n        src=\"https://s3.amazonaws.com/digitalgov/2021-plain-language-report-card-slide-6-sba-covid.png\"alt=\"Screen capture of slide number six from the event presentation shows the Small Business Administration (SBA) COVID-19 Relief Options page and accompanying text. On the left, a header in blue text says, Action items tailored to the needs of the target audience. Below that is a list of six sentences in black text, each with an arrow pointing to corresponding examples on the web page. One: Information that the audience is most likely to use appears at the top of the page and is organized for easy next steps. Two: The page highlights resources that speak [to] the target audience\u0026#39;s needs. Three: Clean graphics and restrained use of just a few colors. Four: Helpful, conversational tone and strong action verbs. Five: Text is extremely concise, with no extraneous information included. Six: Effective use of images that directly support section content.\"/\u003e\u003c/div\u003e\n\n\n\u003ch3 id=\"a-quick-case-study\"\u003eA Quick Case Study\u003c/h3\u003e\n\u003cp\u003eThe \u003ca href=\"https://www.dhs.gov/foia\"\u003eDepartment of Homeland Security (DHS) FOIA request page\u003c/a\u003e is a perfect example of an agency following plain language guidelines. David Lipscomb explains how this page received such an outstanding report card score in this short video clip:\u003c/p\u003e\n\n\n\n\n\n\n\u003cdiv\n  class=\"video\"\n  style=\"position: relative; padding-bottom: 56.25%; padding-top: 30px; height: 0; overflow: hidden;\"\n\u003e\n  \n  \u003ciframe src=\"https://www.youtube.com/embed/sl3yiSA-4LY\" title=\"Results of the 2021 Federal Plain Language Report Card\" style=\"position: absolute; top: 0; left: 0; width: 100%; height: 100%;\" allowfullscreen=\"\" frameborder=\"0\" \u003e\u003c/iframe\u003e\n\u003c/div\u003e\n\n\u003ch2 id=\"the-donts\"\u003eThe Don’ts\u003c/h2\u003e\n\u003cp\u003eDavid Lipscomb also shared examples of some mistakes to avoid when producing web content:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eAvoid graphics that don’t convey much information and that visually dominate the page.\u003c/li\u003e\n\u003cli\u003eDon’t include information that doesn’t clearly explain what a user can do with it.\u003c/li\u003e\n\u003cli\u003eDon’t write information reflecting the agency; focus on the user and what they can do.\u003c/li\u003e\n\u003cli\u003eDon’t write long, complex sentences that use legalistic, formal language.\u003c/li\u003e\n\u003cli\u003eAvoid long lists of hyperlinked resources that can overwhelm the user.\u003c/li\u003e\n\u003c/ul\u003e\n\n\n\n\n\n\n\n\u003cdiv class=\"image\"\u003e\n  \u003cimg\n        src=\"https://s3.amazonaws.com/digitalgov/2021-plain-language-report-card-slide-8-dod-foia.png\"alt=\"Screen capture of slide number eight from the event presentation shows the Department of Defense’s (DOD) FOIA request page page and accompanying text. On the right, a header in red text texts says, Aims to provide resources but may overwhelm. Below that is a list of five sentences in black text, each with an arrow pointing to corresponding examples on the web page. One: A graphic that doesn’t convey much information visually dominates the top of the page. Two: Users may struggle to understand how information pertains to them or what they can do with it. Three: Focused on the agency, not the user. Four: Long and complex sentences that use legalistic, formal language. Five: A potentially overwhelming number of options for linked resources.\"/\u003e\u003c/div\u003e\n\n\n\u003cp\u003eWe can continuously use the results of the Plain Language Report Card to guide future website content. These examples, with both high and low report card scores, remind us what we should and shouldn’t do to ensure clear communication for all users.\u003c/p\u003e\n\u003ch2 id=\"additional-resources\"\u003eAdditional Resources\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"https://www.plainlanguage.gov/\"\u003ePlainLanguage.gov\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://centerforplainlanguage.org/\"\u003eCenter for Plain Language\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://centerforplainlanguage.org/2021-federal-plain-language-report-card/\"\u003e2021 Plain Language Report Card\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://digital.gov/event/2021/01/13/2020-federal-report-card-briefing/\"\u003e2020 Federal Report Card Briefing\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://digital.gov/event/2020/07/15/federal-report-card-update/\"\u003eFederal Report Card Update\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n"}
  ]
}