<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>CalmIT</title>
	<atom:link href="http://calmit.org/feed/" rel="self" type="application/rss+xml" />
	<link>https://calmit.org</link>
	<description>Remote Support</description>
	<lastBuildDate>Tue, 05 May 2026 10:25:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>

<image>
	<url>https://calmit.org/wp-content/uploads/Circle_blue-1.png</url>
	<title>CalmIT</title>
	<link>https://calmit.org</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>test</title>
		<link>https://calmit.org/test/</link>
		
		<dc:creator><![CDATA[n0t2hungry]]></dc:creator>
		<pubDate>Tue, 05 May 2026 09:55:18 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://calmit.org/?p=4209</guid>

					<description><![CDATA[Most people don’t read through the content we put on our websites. They skim and scan the pages, “taking in headings, the beginnings of paragraphs, and first words of sentences.” (1) They’re looking for something that strikes their attention or matches the question or need they have. If they find it, they dig in and [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Most people don’t read through the content we put on our websites. They skim and scan the pages, “taking in headings, the beginnings of paragraphs, and first words of sentences.” (<a href="#refs">1</a>) They’re looking for something that strikes their attention or matches the question or need they have. If they find it, they dig in and read more carefully.</p>
<p><strong>To help our web visitors find what they’re looking for, we can create webpages that are easy to scan</strong>.<br />
Here are 10 “how-to” tips.</p>
<ol>
<li><a href="#toc">Include a table of contents</a></li>
<li><a href="#start">State the most important information in the first two paragraphs</a></li>
<li><a href="#short">Chunk content in short paragraphs</a></li>
<li><a href="#mainidea">Put only one main idea in a paragraph</a></li>
<li><a href="#headings">Bold headings and subheadings</a></li>
<li><a href="#frontload">Front load headings with significant words</a></li>
<li><a href="#bullets">Use bullets, numbered lists, and numerals</a></li>
<li><a href="#center">Don’t center text on the page</a></li>
<li><a href="#links">Make your links meaningful</a></li>
<li><a href="#testing">Test your site with a few users</a></li>
</ol>
<p><a href="#top">Back to top</a></p>
<h3>1 | <span id="toc"></span>Include a Table of Contents</h3>
<p>You can start webpages (especially longer ones) with a table of contents. This gives readers a quick <strong>snapshot of the content</strong> they’re going to find on that page. The items in the table of contents should match the major headings or sections of the page and be linked to those sections, so that users can “rappel like rock climbers down the text.” (<a href="#refs">2</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>2 | <span id="start"></span>State the Most Important Information in the First Two Paragraphs</h3>
<p>We have to <strong>state the essential message of the page first,</strong> right off the bat. Immediately. In the first two paragraphs. Why? Because web visitors give 80% of their attention to what’s “above the fold” on the webpage. (<a href="#refs">3</a>) “Above the fold” means the content they initially see when they land on the page (without scrolling).</p>
<p>Putting the most important information first means that web users will actually see it. Of course, doing so violates the rules of writing we learned in high school. We’re supposed to start with a nice intro, lay the foundation, give some background and context, and kind of <em>ease into</em> our topic.</p>
<p>But writing for the web is very different from writing for print. Giving a quick overview of the content in the first two paragraphs of a webpage “helps the reader get the point and purpose of a page instantly, letting the user make a quick judgement whether to read on for a bit more detail.” (<a href="#refs">4</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>3 | <span id="short"></span>Chunk Content in Short Paragraphs</h3>
<p><strong>Short and concise paragraphs are easier to scan</strong>—and they get twice as many eye fixations as long paragraphs. (<a href="#refs">5</a>) Web users also pay more attention to the first words in a sentence and to the first and last sentences in a paragraph. So put keywords or <strong>information-carrying words first</strong>, where they’ll catch the eye.</p>
<p><strong>How short is short?</strong> Less than 100 words seems to be the conventional wisdom. Cut out what’s unnecessary. Start a new paragraph when you veer away from the single point of the paragraph. (<a href="#refs">6</a>)</p>
<p>Want more info on <em>how</em> to chunk? Try our companion page <a href="https://zenpages.org/webwriting/chunking/"><em>Chunking Your Content</em></a></p>
<p><a href="#top">Back to top</a></p>
<h3>4 | <span id="mainidea"></span>Put Only One Main Idea in a Paragraph</h3>
<p>Rule of thumb: Limit each paragraph to one main idea. <strong>Front load your message</strong> at the beginning of the paragraph. “While a meandering introductory clause may seem like a good idea to you, the reader might stop reading–before [getting] to the heart of your sentence.” (<a href="#refs">7</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>5 | <span id="headings"></span>Bold Headings and Subheadings</h3>
<p>Headings and subheadings are one of the main ways that web readers skim the page. They act as “landmarks.” (<a href="#refs">8</a>)</p>
<p>To write strong headings:</p>
<ul>
<li><strong>Make headers into questions</strong> your visitors ask.</li>
<li><strong>Write headers as action statements</strong>.</li>
<li><strong>Make headings stand out</strong> visually.</li>
<li><strong>Keep headings short</strong>. Readers see the first two words most clearly. (<a href="#refs">9</a>)</li>
</ul>
<p>In sum: “the more efficiently you tell them what it is you’ve got, the better your heading will work.” (<a href="#refs">10</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>6 | <span id="frontload"></span>Front Load Headings with Significant Words</h3>
<p>Start your headings with <strong>content-significant words</strong>. Users scan down the left margin and notice the first two words. It also helps search engines. (<a href="#refs">11</a>)</p>
<p><strong>Examples:</strong></p>
<ul>
<li>Purposes of evaluation</li>
<li>IDEA’s definition of “child with a disability”</li>
<li>Identifying children for evaluation</li>
<li>Giving parents notice</li>
<li>Parent consent</li>
<li>Timeframe for initial evaluation</li>
</ul>
<p><a href="#top">Back to top</a></p>
<h3>7 | <span id="bullets"></span>Use Bullets, Numbered Lists, and Numerals</h3>
<p><strong>Bullets</strong> break up walls of text and are easy to scan. (<a href="#refs">12</a>)</p>
<p><strong>Numbered lists</strong> help with step-by-step tasks.</p>
<p><strong>Use numerals</strong> instead of spelling out numbers. (<a href="#refs">13</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>8 | <span id="center"></span>Don’t Center Headings or Text on the Page</h3>
<p>Centering text doesn’t work well on the web. Users focus on the left margin. Only 30% of attention goes to the right side. (<a href="#refs">14</a>)</p>
<p>Keep headings:</p>
<ul>
<li><strong>Left aligned</strong></li>
<li>Styled using <strong>HTML heading tags</strong></li>
</ul>
<p><a href="#top">Back to top</a></p>
<h3>9 | <span id="links"></span>Make Your Links Meaningful</h3>
<p>Key findings:</p>
<ul>
<li>Users <strong>do</strong> pay attention to links.</li>
<li>Links on the <strong>left margin</strong> get more attention.</li>
<li>Users want to predict what they’ll find if they click.</li>
</ul>
<p><strong>Use content words</strong> in links. (<a href="#refs">16</a>)<br />
<strong>First two words</strong> matter most. (<a href="#refs">17</a>)<br />
<strong>Use action phrases</strong> for action links. (<a href="#refs">18</a>)</p>
<p>Avoid “click here.” (<a href="#refs">19</a>)</p>
<p>Example:</p>
<div style="padding-left: 30px;"><span style="color: #3366ff;">See pictures of Skeletar</span>. (<a href="#refs">20</a>)</div>
<p><a href="#top">Back to top</a></p>
<h3>10 | <span id="testing"></span>Test Your Site with a Few Users</h3>
<p><strong>User testing</strong> helps you create pages that work for most visitors. Nielsen suggests you can test with as few as 5 users. (<a href="#refs">21</a>)</p>
<p>If you want to know more:</p>
<ul>
<li><a href="http://www.useit.com/alertbox/20000319.html" target="_blank">Why You Only Need to Test with 5 Users</a></li>
<li><a href="http://www.useit.com/alertbox/20030120.html" target="_blank">Recruiting Test Participants</a></li>
</ul>
<p><a href="#top">Back to top</a></p>
<h3>Want to read another section of Writing for the Web?</h3>
<ul>
<li><a href="/webwriting/reading">How people read on the web</a></li>
<li>Helping readers skim and scan (you’re here)</li>
<li><a href="https://zenpages.org/essential-message-first/">Putting your essential message first</a></li>
<li><a href="/webwriting/chunking">Chunking your information</a></li>
<li><a href="/webwriting/headings">Using headings and subheadings</a></li>
<li><a href="/webwriting/plain">Writing in plain language</a></li>
</ul>
<p><span id="refs"></span><br />
<a href="#top">Back to top</a></p>
<h3>References</h3>
<p><!-- Reference list unchanged --></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Installing ScreenConnect on a Mac</title>
		<link>https://calmit.org/installing-screenconnect-on-a-mac/</link>
					<comments>https://calmit.org/installing-screenconnect-on-a-mac/#comments</comments>
		
		<dc:creator><![CDATA[n0t2hungry]]></dc:creator>
		<pubDate>Mon, 18 Aug 2025 11:22:08 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://calmit.org/?p=46</guid>

					<description><![CDATA[1. Download the ScreenConnect Installer ScreenConnect.ClientSetup.pkg 2. Open Finder and navigate to the downloaded .pkg file Open Finder and navigate to the location of the package. Note: Depending on your browser, you may not need to open Finder to locate the .pkg file. 3. Hold the Ctrl key and click the .pkg file (if this [&#8230;]]]></description>
										<content:encoded><![CDATA[<div id="section_3" class="mt-section">
<div id="section_5" class="mt-section">
<h3>1. Download the ScreenConnect Installer <a href="/wp-content/uploads/ScreenConnect.ClientSetup.pkg">ScreenConnect.ClientSetup.pkg</a></h3>
<h3></h3>
<h3 class="editable">2. Open Finder and navigate to the downloaded .pkg file</h3>
<p>Open Finder and navigate to the location of the package.</p>
<div class="alert alert-info style-wrap" title="Note">
<p><strong>Note</strong>: Depending on your browser, you may not need to open Finder to locate the .pkg file.</p>
</div>
<p><img loading="lazy" decoding="async" class="" src="https://calmit.org/wp-content/uploads/Downloaded.png" width="729" height="215" /></p>
</div>
<div id="section_6" class="mt-section">
<h3 class="editable">3. Hold the Ctrl key and click the .pkg file (if this doesn&#8217;t work go to point 5 below)</h3>
<div class="mt-contentreuse-widget" data-page="ConnectWise_ScreenConnect_Documentation/Get_started/Remote_access_guide/Install_the_Mac_access_agent" data-section="3. Hold the Ctrl key and click the .pkg file" data-show="false">
<div id="s62465" class="mt-include">
<p>In order to run the package, you must open it from the context menu. Press the <strong>Ctrl</strong> key and click on the .pkg file. From the pop-up menu, click <strong>Open</strong> to run the file.</p>
<div class="alert alert-warning style-wrap" title="Note">
<p><strong>Important:</strong> If you double-click to run the installer, you will not see an option to <strong>Open</strong> it. You must open it from the context menu.</p>
</div>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/34870/MacInstallerContextMenu.png?revision=1" alt="MacInstallerContextMenu.png" /></p>
<p>During installation, if you see the following &#8220;Installer&#8221; prompt, click <strong>OK</strong>.</p>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/27108/MacInstallerPrompt.png?revision=1" alt="MacInstallerPrompt.png" /></p>
</div>
</div>
</div>
<div id="section_7" class="mt-section">
<p>&nbsp;</p>
<h3 class="editable">4. Open the .pkg file</h3>
<div class="mt-contentreuse-widget" data-page="ConnectWise_ScreenConnect_Documentation/Get_started/Remote_access_guide/Install_the_Mac_access_agent" data-section="4. Open the .pkg file" data-show="false">
<div id="s62465" class="mt-include">
<p>You&#8217;ll see a prompt notifying that macOS cannot verify the developer of the package. This is because ScreenConnect is not a Mac application, and the package file is created each time it is built.</p>
<p>To proceed, click <b>Open</b>.</p>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/34871/MacInstallerCannotVerifyDeveloper.png?revision=1" alt="MacInstallerCannotVerifyDeveloper.png" /></p>
<div id="section_6" class="mt-section">
<div class="mt-contentreuse-widget" data-page="ConnectWise_ScreenConnect_Documentation/Get_started/Remote_access_guide/Install_the_Mac_access_agent" data-section="3. Hold the Ctrl key and click the .pkg file" data-show="false">
<div id="s62465" class="mt-include">
<p><span style="font-size: 14pt;"><strong>5. On newer Macs Ctrl+Click will not work to open ScreenConnect.ClientSetup.pkg</strong></span></p>
<p><img decoding="async" src="https://calmit.org/wp-content/uploads/not-opened.png" /></p>
<p>Go to <strong>System Settings &gt; Privacy &amp; Security &gt; Security  </strong>where you will see <strong>&#8220;ScreenConnect.ClientSetup.pkg&#8221; was blocked to protect your Mac</strong></p>
<p>and click on <strong>Open Anyway</strong></p>
</div>
</div>
</div>
<div id="section_7" class="mt-section">
<p><img decoding="async" src="https://calmit.org/wp-content/uploads/open-anyway.png" /></p>
</div>
</div>
</div>
</div>
<div id="section_8" class="mt-section">
<p>&nbsp;</p>
<h3 class="editable">6. Follow the wizard to complete the installation of the ScreenConnect client</h3>
<div class="mt-contentreuse-widget" data-page="ConnectWise_ScreenConnect_Documentation/Get_started/Remote_access_guide/Install_the_Mac_access_agent" data-section="5. Complete the installation of the ScreenConnect agent" data-show="false">
<div id="s62465" class="mt-include">
<p>Follow each step of the installation wizard to install the ScreenConnect agent.</p>
<div class="alert alert-info style-wrap" title="Note">
<p><strong>Note: </strong>To complete installation, you&#8217;ll need to enter administrator credentials.</p>
</div>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/34868/MacInstallerEnterAdminPassword.png?revision=1" alt="MacInstallerEnterAdminPassword.png" /></p>
<p>And the end of the installation, you&#8217;ll also be asked to keep the .pkg file or move it to the trash. In most cases, you can move the installer to the trash.</p>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/34872/MoveToTrash.png?revision=1" alt="MoveToTrash.png" /></p>
</div>
</div>
</div>
</div>
<div id="section_9" class="mt-section">
<p>&nbsp;</p>
<h2 class="editable">First connecting to an access session</h2>
<div id="section_10" class="mt-section">
<h3 class="editable">1. Connect to the macOS machine</h3>
<p>Upon connection, you&#8217;ll see a large <strong>Review System Access </strong>window.</p>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/35127/VenturaPrompt.png?revision=2" alt="VenturaPrompt.png" /></p>
<p><span style="color: #333333; font-size: 22px;">2. Allow screen recording</span></p>
</div>
<div id="section_11" class="mt-section">
<div class="mt-contentreuse-widget" data-page="ConnectWise_ScreenConnect_Media_Repo/Snippets/macOS_agent_installation" data-section="Allow screen recording" data-show="false">
<div id="s77333" class="mt-include">
<p>In the Screen Recording section of the large prompt, click <strong>Request Access.</strong></p>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/34873/ScreenRecordingDenied.png?revision=1" alt="ScreenRecordingDenied.png" /></p>
<div class="alert alert-info style-wrap" title="Note">
<p><strong>Note:</strong> Earlier versions of macOS require you to click the dialog&#8217;s padlock icon before editing the <strong>Privacy</strong> settings.</p>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/34874/SystemPreferencesLock.png?revision=1" alt="SystemPreferencesLock.png" /></p>
</div>
<p>Next, click the toggle switch for the ScreenConnect client. The client name begins with &#8220;<b>connectwisecontrol</b>&#8220;.</p>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/39235/SecurityAndPrivacyScreenRecording.png?revision=1" alt="SecurityAndPrivacyScreenRecording.png" /></p>
<p>If required, enter a username and password to allow your changes.</p>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/39236/PrivacySecurityModifySettings.png?revision=1" alt="PrivacySecurityModifySettings.png" /></p>
<p>Next, a new message appears with the option to <b>Quit &amp; Reopen</b>. Click <strong>Quit &amp; Reopen </strong>and the client will automatically restart.</p>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/39237/SecurityAndPrivacyScreenRecordingQuitNow.png?revision=1" alt="SecurityAndPrivacyScreenRecordingQuitNow.png" /></p>
<p>Once the client reopens and the large ScreenConnect prompt returns, you should see that Screen Recording access is granted.</p>
<p><img decoding="async" class="internal glow default" src="https://docs.connectwise.com/@api/deki/files/37862/AccessGrantedMacScreenRecording.png?revision=5" alt="AccessGrantedMacScreenRecording.png" /></p>
</div>
</div>
</div>
<div id="section_12" class="mt-section">
<p>&nbsp;</p>
<h3 class="editable">3. Allow accessibility access</h3>
<div class="mt-contentreuse-widget" data-page="ConnectWise_ScreenConnect_Media_Repo/Snippets/macOS_agent_installation" data-section="Allow accessibility access" data-show="false">
<div id="s77333" class="mt-include">
<p>Return to the large <strong>Review System Access </strong>window. In the Accessibility section of the window, click <strong>Request Access.</strong></p>
<p><img decoding="async" class="internal defaul glow" src="https://docs.connectwise.com/@api/deki/files/34875/AccessibilityDenied.png?revision=1" alt="AccessibilityDenied.png" /></p>
<div class="alert alert-info style-wrap" title="Note">
<p><strong>Note:</strong> Earlier versions of macOS require you to click the dialog&#8217;s padlock icon before editing the <strong>Privacy</strong> settings.</p>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/34874/SystemPreferencesLock.png?revision=1" alt="SystemPreferencesLock.png" /></p>
</div>
<p>Next, click the &#8220;<strong><b>connectwisecontrol</b></strong>&#8221; switch.</p>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/39238/PrivacySecurityAccessibility.png?revision=1" alt="PrivacySecurityAccessibility.png" /></p>
<p>When you have finished, click the lock again to prevent further changes, and close the window.</p>
</div>
</div>
</div>
<div id="section_13" class="mt-section">
<p>&nbsp;</p>
<h3 class="editable">4. Check the Review System Access window</h3>
<div class="mt-contentreuse-widget" data-page="ConnectWise_ScreenConnect_Media_Repo/Snippets/macOS_agent_installation" data-section="Check the Review System Access window" data-show="false">
<div id="s77333" class="mt-include">
<p>You should see a green circle and a <strong>Granted</strong> status for both Screen Recording and Accessibility.</p>
<p>A technician should now have remote control over the macOS device.</p>
<p><img decoding="async" class="internal default glow" src="https://docs.connectwise.com/@api/deki/files/35128/BigSurPromptAccessGranted.png?revision=1" alt="BigSurPromptAccessGranted.png" /></p>
</div>
</div>
</div>
</div>
<h3 class="editable"><strong>5. If the Review System Access window does not appear</strong></h3>
<p>Go to <strong>System Settings &gt; General &gt; Login Items &amp; Extensions  </strong>and ensure <strong>ConnectWise, Inc </strong>is enabled</p>
<div id="section_9" class="mt-section">
<div id="section_13" class="mt-section">
<div class="mt-contentreuse-widget" data-page="ConnectWise_ScreenConnect_Media_Repo/Snippets/macOS_agent_installation" data-section="Check the Review System Access window" data-show="false">
<div id="s77333" class="mt-include">
<p><img loading="lazy" decoding="async" class="" src="https://calmit.org/wp-content/uploads/Login-items-and-extensions.png" width="614" height="348" /></p>
<p>Go to <strong>System Settings &gt; Privacy &amp; Security &gt; Accessibility  </strong>and ensure that <strong>Connecwisecontrol-d9253538a6fa5497 </strong>is enabled</p>
<p>and Go to <strong>Screen &amp; System Audio Recording</strong> and ensure that <strong>Connecwisecontrol-d9253538a6fa5497 </strong>is enabled</p>
</div>
</div>
</div>
</div>
]]></content:encoded>
					
					<wfw:commentRss>https://calmit.org/installing-screenconnect-on-a-mac/feed/</wfw:commentRss>
			<slash:comments>649</slash:comments>
		
		
			</item>
		<item>
		<title>Writing Plainly</title>
		<link>https://calmit.org/plain-language/</link>
		
		<dc:creator><![CDATA[n0t2hungry]]></dc:creator>
		<pubDate>Tue, 07 Jan 2014 17:41:52 +0000</pubDate>
				<category><![CDATA[Writing for the Web]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[How to]]></category>
		<category><![CDATA[style guide]]></category>
		<category><![CDATA[writing]]></category>
		<guid isPermaLink="false">https://zenpages.org/?page_id=2396</guid>

					<description><![CDATA[PDF version Hard writing makes easy reading. ~An old adage. Plain language writing is reader-focused writing. But what makes something plain language? The Center for Plain Language defines “plain” in terms of people’s behaviour. Can the audience for the material quickly and easily: find what they need understand what they find act appropriately on that [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><a style="line-height: 1.5em;" href="https://calmit.org/wp-content/uploads/PlainLanguage.pdf" target="_blank" rel="noopener">PDF version</a></p>
<div id="attachment_2514" style="width: 275px" class="wp-caption alignright"><img loading="lazy" decoding="async" aria-describedby="caption-attachment-2514" class="wp-image-2514 size-full" src="https://calmit.org/wp-content/uploads/pen_writing.jpg" alt="pen_writing" width="265" height="178" /><p id="caption-attachment-2514" class="wp-caption-text">Writing in plain language is key to helping readers understand and use your information.</p></div>
<p><strong><em>Hard writing makes easy reading.</em></strong></p>
<p>~An old adage.</p>
<p>Plain language writing is <strong>reader-focused</strong> writing. But what makes something plain language?</p>
<p>The Center for Plain Language defines “plain” in terms of people’s <strong><em>behaviour.</em></strong> Can the audience for the material quickly and easily:</p>
<ul>
<li>find what they need</li>
<li>understand what they find</li>
<li>act appropriately on that understanding? (<a href="#ref1">1</a>)</li>
</ul>
<p>In 1998, President Clinton made plain language a major government initiative. He wrote:</p>
<p><em>By using plain language, we send a clear message about what the government is doing, what it requires, and what services it offers…. Plain language documents have logical organization; common, everyday words, except for necessary technical terms; ‘you’ and other pronouns; the active voice; and short sentences.</em> (<a href="#ref2">2</a>)</p>
<p>Today, all of us who write can find immediate guidance on the principles of plain language at the government’s website <a href="http://www.plainlanguage.gov/" target="_blank" rel="noopener">plainlanguage.gov</a>. The info in this tip sheet comes directly from its how-to’s, tools, checklists, and examples, sometimes even verbatim.</p>
<p>Of course, we’ve only tapped the surface of what you can find with a visit to plainlanguage.gov. You’ll also find info and guidance on writing in plain language for the sake of your readers by visiting the <a href="#resources">resources</a> we’ve listed at the end of this page. Enjoy!</p>
<p><a href="#top">Back to top</a></p>
<h4>10 Tips for Writing in Plain Language</h4>
<p><strong>#1 | Write for the average reader.</strong></p>
<p>Know the expertise and interest of your average reader, and write to that person. Don’t write to the experts, the lawyers, or doctoral candidates, unless they’re your intended audience. (<a href="#ref3">3</a>)</p>
<p>To communicate with the average reader, we need to write at the 6th to the 8th grade reading level. (<a href="#ref4">4</a>)</p>
<p><strong>#2 | Organize to serve the reader’s needs.</strong></p>
<p>The two most useful principles:</p>
<ul>
<li>Put the most important material first and the exceptions last</li>
<li>Organize material chronologically</li>
</ul>
<p><strong>#3 | Use helpful headings.</strong></p>
<p>Headings help the reader find their way. Use more headings on the web, with less info under each. People skim and scan.<br />
(Read more about <a href="/webwriting/headings">crafting your headings and subheadings</a>.)</p>
<p><a href="#top">Back to top</a></p>
<p><strong>#4 | Use “you” to speak to your reader.</strong></p>
<p>Using pronouns pulls the reader in. Use “you” for the reader, “we” for your agency.</p>
<p><strong>#5 | Use active voice.</strong></p>
<p>Active voice makes it clear <em>who</em> is doing <em>what</em>. It is shorter and clearer.</p>
<p><em><strong>Examples</strong></em><br />
<em>Passive:</em> The tray of food was dropped by the waiter.<br />
<em>Active:</em> The waiter dropped the tray of food.</p>
<p><em>Passive:</em> Your request for funding has been denied by the review committee.<br />
<em>Active:</em> The review committee denied your request for funding. (<a href="#ref5">5</a>)</p>
<p><em>Occasions to use passive voice:</em></p>
<ul>
<li>when you don’t know the actor (“John was murdered.”)</li>
<li>when the actor is unimportant (“The senator was re-elected.”)</li>
<li>when the emphasis is on the acted-upon (“The little girl was rescued.”) (<a href="#ref6">6</a>)</li>
</ul>
<p><a href="#top">Back to top</a></p>
<p><strong>#6 | Use short sentences and short sections.</strong></p>
<p>Short sentences, paragraphs, and sections help readers get through material. Chunking adds white space.</p>
<p><em>Example</em><br />
<strong>Before:</strong> Long, dense paragraph…<br />
<strong>After:</strong> Do at least 30 minutes of exercise, like brisk walking, most days of the week.</p>
<p><a href="#top">Back to top</a></p>
<p><strong>#7 | Use concrete, familiar words.</strong></p>
<p>Avoid jargon, foreign terms, legal terms. Replace complex words with simple ones.</p>
<p><em>Examples</em><br />
Instead of: <em>a and/or b</em> → <strong>a or b or both</strong><br />
Instead of: <em>accomplish</em> → <strong>do</strong><br />
Instead of: <em>accorded</em> → <strong>given</strong></p>
<p><strong><em>Want the full list?</em></strong><br />
<a href="https://www.plainlanguage.gov/resources/checklists/" target="_blank" rel="noopener">plainlanguage.gov</a></p>
<p><a href="#top">Back to top</a></p>
<p><strong>#8 | Omit excess words.</strong></p>
<p>Challenge every word. Remove unnecessary modifiers.</p>
<p><em>Examples</em><br />
Instead of: <em>as a means of</em> → <strong>to</strong><br />
Instead of: <em>at the present time</em> → <strong>now</strong></p>
<p><strong>Before:</strong> Long bureaucratic sentence…<br />
<strong>After:</strong> If you make a hole while freeing a stuck vehicle, you must fill it before you drive away.</p>
<p><a href="#top">Back to top</a></p>
<p><strong>#9 | Place words carefully.</strong></p>
<p>Keep subject, verb, and object close. Put exceptions at the end. Place modifiers correctly.</p>
<p><strong>#10 | Use no more than 2 or 3 subordinate levels.</strong></p>
<p>More than 3 levels confuses readers. Subdivide instead.</p>
<p><span id="resources"></span><br />
<a href="#top">Back to top</a></p>
<h4>Resources of More Information</h4>
<p>plainlanguage.gov is not the only source. Here are others:</p>
<p>NIH Plain Language Online Training<br />
<a href="http://plainlanguage.nih.gov/CBTs/PlainLanguage/login.asp" target="_blank" rel="noopener">plainlanguage.nih.gov</a></p>
<p>Plain Language Wizardry<br />
<a href="http://plainlanguage.com/" target="_blank" rel="noopener">plainlanguage.com</a></p>
<p>Plain English Campaign<br />
<a href="http://www.plainenglishtraining.com/" target="_blank" rel="noopener">plainenglishtraining.com</a></p>
<p>Plain Language Association International<br />
<a href="http://www.plainlanguagenetwork.org/" target="_blank" rel="noopener">plainlanguagenetwork.org</a></p>
<p>Center for Plain Language<br />
<a href="http://www.centerforplainlanguage.org/" target="_blank" rel="noopener">centerforplainlanguage.org</a></p>
<p>Readability Formulas<br />
<a href="http://www.readabilityformulas.com/" target="_blank" rel="noopener">readabilityformulas.com</a></p>
<p>Style Writer’s Readability Calculations<br />
<a href="http://www.stylewriter-usa.com/readabilitycalc.html" target="_blank" rel="noopener">stylewriter-usa.com</a></p>
<p><a href="#top">Back to top</a></p>
<p><strong>Want to read another section of Writing for the Web?</strong></p>
<ul>
<li><a href="/webwriting/reading">How people read on the web</a></li>
<li><a href="/webwriting/scanning">Helping readers skim and scan</a></li>
<li><a href="https://zenpages.org/essential-message-first/">Putting your essential message first</a></li>
<li><a href="/webwriting/chunking">Chunking your information</a></li>
<li><a href="/webwriting/headings">Using headings and subheadings</a></li>
<li>Writing in plain language (you’re here)</li>
</ul>
<p><span id="ref1"></span><a href="#top">Back to top</a></p>
<h4>References</h4>
<p><em>The National Dissemination Center thanks <a href="http://www.plainlanguage.gov/" target="_blank" rel="noopener">plainlanguage.gov</a> for its excellent materials, freely used here unless noted below.</em></p>
<p>1 | Center for Plain Language. (n.d.). <em>About plain language</em>. <a href="http://centerforplainlanguage.org/about-plain-language/" target="_blank" rel="noopener">centerforplainlanguage.org</a></p>
<p><span id="ref2"></span><br />
2 | Locke, J. (2004). <em>A history of plain language in the United States government</em>. <a href="http://www.plainlanguage.gov/whatisPL/history/locke.cfm" target="_blank" rel="noopener">plainlanguage.gov</a></p>
<p><span id="ref3"></span><br />
3 | plainlanguage.gov. (n.d.). <em>Document checklist for plain language</em>. <a href="http://www.plainlanguage.gov/howto/quickreference/checklist.cfm" target="_blank" rel="noopener">plainlanguage.gov</a></p>
<p><span id="ref4"></span><br />
4 | The Informatics Review. (n.d.). <em>Comprehension and reading level</em>. <a href="http://web.archive.org/web/20111018045029/http://www.informatics-review.com/FAQ/reading.html" target="_blank" rel="noopener">informatics-review.com</a></p>
<p>As an alternative: DuBay, W.H. (2004). <em>The principles of readability</em>. <a href="http://www.impact-information.com/impactinfo/readability02.pdf" target="_blank" rel="noopener">impact-information.com</a></p>
<p><span id="ref5"></span><br />
5 | The Quality Writing Center. (n.d.). <em>Choosing between active and passive voice</em>. <a href="http://www.uark.edu/campus-resources/qwrtcntr/resources/handouts/activepassive.htm" target="_blank" rel="noopener">uark.edu</a></p>
<p><span id="ref6"></span><br />
6 | Bailey, E.P. (1996). <em>Plain English at work</em>. Oxford.</p>
<p><a href="#top">Back to top</a></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Crafting Headings and Subheadings</title>
		<link>https://calmit.org/headings/</link>
					<comments>https://calmit.org/headings/#comments</comments>
		
		<dc:creator><![CDATA[n0t2hungry]]></dc:creator>
		<pubDate>Mon, 06 Jan 2014 17:42:12 +0000</pubDate>
				<category><![CDATA[Writing for the Web]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[headings]]></category>
		<category><![CDATA[titles]]></category>
		<category><![CDATA[writing]]></category>
		<guid isPermaLink="false">https://zenpages.org/?page_id=2395</guid>

					<description><![CDATA[According to the Web Style Content Guide (1), “On the Web, you live or die by your headings… A good one makes it easier for readers to find your article, and much more likely that they will read what you have written. A bad heading ensures that few, if any, readers will find your text [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>According to the <em>Web Style Content Guide</em> (<a href="#refs">1</a>), “On the Web, <strong>you live or die by your headings</strong>… A good one makes it easier for readers to find your article, and much more likely that they will read what you have written. A bad heading ensures that few, if any, readers will find your text at all, and that those who do will be unlikely to read further.” (<a href="#refs">2</a>)</p>
<p>O–kay. Sounds important, even critical. Let’s get down to it, then:</p>
<ul>
<li><a href="#elements">Elements of a good heading</a></li>
<li><a href="#tips">Tips and examples</a></li>
</ul>
<p><span id="elements"></span><a href="#top">Back to top</a></p>
<h2>Elements of a Good Heading</h2>
<p>Good headings help search engines find your webpages, <em>and</em> they help readers scan webpages efficiently for content of interest. Among other things, good headings (and subheadings):</p>
<ul>
<li>divide your content into different <strong>sections</strong></li>
<li>include <strong>keywords</strong> that your visitors use</li>
<li><strong><em>start</em></strong> with the keywords of visitors</li>
<li>are <strong>concise,</strong> yet give a clear <strong>preview</strong> of the content to follow</li>
<li>may be written as <strong>questions</strong> that your visitors typically ask</li>
<li>are <strong>distinct</strong> from the other text on the page (either by color or by size)</li>
<li>are formatted using <strong>HTML heading tags</strong> (&lt;H1&gt;, &lt;H2&gt;, etc.)</li>
</ul>
<p><span id="tips"></span><a href="#top">Back to top</a></p>
<h2>Tips for Writing Good Headings, with Examples</h2>
<p>Let’s take a closer look at each of the bullets in the list above.</p>
<p><strong>Divide your content with headings</strong><br />
Headings (and subheadings) are a great way to divide up your content and make it easy to scan at a glance. Headings also signal to readers how information on the page is organized—what’s subordinate to what. So be consistent with the color and size of headings at different levels of importance. (<a href="#refs">3</a>)</p>
<p><em>How</em> you divide up the actual content is discussed in the separate webpage <a href="/webwriting/chunking">Chunking Your Content</a>.</p>
<p><a href="#top">Back to top</a></p>
<p><strong>Include keywords in your headings</strong><br />
Keywords are an important part of how readers scan webpages for info of interest to them. (<a href="#refs">4</a>) They’re looking for a word or phrase that tips them off that the page holds content that’s relevant <strong><em>to them</em></strong>. If they see a keyword in a heading or subheading, they know just where to go on the page and start reading in earnest.</p>
<p><em>Use the keywords that your readers use</em> rather than generic headings such as “Introduction” or “Overview.” For example, NICHCY uses the heading “Is There Help Available?” in many of our disability fact sheets, because “help” is what so many of our visitors are looking for.</p>
<p><em>Example</em><br />
From <a href="http://www.directionservice.org/cadre" target="_blank">CADRE</a>, the Center for Appropriate Dispute Resolution in Special Education</p>
<p><em><a href="http://www.directionservice.org/cadre/pdf/ResolutionMeetingParentGuideJAN14.pdf" target="_blank">CADRE’s Resolution Meetings: A Guide for Parents</a></em><br />
Rather than use headings such as “Benefits”, “Concerns”, and “Frequently Asked Questions”, CADRE uses:</p>
<p>• Benefits of Participating in a Resolution Meeting<br />
• Concerns about the Resolution Meeting<br />
• Frequently Asked Questions about Resolution Meetings  </p>
<p>The inclusion of “resolution meeting” in each heading makes it very easy for search engines to find and share the brochure.</p>
<p><a href="#top">Back to top</a></p>
<p><strong><em>Start</em> headings with keywords</strong><br />
Even better than including keywords is <em>starting</em> the heading with them. Web readers skim the <strong>first two words</strong> of headings, sentences, and paragraphs. (<a href="#refs">5</a>)</p>
<p><em>Example</em><br />
From NICHCY’s <a href="http://nichcy.org/babies/effectivepractices">Effective Practices in Early Intervention</a> page:</p>
<p>• Organizations with Serious Expertise<br />
• Addressing Behavior Challenges in Young Children<br />
• Assistive Technology for the Little Ones  </p>
<p>A heading to rewrite: “Let the Child Play (to Learn)!” — too vague, not front‑loaded with meaningful words.</p>
<p><a href="#top">Back to top</a></p>
<p><strong>Be concise but give a clear preview of the content to follow</strong><br />
Headings should be short and descriptive—4 to 8 words. (<a href="#refs">6</a>) They help readers decide instantly whether the section is relevant.</p>
<p>Jakob Nielsen praises BBC News headlines for packing meaning into very few words. (<a href="#refs">7</a>)</p>
<p><em>Examples</em><br />
Iran accuses journalist of spying | Villagers hurt in West Bank clash</p>
<p><em>Examples</em><br />
From Reading Rockets’s <a href="http://www.readingrockets.org/article/42934/" target="_blank">Top 10 Things You Should Know About Reading</a>:</p>
<p>• Too many American children don’t read well<br />
• Learning to read is complex<br />
• Kids who struggle usually have problems sounding out words  </p>
<p><a href="#top">Back to top</a></p>
<p><strong>Pose questions</strong><br />
Questions make excellent headings, especially when they mirror user questions.</p>
<p><em>Example</em><br />
From NICHCY’s <a href="http://nichcy.org/schoolage/placement/overview">Placement, Short-and-Sweet</a>:</p>
<p>• What does IDEA require?<br />
• Who makes the placement decision?<br />
• On what is the decision based?  </p>
<p>You can also pose questions in the user’s voice and answer in yours, creating a conversational structure. (<a href="#refs">8</a>)</p>
<p><em>Example</em><br />
<strong>Who decides if my child is eligible for special education?</strong><br />
Your child’s eligibility is decided by a team that includes you…</p>
<p><a href="#top">Back to top</a></p>
<p><strong>Make headings look different from the other text</strong><br />
This seems obvious, but it matters. Headings must visually stand out.</p>
<p><a href="#top">Back to top</a></p>
<p><strong>Format headings with HTML heading tags</strong><br />
HTML heading tags (&lt;H1&gt;–&lt;H6&gt;) communicate hierarchy to:</p>
<p>• search engines<br />
• screen readers<br />
• human readers  </p>
<p>(<a href="#refs">9</a>)</p>
<p>Using proper heading tags is different from simply bolding text.</p>
<p><a href="#top">Back to top</a></p>
<p><strong>Want to read another section of Writing for the Web?</strong></p>
<ul>
<li><a href="/webwriting/reading">How people read on the web</a></li>
<li><a href="/webwriting/scanning">Helping readers skim and scan</a></li>
<li><a href="https://zenpages.org/essential-message-first/">Putting your essential message first</a></li>
<li><a href="/webwriting/chunking">Chunking your information</a></li>
<li>Using headings and subheadings (you’re here)</li>
<li><a href="/webwriting/plain">Writing in plain language</a></li>
</ul>
<p><a href="#top">Back to top</a></p>
<h4><span id="refs"></span>References</h4>
<p>1 | McGovern, G., Norton, R., &amp; O’Dowd, C. (2001). <em>Web style content guide</em>. Online at: <a href="http://www.gerrymcgovern.com/books/web-content-style-guide" target="_blank">http://www.gerrymcgovern.com/web_content_style_guide.htm</a></p>
<p>2 | McGovern, G., Norton, R., &amp; O’Dowd, C. (2001). Web headings that work. <em>Web Style Content Guide</em> (Part 4). Available at: <a href="http://www.gerrymcgovern.com/books/web-content-style-guide" target="_blank">http://www.gerrymcgovern.com/books/web-content-style-guide</a></p>
<p>3 | Krug, S. (2006). <em>Don’t make me think</em>. Berkeley,</p>
]]></content:encoded>
					
					<wfw:commentRss>https://calmit.org/headings/feed/</wfw:commentRss>
			<slash:comments>24</slash:comments>
		
		
			</item>
		<item>
		<title>Chunking Your Content</title>
		<link>https://calmit.org/chunking/</link>
		
		<dc:creator><![CDATA[n0t2hungry]]></dc:creator>
		<pubDate>Sun, 05 Jan 2014 17:42:17 +0000</pubDate>
				<category><![CDATA[Writing for the Web]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[writing]]></category>
		<guid isPermaLink="false">https://zenpages.org/?page_id=2394</guid>

					<description><![CDATA[Chunking your web content into small paragraphs helps your web visitors scan for the information they’re looking for. Well-written paragraphs on the web: have only 1 main point start with that main point are less than 100 words long Why Small Chunks of Info Suit Web Readers Web visitors don’t really read much of what’s [&#8230;]]]></description>
										<content:encoded><![CDATA[<div id="attachment_2511" style="width: 203px" class="wp-caption alignright"><img loading="lazy" decoding="async" aria-describedby="caption-attachment-2511" class="wp-image-2511 size-full" src="https://calmit.org/wp-content/uploads/rsz_chunk2-193x300.jpg" alt="rsz_chunk2-193x300" width="193" height="300" /><p id="caption-attachment-2511" class="wp-caption-text">Breaking your info into chunks helps readers scan the page for content of interest.</p></div>
<p><span style="line-height: 1.5em;">Chunking your web content into small paragraphs helps your web visitors scan for the information they’re looking for. Well-written paragraphs on the web:</span></p>
<ul>
<li>have only 1 main point</li>
<li><em>start</em> with that main point</li>
<li>are less than 100 words long</li>
</ul>
<h4>Why Small Chunks of Info Suit Web Readers</h4>
<p>Web visitors don’t really read much of what’s on a webpage—not much more than 20% on average (<a href="#ref1">1</a>). They also skip straight over large blocks of text unless the first two words grab their attention. (<a href="#ref2">2</a>) They <em>do</em> read:</p>
<div>
<ul>
<li>the first sentence or two on the page,</li>
<li>headings and subheadings marked in bolded or differently colored text,</li>
<li>captions on images, and</li>
<li>the first and second words in a short paragraph.</li>
</ul>
<p>That’s daunting news, isn’t it? In the TA&amp;D network, we <em>want</em> our content to be read, understood, and put to use in the field. So we have every reason to present our content in ways that increase their chances of being read!
</div>
<p><a href="#top">Back to top</a></p>
<h4>10 Suggestions for Chunking Your Content</h4>
<p>Breaking up content into readable, scannable pieces is actually a fairly straightforward task. Start with these 10 strategies.</p>
<p><strong>1 | Create Sections Topped by Headings</strong><br />
Break your content out into sections that address one or two main points each. Mark each section with a bolded heading that puts keywords first and succinctly describes the message or content of the section.</p>
<p><strong>2 | Put One Main Idea Per Paragraph</strong><br />
Limit each paragraph to 1 main point. The lead sentence in the paragraph should state that point. This helps make your message clear, helps readers scan for info, and keeps the paragraph short. If you start wandering into a different point, start a new paragraph.</p>
<p><strong>3 | Short Paragraphs Rule!</strong><br />
Limit your paragraphs to no more than 3 or 4 short sentences. Readers pay the most attention to the first and last sentences in a paragraph. What’s in between is likely to be skipped. (<a href="#ref3">3</a>)</p>
<p><strong>4 | Short Sentences Rule, Too!</strong><br />
Shorter sentences are easier to read and understand. If your sentences are averaging 15 or more words, try to break them into two simpler sentences. (<a href="#ref4">4</a>)</p>
<p><strong>5 | Try the One-Sentence Paragraph</strong><br />
It’s okay to have only 1 sentence in a paragraph.</p>
<p><strong>6 | Read the Content Aloud</strong><br />
Let the nature of your content suggest how it might best be subdivided and organized. (<a href="#ref5">5</a>) Sometimes it helps to read the content aloud, to hear how the ideas flow and where natural breaking points occur or the topic shifts, suggesting it’s time for a new paragraph or section.</p>
<p><strong>7 | Present Content as Bullet Points</strong><br />
Bullets are very easy to scan. When you can break up a wall of text into bullet points, readers can skim quickly and still get the point. That’s even easier if each bullet contains just a few words. Webwriters and researchers advise: No more than 7 bullet points in a list. Any more and readers may lose the connection between the items. (<a href="#ref6">6</a>)</p>
<p><strong>8 | Use Numbered Lists, Too</strong><br />
When giving instructions, numbered lists are the way to go, walking the reader through the steps to be followed in order. Numbered lists also work for content that you’d like visitors to read in a certain order. (<a href="#ref7">7</a>)</p>
<p><strong>9 | Add Links to Content Chunks</strong><br />
When your webpage is suddenly getting longer than expected, include <strong>“Back to top”</strong> links between chunks of content. This works especially well if you’ve included a table of contents at the top, which lets readers jump to content of interest.</p>
<p>Another type of link you can add at the end of content chunks is <strong>“Read more.”</strong> If users want to learn more about the topic, they can—on a separate page where you can elaborate in greater depth and detail. These webpages on <em>Writing for the Web</em> are designed in this way. (<a href="#ref8">8</a>)</p>
<p><strong>10 | Break Longer Documents into Separate Pages</strong><br />
Longer documents may need to be broken into several interlinked pages, each with its own purpose or message. Taken together, the webpages tell the full story, but readers can pick and choose which pages are relevant to their needs or concerns. Offer the complete document as a PDF file for download and printing.</p>
<p><a href="#top">Back to top</a></p>
<p><strong>Want to read another section of Writing for the Web? </strong><br />
Want to read another of the “chunks” in our <a href="http://nichcy.org/dissemination/tools/webwriting">Writing for the Web</a> discussion? Use the links below to jump there quickly.</p>
<ul>
<li><a href="/webwriting/reading">How people read on the web</a></li>
<li><a href="/webwriting/scanning">Helping readers skim and scan</a></li>
<li><a href="https://zenpages.org/essential-message-first/">Putting your essential message first</a></li>
<li>Chunking your information (you’re here)</li>
<li><a href="/webwriting/headings">Using headings and subheadings</a></li>
<li><a href="/webwriting/plain">Writing in plain language</a></li>
</ul>
<p><span id="ref1"></span><br />
<a href="#top">Back to top</a></p>
<h4>References</h4>
<p>1 | Nielsen, J. (2008, May 6). <em>How little do users read?</em> Online at: <a href="http://www.useit.com/alertbox/percent-text-read.html" target="_blank">http://www.useit.com/alertbox/percent-text-read.html</a></p>
<p><span id="ref2"></span><br />
2 | Nielsen, J. (2009, April 6). <em>First 2 words: A signal for the scanning eye</em>. Online at: <a href="http://www.useit.com/alertbox/nanocontent.html" target="_blank">http://www.useit.com/alertbox/nanocontent.html</a></p>
<p><span id="ref3"></span><br />
3 | Kilian, C. (2007). <em>Writing for the web 3.0</em>. Bellingham, WA: Self-Counsel Press.</p>
<p><span id="ref4"></span><br />
4 | Mayor’s Office of Adult Education. (). <em>Easy-to-read NYC: Guidelines for clear and effective communication.</em> Online at: <a href="http://home2.nyc.gov/html/oath/pdf/Easy-to-Read%20NYC.pdf" target="_blank">http://home2.nyc.gov/html/oath/pdf/Easy-to-Read%20NYC.pdf</a></p>
<p><span id="ref5"></span><br />
5 | Lynch, P.J., &#038; Horton, S. (2008). <em>Organizing your information</em> (Chapter 3). <em>Web style guide</em> (3rd ed.). Online at: <a href="http://webstyleguide.com/wsg3/3-information-architecture/2-organizing-information.html" target="_blank">http://webstyleguide.com/wsg3/3-information-architecture/2-organizing-information.html</a></p>
<p><span id="ref6"></span><br />
6 | French, L. (n.d.). <em>How to write for the web</em>. Online at: <a href="http://www.lancefrench.com/Web_Design/file/write-for-the-web.php" target="_blank">http://www.lancefrench.com/Web_Design/file/write-for-the-web.php</a></p>
<p><span id="ref7"></span><br />
7 | Price, J., and Price, L. (). <em>2d. Turn any list into a bulleted or numbered list</em>. Online at: <a href="http://www.webwritingthatworks.com/DGuideScan2d.htm" target="_blank">http://www.webwritingthatworks.com/DGuideScan2d.htm</a></p>
<p><span id="ref8"></span><br />
8 | Anthony. (2011, June 12). <em>Content chunking: Designing clear, memorable web pages.</em> Online at: <a href="http://uxmovement.com/content/content-chunking-designing-clear-memorable-web-pages/" target="_blank">http://uxmovement.com/content/content-chunking-designing-clear-memorable-web-pages/</a></p>
<p><a href="#top">Back to top</a></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Putting Your Essential Message First</title>
		<link>https://calmit.org/essential-message-first/</link>
		
		<dc:creator><![CDATA[n0t2hungry]]></dc:creator>
		<pubDate>Sat, 04 Jan 2014 17:36:16 +0000</pubDate>
				<category><![CDATA[Writing for the Web]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[headings]]></category>
		<category><![CDATA[titles]]></category>
		<category><![CDATA[writing]]></category>
		<guid isPermaLink="false">https://zenpages.org/?page_id=2392</guid>

					<description><![CDATA[Help web visitors get the point of each of your webpages fast: Load the opening paragraph with the essential message of the page. The web is action-packed, and people are in a hurry. Eye-tracking studies have shown that users pay the most attention to the content they see first—which would be our opening paragraphs. Use [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><span style="font-size: 14px; line-height: 1.5em;">Help web visitors get the point of each of your webpages fast: </span><strong style="font-size: 14px; line-height: 1.5em;">Load the opening paragraph with the essential message of the page</strong><span style="font-size: 14px; line-height: 1.5em;">.</span></p>
<p>The web is action-packed, and people are in a hurry. <a href="/webwriting/reading">Eye-tracking studies</a> have shown that users pay the most attention to the content they see first—which would be our opening paragraphs.</p>
<ul>
<li><a href="#use">Use the inverted pyramid approach</a></li>
<li><a href="#long">Suggestions for long pages</a></li>
</ul>
<p><span id="use"></span></p>
<h4>Use the Inverted Pyramid Approach</h4>
<p>This style of “essential message first” is called the <strong><a href="http://en.wikipedia.org/wiki/Inverted_pyramid" target="_blank">inverted pyramid</a></strong>. The approach comes from journalism, where you lead strong with the five Ws in the first paragraph (who? what? when? where? why?). (<a href="#ref1">1</a>) This flips the content upside down from an academic writing style. Remember all those writing lessons from grammar school to college? Forget them when you’re writing for the web!</p>
<p>Here’s a graphic depiction of the inverted pyramid that shows what content goes into each section. (<a href="#ref2">2</a>)</p>
<div id="attachment_2509" style="width: 310px" class="wp-caption alignnone"><img loading="lazy" decoding="async" aria-describedby="caption-attachment-2509" class="size-full wp-image-2509" src="https://zenpages.org/wp-content/uploads/Inverted-pryamid2-300x242.jpg" alt="The inverted pyramid approach to writing fits the way people read on the web." width="300" height="242" /><p id="caption-attachment-2509" class="wp-caption-text"><br />The inverted pyramid approach to writing fits the way people read on the web.</p></div>
<p><strong style="line-height: 1.5em;">The Lead</strong><span style="line-height: 1.5em;"> | The top part of the pyramid is called the </span><em style="line-height: 1.5em;"><strong>lead </strong></em><span style="line-height: 1.5em;">(another newsroom term). It’s the most important point of your webpage. If visitors take away only 1 point from your page, what point do you want that to be? That’s your lead.</span></p>
<p>Good leads:</p>
<ul>
<li>are 1-2 sentences long</li>
<li>use short sentences (30-35 words max)</li>
<li>include information-carrying keywords</li>
<li>help readers see whether the webpage has info relevant to their need or concern (<a href="#ref3">3</a>)</li>
</ul>
<p><strong>The Body</strong> | The center slice of the pyramid is the <em><strong>body</strong></em>. What you say here supports your lead and presents information in <em>descending order of importance</em>. (<a href="#ref4">4</a>)</p>
<p>Write the body of your webpage using the principles discussed in this series of articles on <a href="https://zenpages.org/webwriting">Writing for the Web</a>. Specifically:</p>
<ul>
<li>Divide the content into distinct sections (especially if there’s a lot of info to communicate)</li>
<li>Use headings (in bold) to mark the sections</li>
<li>Use headings rich with content words</li>
<li>Keep individual paragraphs short</li>
<li>Front-load important information at the start of sentences and paragraphs</li>
<li>Make it easy for visitors to scan the content</li>
<li>Give bulleted lists</li>
<li>Include a table of contents, so visitors can jump to content of interest</li>
<li>Delete words and sentences that aren’t necessary to making your point</li>
</ul>
<div><strong>The Ending</strong> | The end of your webpage is where background information, history, and the least important information goes, what would be “nice” for readers to know. We can count ourselves lucky if web visitors read that far. But many will, as Jakob Nielsen notes:</div>
<p>People will look very far down a page if (a) the <strong>layout encourages scanning</strong>, and (b) the initially viewable information makes them <strong>believe that it will be worth their time</strong> to scroll. (<a href="#ref5">5</a>)</p>
<div>
Nielsen also suggests:</p>
<p>Finally, while placing the most important stuff on top, don’t forget to put a <strong>nice morsel at the very bottom</strong>. (<a href="#ref6">6</a>)
</div>
<p><span id="long"></span><a href="#top">Back to top</a></p>
<h4>Suggestions for Long Pages</h4>
<p>Sometimes it’s not possible—or desirable—to be brief. In the TA&amp;D network, we have important information to share. Many people need the details of our content, including clear explanations of processes, legal requirements, and next steps. And, as Nielsen observes, when people really <strong>need a solution</strong> to a problem or concern, they <em>will</em> read <strong>comprehensive coverage</strong> of the topic. (<a href="#ref7">7</a>) For many of our visitors, then, long pages make sense.</p>
<p>Nielsen suggests a solution that works well for both types of web users:</p>
<ul>
<li>Start with overviews and short pages, and then</li>
<li>Link to long pages or white papers with indepth coverage. (<a href="#ref8">8</a>)</li>
</ul>
<p>It’s still important to make long pages as scannable as possible:</p>
<ul>
<li>Use headings to divide the content up into short, easy-to-read paragraphs or sections</li>
<li>Allow white space on the page</li>
<li>Narrow the focus of the content or split the content into stand-alone pages</li>
<li>Cut text every way you can</li>
</ul>
<p>Shoot for <strong>half the word count</strong> you’d use for a document in print.</p>
<p><a href="#top">Back to top</a></p>
<p><strong>Want to read another section of Writing for the Web? </strong><br />
Want to read another of the “chunks” in our <a href="/webwriting">Writing for the Web</a> discussion? Use the links below to jump there quickly.</p>
<ul>
<li><a href="/webwriting/reading">How people read on the web</a></li>
<li><a href="/webwriting/scanning">Helping readers skim and scan</a></li>
<li>Putting your essential message first (you’re here)</li>
<li><a href="/webwriting/chunking">Chunking your information</a></li>
<li><a href="/webwriting/headings">Using headings and subheadings</a></li>
<li><a href="/webwriting/plain">Writing in plain language</a></li>
</ul>
<p><span id="ref1"></span><br />
<a href="#top">Back to top</a></p>
<h4>References</h4>
<p>1 | Michael. (2007). <em>The inverted pyramid</em>. Online at: <a href="http://www.dailywritingtips.com/the-inverted-pyramid/" target="_blank">http://www.dailywritingtips.com/the-inverted-pyramid/</a></p>
<p><span id="ref2"></span><br />
2 | Howard, M. (2009, July 20). <em>Inverted pyramid: Writing detail pages/information pages</em>. Online at: <a href="http://www.s8080blog.com/tag/inverted-pyramid/" target="_blank">http://www.s8080blog.com/tag/inverted-pyramid/</a></p>
<p><span id="ref3"></span><br />
3 | Stovall, J.G. (n.d.). <em>Inverted pyramid checklist</em>. Online at: <a href="http://www.jprof.com/2013/10/08/inverted-pyramid-checklist/" target="_blank">http://www.jprof.com/writing/invertedpyramidchecklist.html</a></p>
<p><span id="ref4"></span><br />
4 | SNN Newsroom. (). <em>The inverted pyramid</em>. Online at: <a href="http://www.snn-rdr.ca/snn/nr_reporterstoolbox/invertedpyramid.html" target="_blank">http://www.snn-rdr.ca/snn/nr_reporterstoolbox/invertedpyramid.html</a></p>
<p><span id="ref5"></span><br />
5 | Nielsen, J. (2010, March 22). <em>Scrolling and attention</em>. Online at: <a href="http://www.useit.com/alertbox/scrolling-attention.html" target="_blank">http://www.useit.com/alertbox/scrolling-attention.html</a></p>
<p><span id="ref6"></span><br />
6 | Ibid.</p>
<p><span id="ref7"></span><br />
7 | Nielsen, J. (2007, November 12). <em>Long vs. short articles as content strategy</em>. Online at: <a href="http://www.useit.com/alertbox/content-strategy.html" target="_blank">http://www.useit.com/alertbox/content-strategy.html</a></p>
<p><span id="ref8"></span><br />
8 | Nielsen, J. (1997, October 1). <em>How users read on the web</em>. Online at: <a href="http://www.useit.com/alertbox/9710a.html" target="_blank">http://www.useit.com/alertbox/9710a.html</a></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Helping Readers Skim and Scan</title>
		<link>https://calmit.org/scanning/</link>
					<comments>https://calmit.org/scanning/#comments</comments>
		
		<dc:creator><![CDATA[n0t2hungry]]></dc:creator>
		<pubDate>Fri, 03 Jan 2014 17:28:50 +0000</pubDate>
				<category><![CDATA[Writing for the Web]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[headings]]></category>
		<category><![CDATA[links]]></category>
		<category><![CDATA[titles]]></category>
		<category><![CDATA[writing]]></category>
		<guid isPermaLink="false">https://zenpages.org/?page_id=2390</guid>

					<description><![CDATA[Most people don’t read through the content we put on our websites. They skim and scan the pages, “taking in headings, the beginnings of paragraphs, and first words of sentences.” (1) They’re looking for something that strikes their attention or matches the question or need they have. If they find it, they dig in and [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Most people don’t read through the content we put on our websites. They skim and scan the pages, “taking in headings, the beginnings of paragraphs, and first words of sentences.” (<a href="#refs">1</a>) They’re looking for something that strikes their attention or matches the question or need they have. If they find it, they dig in and read more carefully.</p>
<p><strong>To help our web visitors find what they’re looking for, we can create webpages that are easy to scan</strong>.<br />
Here are 10 “how-to” tips.</p>
<ol>
<li><a href="#toc">Include a table of contents</a></li>
<li><a href="#start">State the most important information in the first two paragraphs</a></li>
<li><a href="#short">Chunk content in short paragraphs</a></li>
<li><a href="#mainidea">Put only one main idea in a paragraph</a></li>
<li><a href="#headings">Bold headings and subheadings</a></li>
<li><a href="#frontload">Front load headings with significant words</a></li>
<li><a href="#bullets">Use bullets, numbered lists, and numerals</a></li>
<li><a href="#center">Don’t center text on the page</a></li>
<li><a href="#links">Make your links meaningful</a></li>
<li><a href="#testing">Test your site with a few users</a></li>
</ol>
<p><a href="#top">Back to top</a></p>
<h3>1 | <span id="toc"></span>Include a Table of Contents</h3>
<p>You can start webpages (especially longer ones) with a table of contents. This gives readers a quick <strong>snapshot of the content</strong> they’re going to find on that page. The items in the table of contents should match the major headings or sections of the page and be linked to those sections, so that users can “rappel like rock climbers down the text.” (<a href="#refs">2</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>2 | <span id="start"></span>State the Most Important Information in the First Two Paragraphs</h3>
<p>We have to <strong>state the essential message of the page first,</strong> right off the bat. Immediately. In the first two paragraphs. Why? Because web visitors give 80% of their attention to what’s “above the fold” on the webpage. (<a href="#refs">3</a>)</p>
<p>Putting the most important information first means that web users will actually see it. Of course, doing so violates the rules of writing we learned in high school.</p>
<p>But writing for the web is very different from writing for print. Giving a quick overview in the first two paragraphs “helps the reader get the point and purpose of a page instantly.” (<a href="#refs">4</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>3 | <span id="short"></span>Chunk Content in Short Paragraphs</h3>
<p><strong>Short and concise paragraphs are easier to scan</strong>—and they get twice as many eye fixations as long paragraphs. (<a href="#refs">5</a>)</p>
<p><strong>How short is short?</strong> Less than 100 words. Cut what’s unnecessary. Start a new paragraph when you drift from the main idea. (<a href="#refs">6</a>)</p>
<p>Want more info? See <a href="https://zenpages.org/webwriting/chunking/"><em>Chunking Your Content</em></a>.</p>
<p><a href="#top">Back to top</a></p>
<h3>4 | <span id="mainidea"></span>Put Only One Main Idea in a Paragraph</h3>
<p>Limit each paragraph to one idea. <strong>Front load your message</strong> at the beginning. “A meandering introductory clause may seem like a good idea…but the reader might stop reading.” (<a href="#refs">7</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>5 | <span id="headings"></span>Bold Headings and Subheadings</h3>
<p>Headings act as “landmarks.” (<a href="#refs">8</a>)</p>
<p>To write strong headings:</p>
<ul>
<li><strong>Make them questions</strong> users ask.</li>
<li><strong>Use action statements</strong>.</li>
<li><strong>Make them stand out</strong> visually.</li>
<li><strong>Keep them short</strong>. Readers see the first two words most clearly. (<a href="#refs">9</a>)</li>
</ul>
<p>“In sum…the more efficiently you tell them what you’ve got, the better your heading will work.” (<a href="#refs">10</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>6 | <span id="frontload"></span>Front Load Headings with Significant Words</h3>
<p>Start headings with <strong>content-significant words</strong>. Users scan down the left margin. Search engines also benefit. (<a href="#refs">11</a>)</p>
<p><strong>Examples:</strong></p>
<ul>
<li>Purposes of evaluation</li>
<li>IDEA’s definition of “child with a disability”</li>
<li>Identifying children for evaluation</li>
<li>Giving parents notice</li>
<li>Parent consent</li>
<li>Timeframe for initial evaluation</li>
</ul>
<p><a href="#top">Back to top</a></p>
<h3>7 | <span id="bullets"></span>Use Bullets, Numbered Lists, and Numerals</h3>
<p><strong>Bullets</strong> break up walls of text. (<a href="#refs">12</a>)<br />
<strong>Numbered lists</strong> help with step-by-step tasks.<br />
<strong>Use numerals</strong> instead of words. (<a href="#refs">13</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>8 | <span id="center"></span>Don’t Center Headings or Text on the Page</h3>
<p>Users focus on the left margin. Only 30% of attention goes to the right. (<a href="#refs">14</a>)</p>
<p>Keep headings:</p>
<ul>
<li><strong>Left aligned</strong></li>
<li>Styled with <strong>HTML heading tags</strong></li>
</ul>
<p><a href="#top">Back to top</a></p>
<h3>9 | <span id="links"></span>Make Your Links Meaningful</h3>
<p>Key findings:</p>
<ul>
<li>Users <strong>do</strong> pay attention to links.</li>
<li>Left-aligned links get more attention.</li>
<li>Users want to predict what they’ll find.</li>
</ul>
<p><strong>Use content words</strong> in links. (<a href="#refs">16</a>)<br />
<strong>First two words</strong> matter most. (<a href="#refs">17</a>)<br />
<strong>Use action phrases</strong> for action links. (<a href="#refs">18</a>)</p>
<p>Avoid “click here.” (<a href="#refs">19</a>)</p>
<p>Example:</p>
<div style="padding-left: 30px;"><span style="color: #3366ff;">See pictures of Skeletar</span>. (<a href="#refs">20</a>)</div>
<p><a href="#top">Back to top</a></p>
<h3>10 | <span id="testing"></span>Test Your Site with a Few Users</h3>
<p><strong>User testing</strong> helps you create pages that work. Nielsen suggests testing with as few as 5 users. (<a href="#refs">21</a>)</p>
<p>More info:</p>
<ul>
<li><a href="http://www.useit.com/alertbox/20000319.html" target="_blank">Why You Only Need to Test with 5 Users</a></li>
<li><a href="http://www.useit.com/alertbox/20030120.html" target="_blank">Recruiting Test Participants</a></li>
</ul>
<p><a href="#top">Back to top</a></p>
<h3>Want to read another section of Writing for the Web?</h3>
<ul>
<li><a href="/webwriting/reading">How people read on the web</a></li>
<li>Helping readers skim and scan (you’re here)</li>
<li><a href="/webwriting/essential-message-first/">Putting your essential message first</a></li>
<li><a href="/webwriting/chunking">Chunking your information</a></li>
<li><a href="/webwriting/headings">Using headings and subheadings</a></li>
<li><a href="/webwriting/plain">Writing in plain language</a></li>
</ul>
<p><span id="refs"></span><br />
<a href="#top">Back to top</a></p>
<h3>References</h3>
<p>1 | Hunt, B. (n.d.). <em>Introduction to writing copy for the web</em>. Online at: <a href="http://www.webdesignfromscratch.com/copywriting/writing-for-the-web/" target="_blank">http://www.webdesignfromscratch.com/copywriting/writing-for-the-web/</a></p>
<p>2 | Kilian, C. (2007). <em>Writing for the web 3.0</em>.  Bellingham, WA: Self-Counsel Press. Quote from page 17.</p>
<p>3 | Nielsen, J. (2010, March 22). <em>Scrolling and attention</em>. Online at: <a href="http://www.useit.com/alertbox/scrolling-attention.html" target="_blank">http://www.useit.com/alertbox/scrolling-attention.html</a></p>
<p>4 | Hunt, B. (n.d.). <em>Introduction to writing copy for the web</em>. Online at: <a href="http://www.webdesignfromscratch.com/copywriting/writing-for-the-web/" target="_blank">http://www.webdesignfromscratch.com/copywriting/writing-for-the-web/</a></p>
<p>5 | Kilian, C. (2007). <em>Writing for the web 3.0</em>.  Bellingham, WA: Self-Counsel Press.</p>
<p>6 | McAdams, M.J. (2005).<em> Chunks: Writing for the web</em>. Online at: <a href="http://www.macloo.com/webwriting/chunks.htm">http://www.macloo.com/webwriting/chunks.htm</a></p>
<p>7 | McAdams, M.J. (2006). <em>Tips for writing for the web</em>. Online at: <a href="http://www.macloo.com/webwriting/" target="_blank">http://www.macloo.com/webwriting/</a></p>
<p>8 | Kilian, C. (2007). <em>Writing for the web 3.0</em>.  Bellingham, WA: Self-Counsel Press.  Quote from page 32.</p>
<p>9 | Nielsen, J. (2009, April 6). First 2 words: A signal for the scanning eye. Online at: <a href="http://www.useit.com/alertbox/nanocontent.html" target="_blank">http://www.useit.com/alertbox/nanocontent.html</a></p>
<p>10 | McGovern, G. (2001). <em>Web headings that work</em> (Part 4 of the <em>Web Style Content Guide</em>). Available for purchase at: <a href="http://www.gerrymcgovern.com/books/web-content-style-guide" target="_blank">http://www.gerrymcgovern.com/books/web-content-style-guide</a></p>
<p>11 | Nielsen, J. (2007, October 22). Passive voice is redeemed. Online at: <a href="http://www.useit.com/alertbox/passive-voice.html" target="_blank">http://www.useit.com/alertbox/passive-voice.html</a></p>
<p>12 | Redish, J. (2007). <em>Letting go of the words: Writing web content that works</em>. San Francisco, CA: Elsevier.</p>
<p>13 | Nielsen, J. (2007, April 16). <em>Show numbers as numerals when writing for online readers</em>. Online at:<a href="http://www.useit.com/alertbox/writing-numbers.html" target="_blank">http://www.useit.com/alertbox/writing-numbers.html</a></p>
<p>14 | Nielsen, J.  (2010, April 6). <em>Horizontal attention leans left</em>. Online at: <a href="http://www.useit.com/alertbox/horizontal-attention.html" target="_blank">http://www.useit.com/alertbox/horizontal-attention.html</a></p>
<p>15 | Nielsen, J. (2009, April 6).<em> First 2 words: A signal for the scanning eye</em>. Online at: <a href="http://www.useit.com/alertbox/nanocontent.html" target="_blank">http://www.useit.com/alertbox/nanocontent.html</a></p>
<p>16 | Ibid.</p>
<p>17 | Ibid.</p>
<p>18 | Redish, J. (2007). <em>Letting go of the words: Writing web content that works</em>. San Francisco, CA: Elsevier.</p>
<p>19 | Ibid.</p>
<p>20 | Nielsen, J. (2005, October 3). <em>Top ten web design mistakes of 2005</em>.  Online at: <a href="http://www.useit.com/alertbox/designmistakes.html" target="_blank">http://www.useit.com/alertbox/designmistakes.html</a></p>
<p>21 |  Spooner, C. (2009). <em>10 usability crimes you really shouldn’t commit</em>.  Online at: <a href="http://line25.com/articles/10-usability-crimes-you-really-shouldnt-commit" target="_blank">http://line25.com/articles/10-usability-crimes-you-really-shouldnt-commit</a></p>
<p><a href="/#top">Back to top</a></p>
]]></content:encoded>
					
					<wfw:commentRss>https://calmit.org/scanning/feed/</wfw:commentRss>
			<slash:comments>32</slash:comments>
		
		
			</item>
		<item>
		<title>How people read on the web</title>
		<link>https://calmit.org/reading-on-the-web/</link>
		
		<dc:creator><![CDATA[n0t2hungry]]></dc:creator>
		<pubDate>Thu, 02 Jan 2014 22:33:39 +0000</pubDate>
				<category><![CDATA[Writing for the Web]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[writing]]></category>
		<guid isPermaLink="false">https://zenpages.org/?p=2386</guid>

					<description><![CDATA[Most people don’t read through the content we put on our websites. They skim and scan the pages, “taking in headings, the beginnings of paragraphs, and first words of sentences.” (1) They’re looking for something that strikes their attention or matches the question or need they have. If they find it, they dig in and [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Most people don’t read through the content we put on our websites. They skim and scan the pages, “taking in headings, the beginnings of paragraphs, and first words of sentences.” (<a href="#refs">1</a>) They’re looking for something that strikes their attention or matches the question or need they have. If they find it, they dig in and read more carefully.</p>
<p><strong>To help our web visitors find what they’re looking for, we can create webpages that are easy to scan</strong>.<br />
Here are 10 “how-to” tips.</p>
<ol>
<li><a href="#toc">Include a table of contents</a></li>
<li><a href="#start">State the most important information in the first two paragraphs</a></li>
<li><a href="#short">Chunk content in short paragraphs</a></li>
<li><a href="#mainidea">Put only one main idea in a paragraph</a></li>
<li><a href="#headings">Bold headings and subheadings</a></li>
<li><a href="#frontload">Front load headings with significant words</a></li>
<li><a href="#bullets">Use bullets, numbered lists, and numerals</a></li>
<li><a href="#center">Don’t center text on the page</a></li>
<li><a href="#links">Make your links meaningful</a></li>
<li><a href="#testing">Test your site with a few users</a></li>
</ol>
<p><a href="#top">Back to top</a></p>
<h3>1 | <span id="toc"></span>Include a Table of Contents</h3>
<p>You can start webpages (especially longer ones) with a table of contents. This gives readers a quick <strong>snapshot of the content</strong> they’re going to find on that page. The items in the table of contents should match the major headings or sections of the page and be linked to those sections, so that users can “rappel like rock climbers down the text.” (<a href="#refs">2</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>2 | <span id="start"></span>State the Most Important Information in the First Two Paragraphs</h3>
<p>We have to <strong>state the essential message of the page first,</strong> right off the bat. Immediately. In the first two paragraphs. Why? Because web visitors give 80% of their attention to what’s “above the fold” on the webpage. (<a href="#refs">3</a>) “Above the fold” means the content they initially see when they land on the page (without scrolling).</p>
<p>Putting the most important information first means that web users will actually see it. Of course, doing so violates the rules of writing we learned in high school. We’re supposed to start with a nice intro, lay the foundation, give some background and context, and kind of <em>ease into</em> our topic.</p>
<p>But writing for the web is very different from writing for print. Giving a quick overview of the content in the first two paragraphs of a webpage “helps the reader get the point and purpose of a page instantly, letting the user make a quick judgement whether to read on for a bit more detail.” (<a href="#refs">4</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>3 | <span id="short"></span>Chunk Content in Short Paragraphs</h3>
<p><strong>Short and concise paragraphs are easier to scan</strong>—and they get twice as many eye fixations as long paragraphs. (<a href="#refs">5</a>) Web users also pay more attention to the first words in a sentence and to the first and last sentences in a paragraph. So put keywords or <strong>information-carrying words first</strong>, where they’ll catch the eye.</p>
<p><strong>How short is short?</strong> Less than 100 words seems to be the conventional wisdom. Cut out what’s unnecessary. Start a new paragraph when you veer away from the single point of the paragraph. (<a href="#refs">6</a>)</p>
<p>Want more info on <em>how</em> to chunk? Try our companion page <a href="https://zenpages.org/webwriting/chunking/"><em>Chunking Your Content</em></a></p>
<p><a href="#top">Back to top</a></p>
<h3>4 | <span id="mainidea"></span>Put Only One Main Idea in a Paragraph</h3>
<p>Rule of thumb: Limit each paragraph to one main idea. <strong>Front load your message</strong> at the beginning of the paragraph. “While a meandering introductory clause may seem like a good idea to you, the reader might stop reading–before [getting] to the heart of your sentence.” (<a href="#refs">7</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>5 | <span id="headings"></span>Bold Headings and Subheadings</h3>
<p>Headings and subheadings are one of the main ways that web readers skim the page. They act as “landmarks.” (<a href="#refs">8</a>)</p>
<p>To write strong headings:</p>
<ul>
<li><strong>Make headers into questions</strong> your visitors ask.</li>
<li><strong>Write headers as action statements</strong>.</li>
<li><strong>Make headings stand out</strong> visually.</li>
<li><strong>Keep headings short</strong>. Readers see the first two words most clearly. (<a href="#refs">9</a>)</li>
</ul>
<p>In sum: “the more efficiently you tell them what it is you’ve got, the better your heading will work.” (<a href="#refs">10</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>6 | <span id="frontload"></span>Front Load Headings with Significant Words</h3>
<p>Start your headings with <strong>content-significant words</strong>. Users scan down the left margin and notice the first two words. It also helps search engines. (<a href="#refs">11</a>)</p>
<p><strong>Examples:</strong></p>
<ul>
<li>Purposes of evaluation</li>
<li>IDEA’s definition of “child with a disability”</li>
<li>Identifying children for evaluation</li>
<li>Giving parents notice</li>
<li>Parent consent</li>
<li>Timeframe for initial evaluation</li>
</ul>
<p><a href="#top">Back to top</a></p>
<h3>7 | <span id="bullets"></span>Use Bullets, Numbered Lists, and Numerals</h3>
<p><strong>Bullets</strong> break up walls of text and are easy to scan. (<a href="#refs">12</a>)</p>
<p><strong>Numbered lists</strong> help with step-by-step tasks.</p>
<p><strong>Use numerals</strong> instead of spelling out numbers. (<a href="#refs">13</a>)</p>
<p><a href="#top">Back to top</a></p>
<h3>8 | <span id="center"></span>Don’t Center Headings or Text on the Page</h3>
<p>Centering text doesn’t work well on the web. Users focus on the left margin. Only 30% of attention goes to the right side. (<a href="#refs">14</a>)</p>
<p>Keep headings:</p>
<ul>
<li><strong>Left aligned</strong></li>
<li>Styled using <strong>HTML heading tags</strong></li>
</ul>
<p><a href="#top">Back to top</a></p>
<h3>9 | <span id="links"></span>Make Your Links Meaningful</h3>
<p>Key findings:</p>
<ul>
<li>Users <strong>do</strong> pay attention to links.</li>
<li>Links on the <strong>left margin</strong> get more attention.</li>
<li>Users want to predict what they’ll find if they click.</li>
</ul>
<p><strong>Use content words</strong> in links. (<a href="#refs">16</a>)<br />
<strong>First two words</strong> matter most. (<a href="#refs">17</a>)<br />
<strong>Use action phrases</strong> for action links. (<a href="#refs">18</a>)</p>
<p>Avoid “click here.” (<a href="#refs">19</a>)</p>
<p>Example:</p>
<div style="padding-left: 30px;"><span style="color: #3366ff;">See pictures of Skeletar</span>. (<a href="#refs">20</a>)</div>
<p><a href="#top">Back to top</a></p>
<h3>10 | <span id="testing"></span>Test Your Site with a Few Users</h3>
<p><strong>User testing</strong> helps you create pages that work for most visitors. Nielsen suggests you can test with as few as 5 users. (<a href="#refs">21</a>)</p>
<p>If you want to know more:</p>
<ul>
<li><a href="http://www.useit.com/alertbox/20000319.html" target="_blank">Why You Only Need to Test with 5 Users</a></li>
<li><a href="http://www.useit.com/alertbox/20030120.html" target="_blank">Recruiting Test Participants</a></li>
</ul>
<p><a href="#top">Back to top</a></p>
<h3>Want to read another section of Writing for the Web?</h3>
<ul>
<li><a href="/webwriting/reading">How people read on the web</a></li>
<li>Helping readers skim and scan (you’re here)</li>
<li><a href="https://zenpages.org/essential-message-first/">Putting your essential message first</a></li>
<li><a href="/webwriting/chunking">Chunking your information</a></li>
<li><a href="/webwriting/headings">Using headings and subheadings</a></li>
<li><a href="/webwriting/plain">Writing in plain language</a></li>
</ul>
<p><span id="refs"></span><br />
<a href="#top">Back to top</a></p>
<h3>References</h3>
<p>1 | Hunt, B. (n.d.). <em>Introduction to writing copy for the web</em>. Online at: <a href="http://www.webdesignfromscratch.com/copywriting/writing-for-the-web/" target="_blank">http://www.webdesignfromscratch.com/copywriting/writing-for-the-web/</a></p>
<p>2 | Kilian, C. (2007). <em>Writing for the web 3.0</em>.  Bellingham, WA: Self-Counsel Press. Quote from page 17.</p>
<p>3 | Nielsen, J. (2010, March 22). <em>Scrolling and attention</em>. Online at: <a href="http://www.useit.com/alertbox/scrolling-attention.html" target="_blank">http://www.useit.com/alertbox/scrolling-attention.html</a></p>
<p>4 | Hunt, B. (n.d.). <em>Introduction to writing copy for the web</em>. Online at: <a href="http://www.webdesignfromscratch.com/copywriting/writing-for-the-web/" target="_blank">http://www.webdesignfromscratch.com/copywriting/writing-for-the-web/</a></p>
<p>5 | Kilian, C. (2007). <em>Writing for the web 3.0</em>.  Bellingham, WA: Self-Counsel Press.</p>
<p>6 | McAdams, M.J. (2005).<em> Chunks: Writing for the web</em>. Online at: <a href="http://www.macloo.com/webwriting/chunks.htm">http://www.macloo.com/webwriting/chunks.htm</a></p>
<p>7 | McAdams, M.J. (2006). <em>Tips for writing for the web</em>. Online at: <a href="http://www.macloo.com/webwriting/" target="_blank">http://www.macloo.com/webwriting/</a></p>
<p>8 | Kilian, C. (2007). <em>Writing for the web 3.0</em>.  Bellingham, WA: Self-Counsel Press.  Quote from page 32.</p>
<p>9 | Nielsen, J. (2009, April 6). First 2 words: A signal for the scanning eye. Online at: <a href="http://www.useit.com/alertbox/nanocontent.html" target="_blank">http://www.useit.com/alertbox/nanocontent.html</a></p>
<p>10 | McGovern, G. (2001). <em>Web headings that work</em> (Part 4 of the <em>Web Style Content Guide</em>). Available for purchase at: <a href="http://www.gerrymcgovern.com/books/web-content-style-guide" target="_blank">http://www.gerrymcgovern.com/books/web-content-style-guide</a></p>
<p>11 | Nielsen, J. (2007, October 22). Passive voice is redeemed. Online at: <a href="http://www.useit.com/alertbox/passive-voice.html" target="_blank">http://www.useit.com/alertbox/passive-voice.html</a></p>
<p>12 | Redish, J. (2007). <em>Letting go of the words: Writing web content that works</em>. San Francisco, CA: Elsevier.</p>
<p>13 | Nielsen, J. (2007, April 16). <em>Show numbers as numerals when writing for online readers</em>. Online at:<a href="http://www.useit.com/alertbox/writing-numbers.html" target="_blank">http://www.useit.com/alertbox/writing-numbers.html</a></p>
<p>14 | Nielsen, J.  (2010, April 6). <em>Horizontal attention leans left</em>. Online at: <a href="http://www.useit.com/alertbox/horizontal-attention.html" target="_blank">http://www.useit.com/alertbox/horizontal-attention.html</a></p>
<p>15 | Nielsen, J. (2009, April 6).<em> First 2 words: A signal for the scanning eye</em>. Online at: <a href="http://www.useit.com/alertbox/nanocontent.html" target="_blank">http://www.useit.com/alertbox/nanocontent.html</a></p>
<p>16 | Ibid.</p>
<p>17 | Ibid.</p>
<p>18 | Redish, J. (2007). <em>Letting go of the words: Writing web content that works</em>. San Francisco, CA: Elsevier.</p>
<p>19 | Ibid.</p>
<p>20 | Nielsen, J. (2005, October 3). <em>Top ten web design mistakes of 2005</em>.  Online at: <a href="http://www.useit.com/alertbox/designmistakes.html" target="_blank">http://www.useit.com/alertbox/designmistakes.html</a></p>
<p>21 |  Spooner, C. (2009). <em>10 usability crimes you really shouldn’t commit</em>.  Online at: <a href="http://line25.com/articles/10-usability-crimes-you-really-shouldnt-commit" target="_blank">http://line25.com/articles/10-usability-crimes-you-really-shouldnt-commit</a></p>
<p><a href="#top">Back to top</a></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Writing for the Web</title>
		<link>https://calmit.org/writing-for-the-web/</link>
					<comments>https://calmit.org/writing-for-the-web/#comments</comments>
		
		<dc:creator><![CDATA[n0t2hungry]]></dc:creator>
		<pubDate>Wed, 01 Jan 2014 18:48:24 +0000</pubDate>
				<category><![CDATA[Writing for the Web]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[writing]]></category>
		<guid isPermaLink="false">https://zenpages.org/?page_id=2378</guid>

					<description><![CDATA[This excellent information on Writing for the Web is sourced from nichcy.org &#8211; National Dissemination Center for Children with Disabilities. Nichcy&#8217;s website is being phased out in Sept 2014 and Nichcy is encouraging reuse of its material Is your website one of your project’s most valuable ways of disseminating information? If so, this page will [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><span style="font-size: 8pt;"><em>This excellent information on Writing for the Web is sourced from <strong><a href="http://web.archive.org/web/20140722122930/http://nichcy.org/dissemination/tools/webwriting" target="_blank" rel="noopener">nichcy.org </a></strong>&#8211; National Dissemination Center for C<span style="color: #000000;">hildren with Disabilities.</span></em><em> Nichcy&#8217;s website is being <a href="http://web.archive.org/web/20140722130627/http://nichcy.org/about" target="_blank" rel="noopener">phased out in Sept 2014 </a>and <a href="http://web.archive.org/web/20140719031454/http://nichcy.org/dissemination/tools/steal" target="_blank" rel="noopener">Nichcy is encouraging reuse of its material</a></em></span></p>
<p>Is your website one of your project’s most valuable ways of disseminating information? If so, this page will give you<strong><em> 6 tips for writing content</em></strong> that engages and motivates your web visitors—and, most importantly, helps them find the information they’re looking for. The tips are:</p>
<ul>
<li><a href="#read">Understand how people read on the web</a></li>
<li><a href="#scan">Help readers skim and scan</a></li>
<li><a href="#first">Put the essential message first</a></li>
<li><a href="#chunk">Chunk your information</a></li>
<li><a href="#headings">Use headings and subheadings</a></li>
<li><a href="#plain">Write in plain language</a></li>
</ul>
<p><span id="read"></span><br />
<a href="#top">Back to top</a></p>
<p><strong>1 | Understand How People Read on the Web</strong><br />
People come to your webpage with a <em>mission</em>, a question they want to answer, a task they want to know how to do. They don’t really read your content—they scan and skim it until they hit the keyword, question, or heading that speaks to their mission. If they don’t see what they’re looking for, poof! they exit. Sometimes in a matter of seconds.</p>
<p>Here are three interesting findings from research to consider:</p>
<ul>
<li>Web users swipe what they see on their screen in a roughly F-shaped pattern (two horizontal swipes followed by a vertical swipe).</li>
<li>Headings and subheadings catch their eye.</li>
<li>So do headings posed as <em>questions</em>.</li>
</ul>
<div>These findings offer all of us powerful insights into how to design our websites to match the way that users search for information on the web.</div>
<div>||  <a href="/webwriting/reading">Read more about how people read on the web</a></div>
<p><span id="scan"></span><br />
<a href="#top">Back to top</a></p>
<p><strong>2 | Help Readers Skim and Scan</strong><br />
Consider how users read—and don’t read—content. They’ve come on a mission, and you can help them accomplish that mission efficiently with the way you design and write for the web.  Here are four ways you can help web users skim and scan:</p>
<ul>
<li>Use the tips discussed on this page, because all of them will help speed your web visitors to the content that’s relevant<strong><em> to them</em></strong>.</li>
<li>Include a table of contents that makes it easy for readers to see what content the webpage includes and jump to sections of interest to them.</li>
<li>Keep paragraphs short and use the keywords that readers themselves use.</li>
<li>Don’t center text on the page. Visitors often don’t even see it!</li>
</ul>
<p>||   <a href="/webwriting/scanning">Read more about how to help readers skim and scan</a></p>
<p><span id="first"></span><br />
<a href="#top">Back to top</a></p>
<p><strong>3 | Put the Essential Message First </strong><br />
Because web users don’t read text thoroughly or for very long, make sure your webpages state your essential message first, right up front. In the first two paragraphs, in fact. Use keywords and an active voice to give a quick summary that orients readers to the page and what they’ll find there.</p>
<p>People also pay the most attention to the first and last words in a sentence—and to the first and last sentences in a paragraph. Strategically place keywords and important information there. If that information is what visitors are looking for, bull’s eye! They’ve found it—and efficiently.</p>
<p>|| <a href="https://zenpages.org/essential-message-first/">Read more about putting the essential message first</a></p>
<p><span id="chunk"></span><br />
<a href="#top">Back to top</a></p>
<p><strong>4 | Chunk Your Information</strong><br />
The average computer screen doesn’t display a lot of content at one time, and you can’t count on visitors scrolling down to see more. Make it easier for readers to scan your content by:</p>
<ul>
<li>delivering it in small paragraphs (maybe no more than 100 words)</li>
<li>breaking up longer paragraphs into bulleted lists, which readers can quickly skim and, at the same time, absorb</li>
<li>taking out the fluff and the unnecessary, paring the content down to an understandable minimum</li>
</ul>
<p>You can always offer more detailed information on the subject in a separate page, for visitors who need and want the details.</p>
<p>||  <a href="/webwriting/chunking">Read more about chunking content</a></p>
<p><span id="headings"></span><br />
<a href="#top">Back to top</a></p>
<p><strong>5 | Use Headings and Subheadings</strong><br />
Web visitors definitely make use of a webpage’s headings and subheadings in their rapid eye scan for content of interest. Headings and subheadings are also a useful way to break up content and make it easier to read. To write good headings and subheadings:</p>
<ul>
<li>Use active, strong, information-carrying words, which also helps search engines find and share your page</li>
<li>Pose questions, especially questions that mirror those that your web visitors have</li>
<li>Code all headings and subheadings with HTML tags that mark them as an H1, H2, H3, or H4 heading (rather than just bolding the text). This enables visitors who use screen-readers to skim the page, jumping from one heading to another until they strike on the piece of information they were looking for.</li>
</ul>
<p><span style="color: #333333;">||  </span><a href="/webwriting/headings">Read more about using headings and subheadings</a></p>
<p><span id="plain"></span><br />
<a href="#top">Back to top</a></p>
<p><strong>6 | Write in Plain Language</strong><br />
It’s always a good idea to write in plain, understandable language, but never more than on the web. Plain language is friendly and easy-going, avoids jargon (or explains it), and is characterized by shorter sentences written in an active, engaging voice.  It’s especially helpful to readers with limited reading skills or English skills.</p>
<p>||  <a href="/webwriting/plain">Read more about writing in plain language</a></p>
<p><a href="#top">Back to top</a></p>
]]></content:encoded>
					
					<wfw:commentRss>https://calmit.org/writing-for-the-web/feed/</wfw:commentRss>
			<slash:comments>39</slash:comments>
		
		
			</item>
	</channel>
</rss>
