<?xml version="1.0" encoding="utf-8"?>
<!-- generator="wordpress/2.0.5" -->
<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/"
	>

<channel>
	<title>Beast-Blog.com</title>
	<link>http://green-beast.com/blog</link>
	<description>Mike Cherim's Professional and Personal Web Log</description>
	<pubDate>Sat, 14 Jun 2008 13:10:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>
	<language>en</language>
			<item>
		<title>Web Excessibility</title>
		<link>http://green-beast.com/blog/?p=249</link>
		<comments>http://green-beast.com/blog/?p=249#comments</comments>
		<pubDate>Thu, 12 Jun 2008 22:14:03 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Access Counts</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=249</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/access-excess.jpg" width="200" height="150" alt="" /> They say too much of a good thing isn't all that good. It's true, and this fact remains as the statement is applied to web development. Especially when it's applied to the web accessibility branch. Let's explore this. Web accessibility is a good thing, right? You bet it is, from its benefits to myriad users to its benefits to the site in the area of search engine indexing. It's win-win all the way. But before jumping in and going wild with its application and adherence on <em>your</em> next project, making sure your site is accessible to the nth degree and all that, it can be <em>overdone</em>.]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=249</wfw:commentRss>
		</item>
		<item>
		<title>My What-I&#8217;ve-Been-Up-To Post</title>
		<link>http://green-beast.com/blog/?p=309</link>
		<comments>http://green-beast.com/blog/?p=309#comments</comments>
		<pubDate>Tue, 03 Jun 2008 19:05:03 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Beast Ramblings</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=309</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/sans-tempo.jpg" width="200" height="160" alt="" /> I haven't been posting as much, roughly once a week I guess, but not as much as I used to. This post is meant to explain why. To tell you what I've been up to -- or <em>not</em> up to as the case may be. I <em>have</em> been purposely cutting back. I have family, it's the nice time of year, and I have a life-long hobby I'm taking to new level, or trying to. I'll offer more about that at another time. I have been dong fewer web and blog projects, or perhaps you could say I'm allowing more room between projects, making time or all of my other pursuits. Which are varied.]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=309</wfw:commentRss>
		</item>
		<item>
		<title>Web Semantics and Search</title>
		<link>http://green-beast.com/blog/?p=226</link>
		<comments>http://green-beast.com/blog/?p=226#comments</comments>
		<pubDate>Tue, 27 May 2008 04:09:25 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Wicked Wild Web</category>

		<category>Access Counts</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=226</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/search-semantics.jpg" width="200" height="135" alt="" /> Semantics, <i>schemantics</i>, right? If that's your view, you might want to start questioning it now. The importance of web semantics may be on the rise. Semantics is <em>meaning</em>. On the web semantic <abbr title="Hypertext Markup Language">HTML</abbr> conveys this meaning to the user and his or her user agent. It lends itself to web accessibility, and the clear content organization is extraordinarily helpful to being properly indexed by search engines. Someday this fact may be more important than ever thanks to an interesting new approach to search. ]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=226</wfw:commentRss>
		</item>
		<item>
		<title>Killing Off Web Widows</title>
		<link>http://green-beast.com/blog/?p=288</link>
		<comments>http://green-beast.com/blog/?p=288#comments</comments>
		<pubDate>Wed, 14 May 2008 16:29:18 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Beast Ramblings</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=288</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/widow.jpg" width="170" height="170" alt="I miss my words." /> Please, let me explain. I speak not of wives without husbands. I am instead talking about a typographers' term that defines an undesirable situation that looks bad in print and is best avoided for reasons of both aesthetics and readability. The term pertains primarily to print as said, but it also applies to a web page situation that, in my opinion, is also best avoided. I'm not going to provide graphical example of the aforementioned malady, but I will offer a quick definition of the term I've introduced you to.]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=288</wfw:commentRss>
		</item>
		<item>
		<title>Protecting Forms from Spam &#8216;Bots</title>
		<link>http://green-beast.com/blog/?p=220</link>
		<comments>http://green-beast.com/blog/?p=220#comments</comments>
		<pubDate>Wed, 30 Apr 2008 04:19:43 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>All Things PHP</category>

		<category>Security Matters</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=220</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/trapped-bots.jpg" width="250" height="120" alt="" /> Spam robots or spam 'bots abuse comment forms, contact forms, and any forms they can. A true scourge of the web. They exploit insecure forms to send spam. Fortunately there are individual methods of slowing them down. And when used jointly, 'bots can actually be stopped. This post shares four scripted operations I've found particularly helpful to prevent illegitimate posting. In the following examples, at least one variable will be posted, and will appear in this article as <code>$posted_var</code> (meaning it's captured by <code>$_POST[&#039;var&#039;]</code>) to offer greater clarity, but this variable can be whatever you need it to be: name, email, etc. ]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=220</wfw:commentRss>
		</item>
		<item>
		<title>Will the Road to HTML 5 be Rough?</title>
		<link>http://green-beast.com/blog/?p=264</link>
		<comments>http://green-beast.com/blog/?p=264#comments</comments>
		<pubDate>Fri, 18 Apr 2008 14:25:01 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Access Counts</category>

		<category>Coding &#038; Markup</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=264</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/4-2-5.jpg" width="220" height="110" alt="" /> I am really impressed with the <a href="http://www.whatwg.org/specs/web-apps/current-work/"><abbr title="HyperText Markup Language">HTML</abbr> 5 work</a> being performed by <a href="http://ln.hixie.ch/">Ian Hickson</a>, as the draft editor, and the others who are part of the <a href="http://www.whatwg.org/"><acronym title="Web Hypertext Application Technology Working Group">WHATWG</acronym></a>. I'm a fan of the work, and I believe it has promise. From the updated meaning of some of those gray area elements, to the deprecation (made obsolete) of some of the garbage that has littered the web for the past fifteen years, to the introduction of new elements that will offer organizational value where none exists today, to the introduction of new attributes to give all elements clearer meaning, it all bodes well with me. But I cannot help but wonder how we will get there.]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=264</wfw:commentRss>
		</item>
		<item>
		<title>The Minutiae Motherload</title>
		<link>http://green-beast.com/blog/?p=294</link>
		<comments>http://green-beast.com/blog/?p=294#comments</comments>
		<pubDate>Thu, 03 Apr 2008 04:43:19 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Beast Ramblings</category>

		<category>Computer Stuff</category>

		<category>WordPressing</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=294</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/post-it-notes.jpg" width="200" height="200" alt="" /> It's time to get a couple of nasty old Post-It notes off my desk. They're dusty and faded, they no longer stick to anything, and their edges are curled. A sad and all too typical sight no doubt. On them I see what may be little nuggets of one man's wisdom, and maybe a question or two (hard to read). Some of it is crap, some of it is gold, that is up to you. Since none is really worthy of an article of its own, I locked them away in a Post-It note safe so to speak. I am now opening that safe -- and the contents are spilling out. If something looks good to you, feel free to grab it.]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=294</wfw:commentRss>
		</item>
		<item>
		<title>Goodbye Free Email</title>
		<link>http://green-beast.com/blog/?p=232</link>
		<comments>http://green-beast.com/blog/?p=232#comments</comments>
		<pubDate>Tue, 01 Apr 2008 04:01:10 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Wicked Wild Web</category>

		<category>Fiction Dept.</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=232</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/no-free-email.jpg" width="200" height="150" alt="" /> Worldwide email spam volume has grown to unprecedented proportions and something must be done. Something will be. Beginning August 1st, 2008, an action initiated by the International Consortium of Email Regulation (ICER), of Geneva, Switzerland -- supported by leaders in all continents -- will be effected. Precisely this action will be the application of outbound email charges levied by major telecom and cable communications carriers, billed to users (per email or in bulk mail lots) by Internet Service Providers (ISP), and metered at the mail server level.]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=232</wfw:commentRss>
		</item>
		<item>
		<title>Views From a Screen Reader User</title>
		<link>http://green-beast.com/blog/?p=262</link>
		<comments>http://green-beast.com/blog/?p=262#comments</comments>
		<pubDate>Tue, 25 Mar 2008 14:17:22 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Access Counts</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=262</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/sr-view.jpg" width="200" height="150" alt="" /> As it concerns using lists and other non-form structural elements to lay out web forms, my feelings <a href="http://green-beast.com/blog/?p=259" title="Are Lists Becoming the New Tables">have been known</a>. They haven't changed, but after interviewing an experienced screen reader user about this very subject recently, I do have new insights into it -- his perspective anyway. It was a revealing interview. Offering without a doubt relief to some, and probably disappointment to others. Any earned responses will likely determine that.]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=262</wfw:commentRss>
		</item>
		<item>
		<title>Making Bad Images Look a Little Better</title>
		<link>http://green-beast.com/blog/?p=280</link>
		<comments>http://green-beast.com/blog/?p=280#comments</comments>
		<pubDate>Thu, 20 Mar 2008 21:25:40 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Imagery &#038; Graphics</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=280</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/fix-bad-x.jpg" width="200" height="150" alt="" /> This is a technique I use to make less than great images look a little better. Bear in mind this isn't a good technique for print-quality images, nor is it terribly helpful for really large images where down-to-the-pixel perfection is required, but for web-use images under 800x600, this can be a real time saver -- a down and dirty technique -- with no heavy tools required, meaning most mid-range image editing software can handle this. Here's how it's done... In six, or so, easy steps. A poor man's technique. (Dial-up users: This post contains ~130kb of images.)]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=280</wfw:commentRss>
		</item>
		<item>
		<title>A WCAG 2.0 Implementation Site</title>
		<link>http://green-beast.com/blog/?p=221</link>
		<comments>http://green-beast.com/blog/?p=221#comments</comments>
		<pubDate>Tue, 11 Mar 2008 04:43:59 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Wicked Wild Web</category>

		<category>Access Counts</category>

		<category>WordPressing</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=221</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/wcag2-stamp.jpg" width="220" height="150" alt="" /> Over the past month I <a href="http://green-beast.com/blog/?p=254">made mention</a> -- <a href="http://green-beast.com/blog/?p=261">twice</a> -- of a site I was creating that was specifically meant to serve as a practical example of what an accessible web site is supposed to be like and serve the needs of its owner. Since I don't create anything but accessible sites as a rule, this project wasn't really that different than any other project. Initially that was. At first it was a typical Web Content Accessibility Guidelines, <a href="http://www.w3.org/TR/WAI-WEBCONTENT/">WCAG 1.0</a> build, with a focus on meeting all of the <a href="http://www.w3.org/TR/WAI-WEBCONTENT/#priorities">priority 2 checkpoints</a>, "AA," but once word got out, the owner and some of those behind the <a href="http://www.w3.org/TR/WCAG20/">WCAG 2.0</a> requested that I take it further.]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=221</wfw:commentRss>
		</item>
		<item>
		<title>Using the HTML Em and Strong Elements</title>
		<link>http://green-beast.com/blog/?p=234</link>
		<comments>http://green-beast.com/blog/?p=234#comments</comments>
		<pubDate>Thu, 06 Mar 2008 23:10:34 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Coding &#038; Markup</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=234</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/em-strong.jpg" width="180" height="180" alt="" /> The <a href="http://www.w3.org/TR/html401/"><abbr title="HyperText Markup Language">HTML</abbr> 4.01 specification</a> defines <a href="http://www.w3.org/TR/html401/struct/text.html#h-9.2.1">the "phrase" elements</a> <code>em</code> and <code>strong</code> as indicators of emphasis and stronger emphasis, respectively. <a href="http://www.w3.org/TR/xhtml1/">The <abbr title="Extensible HyperText Markup Language">XHTML</abbr> specification</a> doesn't change this, it only demands the use of <del datetime="2008-03-07T12:59:05+00:00">closing elements and</del> proper nesting. These definitions, though, leave something to be desired. Is "stronger emphasis" an inflected inflection?! Is it used when you really, <em>really</em> mean it? Do you add two exclamation points just to get the point across? I don't like any of those options.]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=234</wfw:commentRss>
		</item>
		<item>
		<title>The Four Principles of Web Accessibility</title>
		<link>http://green-beast.com/blog/?p=261</link>
		<comments>http://green-beast.com/blog/?p=261#comments</comments>
		<pubDate>Thu, 28 Feb 2008 17:20:19 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Access Counts</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=261</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/four-principles.jpg" width="250" height="100" alt="" /> I have been fortunate to have had an opportunity to create a web site that is going to be showcased by the <abbr title="World Wide Web Consortium">W3C</abbr>'s Web Content Accessibility Guidelines (WCAG) 2.0 Editors as an early and exemplary implementation of the now nearly complete working draft of the <a href="http://www.w3.org/WAI/GL/WCAG20/">WCAG 2.0</a> (more on this and the WCAG 2.0 later -- expect relevant articles). In this article I will introduce and expound slightly upon the <a href="http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20071218/intro.html#introduction-fourprincs-head">Understanding  [of] the Four Principles of Accessibility</a>. ]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=261</wfw:commentRss>
		</item>
		<item>
		<title>Twelve Things Most Sites Need</title>
		<link>http://green-beast.com/blog/?p=266</link>
		<comments>http://green-beast.com/blog/?p=266#comments</comments>
		<pubDate>Mon, 25 Feb 2008 23:06:24 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Wicked Wild Web</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=266</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/wpdfd-logo.jpg" width="180" height="100" alt="Web Page Design For Designers." /> I was recently contacted by <a href="http://www.wpdfd.com/profiles/davidrodriguez/">David Rodriguez</a> and asked if I was interested in writing an article for the <a href="http://www.wpdfd.com/">Web Page Design For Designers</a> site. I was, so I wrote a two-part article titled "Twelve Things Most Sites Need" covering what I feel are some web site must-haves. The <a href="http://www.wpdfd.com/issues/85/twelve_things_most_sites_need_1/">first part of the article has been published</a>. Enjoy.]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=266</wfw:commentRss>
		</item>
		<item>
		<title>Are Lists Becoming the New Tables?</title>
		<link>http://green-beast.com/blog/?p=259</link>
		<comments>http://green-beast.com/blog/?p=259#comments</comments>
		<pubDate>Fri, 15 Feb 2008 18:50:08 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Wicked Wild Web</category>

		<category>Access Counts</category>

		<category>Coding &#038; Markup</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=259</guid>
		<description><![CDATA[A <a href="http://green-beast.com/blog/?p=124" title="What, When, Who... Internet History Timeline">number of years ago</a> some members of the scientific community and the United States government were involved in a new way to share text and data documents over phone lines. This became the Internet. It didn't take long for people, call them web designers, to adopt and subsequently exploit this technology by using and even misusing the use-specific elements interpreted and rendered by "web browsers."]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=259</wfw:commentRss>
		</item>
		<item>
		<title>Inaccessible Label-Wrapped Form Inputs</title>
		<link>http://green-beast.com/blog/?p=254</link>
		<comments>http://green-beast.com/blog/?p=254#comments</comments>
		<pubDate>Fri, 08 Feb 2008 08:02:48 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Access Counts</category>

		<category>Coding &#038; Markup</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=254</guid>
		<description><![CDATA[<img class="right" src="http://green-beast.com/blog/wp-content/images/label-input.jpg" width="230" height="120" alt="" /> Not too long ago I wrote an article on <a href="http://green-beast.com/blog/?p=206">keeping forms accessible</a>. That was in September of '07. It's an okay article, mostly accurate and helpful. I'll stand behind its recommendations (it's not <em>that</em> old), <em>but</em> one of those recommendations, an allowance actually, is seriously flawed. I am compelled and obligated to correct this. You see, I learned that a normal form-building practice of mine -- wrapping a form <code>input</code> with its <code>label</code> -- can seriously impact the accessibility and usability of a web form. Like hiding an <code>input</code> under a blanket. ]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=254</wfw:commentRss>
<enclosure url='http://green-beast.com/gbcf/_jaws/jaws-formsmode.mp3' length='1027065' type='audio/mpeg'/>
<enclosure url='http://green-beast.com/gbcf/_jaws/jaws-virtualcursormode.mp3' length='1987068' type='audio/mpeg'/>
		</item>
		<item>
		<title>What&#8217;s Best for Web Standards?</title>
		<link>http://green-beast.com/blog/?p=247</link>
		<comments>http://green-beast.com/blog/?p=247#comments</comments>
		<pubDate>Wed, 30 Jan 2008 21:16:48 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>Wicked Wild Web</category>

		<category>Beast Ramblings</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=247</guid>
		<description><![CDATA[<em><img class="right" src="http://green-beast.com/blog/wp-content/images/ie8-switch.jpg" width="200" height="140" alt="This page tested in... Firefox v87.0.1, Opera v110.1, Safari v91.6, oh, and, Internet Explorer v7" /></em> I've been reading the various facts and opinions (<a href="http://green-beast.com/blog/?p=247#read-more">links at the end of the article</a>) and the pros and cons about the plan proposed by Microsoft that will make "<a href="http://en.wikipedia.org/wiki/Quirks_mode" title="Wikipedia: Quirks Mode">DOCTYPE Switch</a>" obsolete beginning with the up-and-coming Internet Explorer 8 (<a href="http://blogs.msdn.com/ie/archive/2007/12/05/internet-explorer-8.aspx">IE8</a>). This news has angered some standards-compliant web developers, while others are finally seeing light at the end of a seemingly endless tunnel -- a tunnel filled with various IE versions of past and present partially blocking the way. Immediately I was against the idea, but I do see the good side of it, too, what with never having to deal with IE version fussing and constant updating again. And if other browser developers jump on board with this idea we will never have to update our sites again (yeah, sure, ha ha). Like a good sales pitch it has appeal. But maybe this is a surface sheen.]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=247</wfw:commentRss>
		</item>
		<item>
		<title>Making the WordPress Menu Smarter</title>
		<link>http://green-beast.com/blog/?p=248</link>
		<comments>http://green-beast.com/blog/?p=248#comments</comments>
		<pubDate>Tue, 29 Jan 2008 16:02:24 +0000</pubDate>
		<dc:creator>Mike Cherim</dc:creator>
		
		<category>All Things PHP</category>

		<category>Do It CSS Style</category>

		<category>WordPressing</category>

		<guid isPermaLink="false">http://green-beast.com/blog/?p=248</guid>
		<description><![CDATA[It was almost a year ago that I published the article "<a href="http://green-beast.com/blog/?p=157">Building a Dynamic WordPress Nav Menu</a>" in which I described the how-to of my <a href="http://green-beast.com/beastblog/">BeastBlog v2</a> theme's navigation menu. I thought I'd revisit the subject since it's been revisited through my projects lately. The menu's gotten smarter. This won't be needed on many sites, and WordPress blogs without "pages" wouldn't need this, but on others it might be a nice enhancement. That's your call.]]></description>
		<wfw:commentRss>http://green-beast.com/blog/?feed=rss2&amp;p=248</wfw:commentRss>
		</item>
	</channel>
</rss>
