<?xml version="1.0" encoding="utf-8"?>
	
		<feed xmlns="http://www.w3.org/2005/Atom">
			<title type="text">Boagworld - Accessibility for the visually impaired?</title>
			<updated>2010-09-07T16:39:07-07:00</updated>
			<id>http://boagworld.com/forum/</id>
			<link rel="alternate" type="text/html" hreflang="en"
				href="http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35400&amp;page=1"/>
			<link rel="self" type="application/atom+xml"
				href="http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35400&amp;Feed=ATOM&amp;page=1"/>
			<generator
				uri="http://getvanilla.com/"
				version="1.1.10">
				Lussumo Vanilla &amp; Feed Publisher
			</generator>
			<entry>
		<title>Accessibility for the visually impaired?</title>
		<link rel="alternate" href="http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35397#Comment_35397" type="application/xhtml+xml" hreflang="en"/>
		<id>http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35397#Comment_35397</id>
		<published>2009-12-06T04:19:26-08:00</published>
		<updated>2010-09-07T16:39:07-07:00</updated>
		<author>
			<name>RalphSaunders</name>
			<uri>http://boagworld.com/forum/account.php?u=2826</uri>
		</author>
		<summary type="text" xml:lang="en">
			I was having a discussion with a web developer last night about how important accessibility was and the best way to go about making your sites accessible. I understand degrading your site with older ...
		</summary>
		<content type="html">
			<![CDATA[I was having a discussion with a web developer last night about how important accessibility was and the best way to go about making your sites accessible. I understand degrading your site with older browsers and how to do it but when it came to making your site accessible to the visually impaired I was at a bit of a loss.<br /><br />He said that he would do his best to make the HTML easy to read without CSS. Which I could understand as a matter of practice but how does this effect visually impaired people?<br /><br />I guess what I am asking is, what is the best way to cater for the visually impaired when I am designing and developing websites?<br /><br />Thanks<br />Ralph]]>
		</content>
	</entry>
	<entry>
		<title>Accessibility for the visually impaired?</title>
		<link rel="alternate" href="http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35400#Comment_35400" type="application/xhtml+xml" hreflang="en"/>
		<id>http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35400#Comment_35400</id>
		<published>2009-12-06T08:12:30-08:00</published>
		<updated>2010-09-07T16:39:07-07:00</updated>
		<author>
			<name>sypher</name>
			<uri>http://boagworld.com/forum/account.php?u=2732</uri>
		</author>
		<summary type="text" xml:lang="en">
			You also have to think about colour blindness too, with reg-green becoming the most common.

http://en.wikipedia.org/wiki/Color_blindness#Design_implications_of_color_blindness
		</summary>
		<content type="html">
			<![CDATA[You also have to think about colour blindness too, with reg-green becoming the most common.<br /><br /><a href="http://en.wikipedia.org/wiki/Color_blindness#Design_implications_of_color_blindness" target="_blank" rel="nofollow">http://en.wikipedia.org/wiki/Color_blindness#Design_implications_of_color_blindness</a>]]>
		</content>
	</entry>
	<entry>
		<title>Accessibility for the visually impaired?</title>
		<link rel="alternate" href="http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35406#Comment_35406" type="application/xhtml+xml" hreflang="en"/>
		<id>http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35406#Comment_35406</id>
		<published>2009-12-06T20:03:23-08:00</published>
		<updated>2009-12-06T20:05:30-08:00</updated>
		<author>
			<name>richquick</name>
			<uri>http://boagworld.com/forum/account.php?u=91</uri>
		</author>
		<summary type="text" xml:lang="en">
			There's a LOT to consider, when it comes to accessibility .. even if you're just focussing on the narrow area of the blind.

Blind people use screen readers.

So, the best way to find out how ...
		</summary>
		<content type="html">
			<![CDATA[There's a LOT to consider, when it comes to accessibility .. even if you're just focussing on the narrow area of the blind.<br /><br />Blind people use screen readers.<br /><br />So, the best way to find out how your site appears to them is to use one or more to visit your site.<br /><br />The best piece of advice I can give you is to find someone who is blind and sit in on them visiting some sites .. ideally including your site.<br /><br />If there's a local blind charity they may be able to arrange this.<br /><br />You'll learn so much.<br /><br />IBM homepage reader has a 30 day trial.  The most common screenreader is Jaws.  Dolphin's another one.<br /><br />Testing your site with CSS turned off will help .. but won't do everything.  Test with images turned off as well .. that'll help.<br /><br />I also use Lynx .. a text only browser .. this highlights a lot of problems.<br /><br />You need to do more than a cursory look at the page.<br /><br />You need to try to perform different tasks.<br /><br />For example, finding a phone number, submiting a contact form etc<br /><br />Things that tend to crop up lots as issues in my experience include:<br /><br />- Links that make no sense out of content .. such as "click here"<br />- Form elements that don't make sense out of context ... eg. without labels.<br />- Language / instructions that require you to be sighted (click on the green button)<br />- Abbreviations that don't make sense when read.  "Nr. London" may make sense to you.  But when you hear "ner London" it isn't obvious what it is.<br /><br />Read up on WCAG 1 and 2.  Look at the RNIB's site (not for design tips, though!!).  Read Joe Clarke's site.<br /><br />Another thing to consider is partial sightedness.<br /><br />Leesy, one of the other forum leaders, knows quite a bit about this.  Leesy - where did you put your Barcamp slides?]]>
		</content>
	</entry>
	<entry>
		<title>Accessibility for the visually impaired?</title>
		<link rel="alternate" href="http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35407#Comment_35407" type="application/xhtml+xml" hreflang="en"/>
		<id>http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35407#Comment_35407</id>
		<published>2009-12-06T20:17:36-08:00</published>
		<updated>2010-09-07T16:39:07-07:00</updated>
		<author>
			<name>Doug S.</name>
			<uri>http://boagworld.com/forum/account.php?u=1797</uri>
		</author>
		<summary type="text" xml:lang="en">
			I think Jamie might be of some help here as well.

Normally what I do to test accessibility on my site is:

(1) Using Firefox, I disable javascript, CSS and images. I basically turn the browser ...
		</summary>
		<content type="html">
			<![CDATA[I think Jamie might be of some help here as well.<br /><br />Normally what I do to test accessibility on my site is:<br /><br />(1) Using Firefox, I disable java&#115cript, CSS and images. I basically turn the browser into purely text so that only the raw markup can be seen. I then make sure the site makes sense if I were to read it out to myself. I look to see if it's easy to jump from one bit to another without having to go through all the content.<br /><br />(2) I take a screen shot of the full page and drop it into Photoshop. There I throw contrast up and down to make sure everything is still clear, play with the saturation, just try to see how far I have to mess with the colors and leveling before it becomes illegible to someone like me who has no trouble seeing things on a screen. If I have to go to extremes to destroy my site (not talking about look but usability) then I figure I'm safe.<br /><br />That's how I deal with the visually impaired. Don't forget that's only one type. I also tend to use big buttons and hit areas for those with motor-function issues. For example, aside from text links I try to make nothing smaller than 20px. Ever seen an elderly person with arthritis try to click a tiny button? They have to fight their body just to make the mouse move, precision isn't in their list of tricks.<br /><br />I'd love to sit down with someone and watch them navigate the web with a screen reader. I'd also love to try it myself, and I may do so at some point.]]>
		</content>
	</entry>
	<entry>
		<title>Accessibility for the visually impaired?</title>
		<link rel="alternate" href="http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35411#Comment_35411" type="application/xhtml+xml" hreflang="en"/>
		<id>http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35411#Comment_35411</id>
		<published>2009-12-07T05:04:48-08:00</published>
		<updated>2009-12-07T05:10:18-08:00</updated>
		<author>
			<name>Leesy</name>
			<uri>http://boagworld.com/forum/account.php?u=57</uri>
		</author>
		<summary type="text" xml:lang="en">
			They are still in my head Rich.  I've been meaning to rewrite it for ages but haven't got round to it yet.  I'll force myself to do it this week :)

So onto the subject - Saying &quot;visually ...
		</summary>
		<content type="html">
			<![CDATA[They are still in my head Rich.  I've been meaning to rewrite it for ages but haven't got round to it yet.  I'll force myself to do it this week :)<br /><br />So onto the subject - Saying "visually impaired" can mean so many things.  I am visually impaired (and "legally blind") but I am sitting here at my PC with no special equipment or software and using the web perfectly well.  I can use the website with no problems because the site is well designed.<br /><br />As mentioned, making sure the page is laid out semantically is helpful.  This will allow screen readers to provide the best experience for using the site.<br /><br />Provide alternative stylesheets which allow users to switch to things like high contrast views, larger text etc.<br /><br />Think about page flow.  Keep things in a logical order.  Things jumping from one side of the page to the other can make it harder for people to read.  For example, this page I find harder to read than others: <a href="http://www.smashingmagazine.com/the-death-of-the-blog-post/">http://www.smashingmagazine.com/the-death-of-the-blog-post/</a>.  First the text is on the left, then it's on the right, now it's on the left again.  There's no consistency which makes it harder to read.<br /><br />And I can't remember what else I talked about in my BCL7 slides so I'll try and dig them up later if I want to add more suggestions.<br /><br />Here's some reading material I really need to get through sometime (suggested to me by Nick Dunn - cheers Nick!):<br /><a href="http://www.amazon.co.uk/dp/1590596382/">http://www.amazon.co.uk/dp/1590596382/</a><br /><a href="http://www.amazon.co.uk/dp/1934356026/">http://www.amazon.co.uk/dp/1934356026/</a><br /><a href="http://diveintoaccessibility.org/">http://diveintoaccessibility.org/</a><br /><a href="http://joeclark.org/book/sashay/serialization/">http://joeclark.org/book/sashay/serialization/</a>]]>
		</content>
	</entry>
	<entry>
		<title>Accessibility for the visually impaired?</title>
		<link rel="alternate" href="http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35436#Comment_35436" type="application/xhtml+xml" hreflang="en"/>
		<id>http://boagworld.com/forum/comments.php?DiscussionID=5086&amp;Focus=35436#Comment_35436</id>
		<published>2009-12-08T21:51:07-08:00</published>
		<updated>2010-09-07T16:39:07-07:00</updated>
		<author>
			<name>RalphSaunders</name>
			<uri>http://boagworld.com/forum/account.php?u=2826</uri>
		</author>
		<summary type="text" xml:lang="en">
			Thankyou guys. Loads to think and play with now. Will try using a screen reader later on this week. :)
		</summary>
		<content type="html">
			<![CDATA[Thankyou guys. Loads to think and play with now. Will try using a screen reader later on this week. :)]]>
		</content>
	</entry>
	
		</feed>