<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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>Comments for Accessibility News &amp; Review</title>
	<atom:link href="http://www.kenotten.com/index.php?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.kenotten.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 09 Jun 2010 19:32:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Toilet Rooms Part 1: Scoping by Darrel McDaniel</title>
		<link>http://www.kenotten.com/?p=97&#038;cpage=1#comment-885</link>
		<dc:creator>Darrel McDaniel</dc:creator>
		<pubDate>Wed, 09 Jun 2010 19:32:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.kenotten.com/?p=97#comment-885</guid>
		<description>Ken, thanks for the heads up and keep them coming.  We have 4 projects where the boys toilets will have a urinal/WC count of 6 or more, so we will now redesign to provide the ambulatory compartment.</description>
		<content:encoded><![CDATA[<p>Ken, thanks for the heads up and keep them coming.  We have 4 projects where the boys toilets will have a urinal/WC count of 6 or more, so we will now redesign to provide the ambulatory compartment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The not-so-final word on Curb Ramps and Truncated Domes by Mark Handler</title>
		<link>http://www.kenotten.com/?p=15&#038;cpage=1#comment-267</link>
		<dc:creator>Mark Handler</dc:creator>
		<pubDate>Fri, 02 Apr 2010 01:54:30 +0000</pubDate>
		<guid isPermaLink="false">http://kenotten.wordpress.com/?p=15#comment-267</guid>
		<description>Thanks for the info
California  Access Codes also require the DW, and will even after the new ADAAG is approved.</description>
		<content:encoded><![CDATA[<p>Thanks for the info<br />
California  Access Codes also require the DW, and will even after the new ADAAG is approved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New ADAAG-R Almost Here! by kenotten</title>
		<link>http://www.kenotten.com/?p=77&#038;cpage=1#comment-8</link>
		<dc:creator>kenotten</dc:creator>
		<pubDate>Wed, 30 Dec 2009 18:59:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.kenotten.com/?p=77#comment-8</guid>
		<description>Fred,
&lt;p&gt;
A number of things &lt;em&gt;could &lt;/em&gt;happen, but here&#039;s what I think will happen.  My understanding is that TDLR may have been working on a revision to the TAS based on the new ADA/ABA guidelines, but I don&#039;t have any personal knowledge of anything.  It is undoubtedly a monumental task, and the Texas Legislature meets in odd numbered years, so unless the Governor calls a Special Session, we won&#039;t have new standards until 2011 or later.
&lt;p&gt;
Since that is an untenable proposition, and since the option of presenting a revised TAS and approving it with all the required hearings, comment periods etc., is probably too big an exercise to complete in a timely fashion, here is my prediction:  the Governor will call a Special Session and revise the TABA to change the design and construction standards from the TAS to the new ADA/ABA Guidelines as they are published by the feds.  Sometime down the line Texas can then revise or amend them, or create a new version of the TAS.
&lt;p&gt;
Looking at the history of Texas accessibility laws and associated guidelines, one will find that our design standards predate the ADAAG (they were based on ANSI).  It probably made sense when the ADAAG came out for Texas to maintain its own set of standards for accessible design, but with this new ADA/ABA Guideline and the efforts on the federal side to harmonize the many divergent accessibility codes (FHA guidelines, ADAAG, ANSI A117.1, IBC etc.), along with the merger of the several model building code organizations into the ICC, it seems logical that TDLR would want to not muddy the waters by introducing a new &quot;different&quot; set of accessibility guidelines in the form of a revised TAS.  
&lt;p&gt;
So, to recap, I think the Legislature will meet in Special Session, amend the Texas Architectural Barriers Act to essentially replace the 1994 TAS with the new ADA/ABA Guidelines and perhaps a number of amendments.  I honestly don&#039;t think anything else will change, although &lt;em&gt;everything&lt;/em&gt; could!  It seems to me that the infrastructure currently in place (especially with the RAS program) works well, and local jurisdictions have become comfortable with allowing enforcement of accessibility code issues at the state level.  
&lt;p&gt;
Having firsthand experienced (more like a nightmare) of a statewide accessibility code (like that in California with Title 24) enforced at both the state and local levels, I wouldn&#039;t recommend Texas regressing back to a scenario like that.  What we have works, so the least amount of change the better (in my opinion).
&lt;p&gt;
That&#039;s my story and I&#039;m sticking to it.  For now.
&lt;p&gt;
Ken</description>
		<content:encoded><![CDATA[<p>Fred,</p>
<p>
A number of things <em>could </em>happen, but here&#8217;s what I think will happen.  My understanding is that TDLR may have been working on a revision to the TAS based on the new ADA/ABA guidelines, but I don&#8217;t have any personal knowledge of anything.  It is undoubtedly a monumental task, and the Texas Legislature meets in odd numbered years, so unless the Governor calls a Special Session, we won&#8217;t have new standards until 2011 or later.
</p>
<p>
Since that is an untenable proposition, and since the option of presenting a revised TAS and approving it with all the required hearings, comment periods etc., is probably too big an exercise to complete in a timely fashion, here is my prediction:  the Governor will call a Special Session and revise the TABA to change the design and construction standards from the TAS to the new ADA/ABA Guidelines as they are published by the feds.  Sometime down the line Texas can then revise or amend them, or create a new version of the TAS.
</p>
<p>
Looking at the history of Texas accessibility laws and associated guidelines, one will find that our design standards predate the ADAAG (they were based on ANSI).  It probably made sense when the ADAAG came out for Texas to maintain its own set of standards for accessible design, but with this new ADA/ABA Guideline and the efforts on the federal side to harmonize the many divergent accessibility codes (FHA guidelines, ADAAG, ANSI A117.1, IBC etc.), along with the merger of the several model building code organizations into the ICC, it seems logical that TDLR would want to not muddy the waters by introducing a new &#8220;different&#8221; set of accessibility guidelines in the form of a revised TAS.
</p>
<p>
So, to recap, I think the Legislature will meet in Special Session, amend the Texas Architectural Barriers Act to essentially replace the 1994 TAS with the new ADA/ABA Guidelines and perhaps a number of amendments.  I honestly don&#8217;t think anything else will change, although <em>everything</em> could!  It seems to me that the infrastructure currently in place (especially with the RAS program) works well, and local jurisdictions have become comfortable with allowing enforcement of accessibility code issues at the state level.
</p>
<p>
Having firsthand experienced (more like a nightmare) of a statewide accessibility code (like that in California with Title 24) enforced at both the state and local levels, I wouldn&#8217;t recommend Texas regressing back to a scenario like that.  What we have works, so the least amount of change the better (in my opinion).
</p>
<p>
That&#8217;s my story and I&#8217;m sticking to it.  For now.
</p>
<p>
Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Timeline for New ADAAG-R by kenotten</title>
		<link>http://www.kenotten.com/?p=51&#038;cpage=1#comment-7</link>
		<dc:creator>kenotten</dc:creator>
		<pubDate>Wed, 30 Dec 2009 18:09:22 +0000</pubDate>
		<guid isPermaLink="false">http://kenotten.wordpress.com/?p=51#comment-7</guid>
		<description>Thanks for the kind words.  Permission is granted to grab our RSS feed and keep up!  Thanks.  Ken Otten</description>
		<content:encoded><![CDATA[<p>Thanks for the kind words.  Permission is granted to grab our RSS feed and keep up!  Thanks.  Ken Otten</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New ADAAG-R Almost Here! by Fred Cawyer</title>
		<link>http://www.kenotten.com/?p=77&#038;cpage=1#comment-5</link>
		<dc:creator>Fred Cawyer</dc:creator>
		<pubDate>Sun, 27 Dec 2009 00:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.kenotten.com/?p=77#comment-5</guid>
		<description>What do you think will happen in Texas ?</description>
		<content:encoded><![CDATA[<p>What do you think will happen in Texas ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ADAAG-R: Reach Range by Jeff Mastin in CA</title>
		<link>http://www.kenotten.com/?p=76&#038;cpage=1#comment-4</link>
		<dc:creator>Jeff Mastin in CA</dc:creator>
		<pubDate>Sat, 07 Nov 2009 18:29:18 +0000</pubDate>
		<guid isPermaLink="false">http://kenotten.wordpress.com/?p=76#comment-4</guid>
		<description>Oh, you are right, the 44&quot; offers more options, like providing a table. Thanks.</description>
		<content:encoded><![CDATA[<p>Oh, you are right, the 44&#8243; offers more options, like providing a table. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ADAAG-R: Reach Range by Kenneth Otten</title>
		<link>http://www.kenotten.com/?p=76&#038;cpage=1#comment-3</link>
		<dc:creator>Kenneth Otten</dc:creator>
		<pubDate>Sat, 07 Nov 2009 17:38:31 +0000</pubDate>
		<guid isPermaLink="false">http://kenotten.wordpress.com/?p=76#comment-3</guid>
		<description>Jeff,

Thanks for the comments!  This is a good observation, and in a future article I hope to detail all the specifications for reach ranges, especially those over obstructions.  One issue parallels your comments: When reaching forward over an obstruction greater than 25 inches, the maximum reach height is reduced to 44 inches AFF.

&lt;img src=&quot;http://www.access-board.gov/ada-aba/figures/ADA-AB17.gif&quot; alt=&quot;Reaching over an abstruction&quot; /&gt;</description>
		<content:encoded><![CDATA[<p>Jeff,</p>
<p>Thanks for the comments!  This is a good observation, and in a future article I hope to detail all the specifications for reach ranges, especially those over obstructions.  One issue parallels your comments: When reaching forward over an obstruction greater than 25 inches, the maximum reach height is reduced to 44 inches AFF.</p>
<p><img src="http://www.access-board.gov/ada-aba/figures/ADA-AB17.gif" alt="Reaching over an abstruction" /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ADAAG-R: Reach Range by Jeff Mastin in CA</title>
		<link>http://www.kenotten.com/?p=76&#038;cpage=1#comment-2</link>
		<dc:creator>Jeff Mastin in CA</dc:creator>
		<pubDate>Sat, 07 Nov 2009 17:23:40 +0000</pubDate>
		<guid isPermaLink="false">http://kenotten.wordpress.com/?p=76#comment-2</guid>
		<description>Ken Otten elucidations 24/7? Pinch me I must be dreaming!  -Seriously, very helpful and from a knowledgable source. My 2 cents:

It is also a good idea for those designing such operable items to place them at max. 46&quot; high as this affords the most options in reach-over-obstructions for both approaches; important in future (inevitable) placing of furniture and such by the user.

Thanks Ken for a great series.</description>
		<content:encoded><![CDATA[<p>Ken Otten elucidations 24/7? Pinch me I must be dreaming!  -Seriously, very helpful and from a knowledgable source. My 2 cents:</p>
<p>It is also a good idea for those designing such operable items to place them at max. 46&#8243; high as this affords the most options in reach-over-obstructions for both approaches; important in future (inevitable) placing of furniture and such by the user.</p>
<p>Thanks Ken for a great series.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
