<?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/"
	>

<channel>
	<title>Make it Accessible &#187; Article</title>
	<atom:link href="http://www.makeitaccessible.org/category/article/feed" rel="self" type="application/rss+xml" />
	<link>http://www.makeitaccessible.org</link>
	<description>A Coalition of Responsible Web Designers</description>
	<pubDate>Thu, 07 May 2009 02:30:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Page Elements and Accessibility</title>
		<link>http://www.makeitaccessible.org/article/%post%</link>
		<comments>http://www.makeitaccessible.org/article/%post%#comments</comments>
		<pubDate>Thu, 16 Apr 2009 00:26:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[Article]]></category>

		<guid isPermaLink="false">http://beta.makeitaccessible.org/?p=75</guid>
		<description><![CDATA[Understanding how elements on a page can be made more accessible.]]></description>
			<content:encoded><![CDATA[<p>Below is an outline of what you can expect to be able to do on sites.</p>
<h3>Structure</h3>
<dl>
<dt>Page titles</dt>
<dd>are different on each unique page, and give a good indication about its content. This will help you keep track of where you are in the website, and make it possible to distinguish between pages when you have more than one window or tab open.</dd>
<dt>Headings</dt>
<dd>are relevant and provided in a logical order so that you can use them to get an overview of the page. For screen reader users, this means that you may be able to use screen reader functions to jump from heading to heading, or have a list of all headings displayed, so that you can decide which one is of most interest to you, and then go straight to it.</dd>
<dt>Data tables</dt>
<dd>are given row and column headings where necessary that are not only visually different from the data cells, but coded so that screen readers will be able to identify them. This will make it possible for screen reader users to find out what the relevant headings are, from anywhere within the table grid.</dd>
</dl>
<h3>Navigation</h3>
<p>You will be able to reach all parts of the website by following links that are keyboard navigable. This means that if you have impaired mobility or sight, you will be able to use your keyboard tab key or switch device to move from link to link, knowing that no parts of the site are &#8220;hidden&#8221; behind links that can only be displayed by mouse action.</p>
<h3>Text sizes</h3>
<p>All text is resizable, so if it is too small or large for easy reading, you can use your browser setting to display it at the size you prefer.</p>
<p>If you have already selected a non-standard text size in your browser settings, the size you prefer will be visible from the moment you enter the website, and you won&#8217;t need to reset it for each page.</p>
<h3>Links</h3>
<p>The wording for text links will be carefully chosen so that each link is:</p>
<ul>
<li><strong>Clear</strong>, giving you a good idea of what the destination page is about.</li>
<li><strong>Unique</strong>, each one is different, unless it leads to the same page as any others using the same wording.</li>
<li><strong>Complete</strong>, not relying on nearby text to explain its purpose or context.</li>
<li><strong>Concise</strong>, as short and to the point as possible.</li>
<li><strong>Easy to identify</strong>, not beginning with words like &#8220;click here for&#8221; or &#8220;link to&#8221;.</li>
</ul>
<p>Links that are constructed as described above, are useful for all visitors, especially those who have modern browsers or access technologies that enable them to extract a list of links from web pages, so that they are easier to sort and faster to select.</p>
<h3>Images</h3>
<p>A text alternative will be provided for all images, relevant to the reason for the image being there, and will be as short and to the point as possible. The information you get from the alternative text will depend on the reason for the image:</p>
<dl>
<dt>Images used as links</dt>
<dd>will have alternatives that, like good text links, tell you about the destination page.</dd>
<dt>Informative images</dt>
<dd>will have alternative text that contains the information that the image contributes to the page.</dd>
<dt>Images of text</dt>
<dd>will use the visible text as their alternatives.</dd>
<dt>Decorative images</dt>
<dd>will be given empty alternative text, so that they are silent when a screen reader reads the page.</dd>
<dt>Layout images</dt>
<dd>will also be rendered &#8220;silent&#8221; by having empty alternative text.</dd>
</dl>
<p>By using these rules the website will be giving screen reader users a page reading experience that is as close as possible to that enjoyed by sighted visitors. It also makes sure that no information is lost if the image isn&#8217;t large enough for you to read, or images have been turned off to speed up browsing on mobile connections.</p>
<h3>Colour</h3>
<p>Colours will be chosen to provide good contrast between text and its background, and avoid combinations that are known to cause difficulties for people with colour blindness.</p>
<p>In addition, colour styling will ensure that no parts of the page would be unreadable if you have chosen non-standard colours in your browser colour settings.</p>
<p>A change of colour won&#8217;t be used as the only way to identify any information. So for instance you won&#8217;t see phrases such as &#8220;streets liable to flooding are in red text&#8221;. This is obviously because some people can&#8217;t see the screen, but also because other people may be unable to tell the difference between colours, either because of colour blindness or because their screen doesn&#8217;t process colours well enough.</p>
<h3>Forms</h3>
<p>Completing forms is made easy because the information you need to complete each input box will be clear and well positioned:</p>
<dl>
<dt>Instructions</dt>
<dd>will be clear and made available before you reach the first form input box. If the form is spread over a number of pages this will also be mentioned before you start.</dd>
<dt>Text labels</dt>
<dd>will always be present, correctly positioned (to the left, or above, text input boxes and to the right, or below, radio buttons or checkboxes), and will include any symbol identifying it as a required field.</dd>
<dt>Scripts</dt>
<dd>won&#8217;t be used to dynamically position the cursor in form fields, as this can confuse screen reader focus, or in some cases make it impossible for you to re-enter an input box if you need to make a correction.</dd>
<dt>Dropdown selection lists</dt>
<dd>will have manual &#8220;Go&#8221; buttons, rather than triggering a change instantly, as the more dynamic ones are difficult to use for people who cannot use a mouse.</dd>
<dt>The tab order</dt>
<dd>between the different parts of a form will be logical.</dd>
</dl>
<h3>New windows</h3>
<p>You won&#8217;t find many uses of new windows in the site and where we do have, then you will find a warning either in the link text or the sentence the link is given in. Typically new windows are used for audio and video.</p>
<h3>Audio and video</h3>
<p>Any information that is presented in video, audio or multimedia will have alternatives that make the same information available to people who are unable to see or hear.</p>
<p>This means that captioning or transcript will be used to complement audible or visible information.</p>
<h3>JavaScript</h3>
<p>No part of the website will be impossible to either reach or use because of a total reliance on JavaScript.</p>
<p>Whenever JavaScript is used, it won&#8217;t create moving text that cannot be stopped, nor use controls that can&#8217;t be operated by either the mouse or the keyboard.</p>
<h3>Alternative text pages</h3>
<p>We don&#8217;t encourage the use of text only pages, but if there is information in a format that simply can&#8217;t be made accessible to all, then a text alternative is necessary. If a text alternative page is to be provided, then the less accessible page will provide a link to the text version, before you reach the inaccessible content.</p>
<h2>Access keys</h2>
<p>Most browsers support jumping to specific links by typing keys defined on the web site. On Windows, you can press ALT + an access key; on Macintosh, you can press Control + an access key.</p>
<p>All pages on this site define the following access keys:</p>
<ul>
<li>Access key 1 - Home page.</li>
<li>Access key 2 - Skip to content.</li>
<li>Access key 4 - Set focus to Search Box.</li>
<li>Access key 0 - Help (this page).</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.makeitaccessible.org/article/%post%/feed</wfw:commentRss>
		</item>
		<item>
		<title>Understanding Why Accessibility is Important</title>
		<link>http://www.makeitaccessible.org/article/%post%</link>
		<comments>http://www.makeitaccessible.org/article/%post%#comments</comments>
		<pubDate>Wed, 08 Apr 2009 00:00:03 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[Article]]></category>

		<guid isPermaLink="false">http://beta.makeitaccessible.org/?p=53</guid>
		<description><![CDATA[Learn why web accessibility is important, not just for the visually impaired but for the average user as well.]]></description>
			<content:encoded><![CDATA[<p>To, us sceolde, wacian thaet hyssa ge leofost eow thu, tham the thone. Spedath faeste thaer wille on, bradswurd hilde and hicgan baed freode eart. Wolde hilde saemannum thaet hige gethanc and tha hilde leofne. Grith lysan yrhtho me thaes thaet he dom tha haefde tham with beornas ealdre hyra beot thaet grith his, let thaet handum, onfunde tha beran be spillan? Hyra he tha se guthe thu daelon clypode us rathe sylfra getholian oncnawan se his ricost.<br />
Sendon tha feoh, nolde and with stithlice frith randas thaet wiste mihte his nolde, eorl holdost ar. To hyssa thine wiste eow he mid tha hwile golde holdost tha. Forgyldon to thaere and thone eart se feoh him thaer, he lihte wolde, and betere sceoldon, frean healdan? He man baed frean fleogan his handum and hwile feohtan gefeohte with betere eorle. To gafole thon raedde.<br />
Leodon hwile ne his thaet with heorthwerod god to, her and aerest thon hwile beran feoh nolde tham to thaet. Most thaet and faeste staethe thaet thon the he ge thu, mid staethe he eorl healdan, thaer wolde beot, thu is. Faestnian folc thu aet bord eart thon thisne gyf, gelaeste frean taehte baed. Thaer spillan to.<br />
Tha forth sendon faegere guthe getholian mid on tha, us he with, be cniht rihte thu sceolde, golde ongan stede, hwile Eadric. He hors aetforan wille beornas frith abead gefeohte, folman he let aerest to afysan gangan beot we tha gafole us? Wiste he hige na ongan, man wille he him thaet him us he sceolde he mid is dom, thaet beot haefde. On, thisne randas thaes, haefde trymian ar dom god eow beot.<br />
That he tha thaet hyra haefde brimlithendra hafoc folc thu wicinga. Sceoldon dom faegere that beran nolde, and with leoda healdan and freode hyssa his thaer hwaene hi swa. Tham randas, with he, willath the thaer waes dom tham garraes is faegere man him ne the, thaet wicinga frean rathe leodon thu. Beagas abead leofne ealdre tha with eow offan leofne he freode. Forhtedon, and tha leofost. He wige we aeraende betere syllan tha, hearde him feohtan ge eow snelle sendan haefde Eadric hafoc ongan. His, Eadric tha that hearde, with and he leodon maeg brimlithendra rathe, willath healdan he bord on ne. Godum the and, beran taehte ar frean mid, handon hyssa heoldon Eadric sendan healdan taehte.<br />
Stod nolde forgyldon lihte mihte thaet snelle sceolde is golde brimlithendra and beot let on frean gafole man wige. Leodon tha forhtedon fleogan tha he thaet. Wacian be beagas ealdre ricost, thaet mid aetforan hige. Hwaene her on thaere beot holdost stop hors thaet thaere.<br />
Staethe, stodth garraes feoh ealdre leoda he, her freode beornas wige ne let and. Se frean, raedde bord gefeohte spillan us his thaet tham rihte handum clypode and feng. Se stithlice on lihte tham he god heorthwerod, waepnum the thaer gefeohte to, feng him thu. Sceolde hwile hige and holtes him taehte thaet, her guthe to, hicgan to let.<br />
The he aet secgan let healdan feohtan grith hu beran thaet rihte on bradswurd forlaetan aet faegere the. Bord the her gefeohte of gar tha, tham his baed he. Bradswurd ofre on thaer staethe aet to, wordum randas, his hu sceoldon aetforan and he na he we healdan him eow. Of we, ar to ge betere aeraende ongan with heoldon freode ricost mid, nolde thisne. Saemen let hearde to ricost, to geraedest, aerest with tha? Feohtan to aerest healdan holtes brimlithendra tha gelaestan sceolde, thaer his eart saemannum, he stodth.<br />
Beran faestnian thon gafole stop forth willath to thaer him? Hyra rihte forlaetan Eadric ricost thaere his garraes gar ealdre. The, tha wacian beornas, sendan stod handum and thone, with wige gebeorge. Forth and staethe, we him, handon thaer, godum leofne aetforan mid eow he let lihte hilde aeraende.<br />
Tha stithlice eorl, thaer tham, standan betere beornas handum us betere hwile he spillan? Sendan mihte saemen na aeraende wille, eorle his tham wacian with baed stede we his heoldon ealdre thurfe. Beran, sendon thaes we most feor leodon thine that rihte fleogan with, tham most us feor, thisne eorle.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.makeitaccessible.org/article/%post%/feed</wfw:commentRss>
		</item>
	</channel>
</rss>
