10
Oct

One year on – Plain Language Issues persist in Gov. websites despite Plain Writing Act

This week marks the first anniversary of the US Plain Writing Act on October 13th. The act is all about clear and transparent communications. Given the anniversary, it’s useful to check how agency websites are complying.

So, last week, on October 3rd we scanned 31 federal agency websites with VisibleThread. The scans revealed some agencies doing really well, others remain challenged.

We plan to publish the full results soon. I wanted to share in this blog post some initial findings. These are items that caught our eye as we reviewed the scans. We hope these will be helpful for US federal agencies looking to comply with the Plain Writing act of 2010.

Why the Act?

Let’s remind ourselves why congressman Braley sponsored this act and why president Obama signed it.

Reason 1 – Improve Customer Engagement: Clarity in documents and websites means citizens are more likely to achieve their goals. Whether you are filing a tax return or trying to understanding labor rights; clear instructions mean we have a higher chance of completing an action.

Reason 2 – Reduce Cost: If the Feds can make it easier for people to engage, it means lower cost. It means lower cost for government due to less follow-up calls, letters and less time spent chasing. It cuts down on possible litigation due to misunderstood terms and conditions.

Plain Language is the mechanism that drives clarity for websites and documents.

The scanned results

Here are just two of the websites that we scanned:

Pension Benefit Guaranty Corporation (www.pbgc.gov) & Federal Highway Administration (www.fhwa.dot.gov). The metrics:

WebsiteReadabilityPassive LanguageLong SentencesAvg SentenceComplex Word HitsDensity of hits
www.pbgc.gov439454814.33%20.30%1512292.79668
www.fhwa.dot.gov321473313.04%17.98%156502.02196

The Pension Benefit Guaranty Corporation scored a little over 20% when measured for long sentences. Long sentences exceed 25 words. In the context of web communications, this score is not good. The Fed Highway Administration wasn’t far behind at close to 18%. Equally, passive density was too high for the sites. Note that we did limit the scan to the first 100 pages of content, in both cases.

Hidden in the weeds – badness

One of the specific areas that caught our attention was the FAQ (Frequently Asked Questions) section of the pension site at: https://www.pbgc.gov/about/faq.html

Aside from the usage of an acronym ‘FAQ’ which is likely unfamiliar to the target demographic (i.e. aged persons), we found many issues with the content itself.

Now, you should note that the FAQ pages are reasonably well laid out and clear. So, the web design guys have done pretty well. The real issues lie in the content under the expandable answers. Under here, lurks some really bad stuff that we picked up in the scan. It’s the proverbial ‘under the rug’ area of any website.

For instance, at: https://www.pbgc.gov/about/faq/pg/general-faqs-about-pbgc.html , in answer to the very first question: ‘What is the Pension Benefit Guaranty Corporation (PBGC)?’ we get this:

A: PBGC is a federal agency created by the Employee Retirement Income Security Act of 1974 (ERISA) to protect pension benefits in private-sector traditional pension plans known as defined benefit plans. If your plan ends (this is called “plan termination”) without sufficient money to pay all benefits, PBGC’s insurance program will pay you the benefit provided by your pension plan up to the limits set by law. (Most people receive the full benefit they had earned before the plan terminated.) Our financing comes from insurance premiums paid by companies whose plans we protect, from our investments, from the assets of pension plans that we take over as trustee, and from recoveries from the companies formerly responsible for the plans, but not from taxes. Your plan is insured even if your employer fails to pay the required premiums.

Each long sentence is highlighted in light blue. Maroon highlights passive language.

So, let’s assume we understand the purpose of the agency, the next question ups the ante. In answer to ‘What can PBGC tell me about my pension?’ we have:

A: If you’re a participant in a pension plan that PBGC insures but that has not yet been taken over (“trusteed”), PBGC generally will have no information specifically about you, your plan, or your benefits under that plan. PBGC gathers this information only after PBGC trustees the plan. This means you’ll find only general information below about our insurance programs and how they operate, including our guarantees. If PBGC has trusteed your pension plan, we’ll have only limited information about your plan and your benefits until we’ve had time to obtain and review your plan’s records-typically after several months.

The rest of this area of the website has equally lengthy and complex language. Clearly, not achieving the aim of the Plain Writing act.

Long Sentences and Passive Voice, why important?

VisibleThread analyzes websites and documents for a number of metrics. While other metrics (complex density, hidden verbs, readability) are useful; long and passive sentences are the ‘low hanging fruit’ of the Plain Language world. If all you do today, is just cut your long sentences down and write in active voice, clarity will immediately improve.

To re-iterate, two of the easiest ways you can reduce complexity & introduce clarity are:

  1. Split long sentences and
  2. Convert passive into active voice.

Easy Steps to simplify your website content

What simple steps can you take to improve website quality?

  1. Scan for and eliminate Long sentences: Aside from being harder to interpret, long sentences often mask several different information concepts. They are thus harder to understand. If you split the sentence, it is an excellent first step to achieve clarity. For websites, where readers are actually visually skimming, long sentences are especially inappropriate.
  1. Rewrite passive with a verb driven approach: Active (verb preceding noun) rather than passive (subject preceding verb) language makes for clearer requirements. It forces an explicit reference to the ‘actor’. The actor is the person or entity responsible for performing the action. This reduces ambiguity and improves likelihood your customers will complete an action.

Summary Takeaways

–          One year on, some agencies are still falling short of complying with the Plain Writing act.

–          We scanned several agency websites with VisibleThread and found some poor examples.

–          If you eliminate long sentences & passive language, clarity will improve.

If you want to try VisibleThread Docs sign up here for a 7-day free trial
https://www.visiblethread.com/2011/10/one-year-on-plain-language-issues-persist-in-gov-websites-despite-plain-writing-act/
www.visiblethread.com
crawl=CC-MAIN-2019-35
105911
application/http; msgtype=response
sha1:3JX4JTMDLB5FKHIRIAKDHFNDEI7B7Z7F
<urn:uuid:364a6156-ca58-4840-a59e-e37cf00237de>
2019-08-25T08:54:40Z
46.22.128.42
text/html
sha1:5GCFXKMBHPW36WQHLL6QBJWWR25D7J42
<urn:uuid:4e80166a-5f4c-4c8d-a57d-1a9b561d92d0>
https://www.visiblethread.com/2011/10/one-year-on-plain-language-issues-persist-in-gov-websites-despite-plain-writing-act/
response
<urn:uuid:5380c5c5-7c96-425f-818b-0e7176ced056>
isPartOf: CC-MAIN-2019-35
publisher: Common Crawl
description: Wide crawl of the web for August 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-214.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/