Well, as pointed out you've got invalid characters... I can't quite say what browser it looks 'right' in as they're all pretty messed up, so I'm going to just go down the code and point out what I'm seeing 'wrong'. Warning, I can be brutally frank on this -- don't take it personally, I'm trying to HELP.
The first thing to catch my eye is the Tranny doctype. That is basically the equivalent to saying "I'm writing HTML 3.2 and slapping this on it to PRETEND I'm writing modern code" -- it LITERALLY means "coding in transition from 1997 to 1998"... There's a reason none of us should be writing anything but STRICT after around 2001. (when it truly became real world deployable).
Inlining your style in the page is a waste of bandwidth when it comes to your sub-pages; that's what external stylesheets are for... even during the development stage it's just bad practice to do that; it's also easier to deal with in a separate file since you can open it as a separate window (if your editor is worth a flying fig leaf) and see them side-by-side; the style and what it's being applied to.
You're spending a lot of time setting margins that could be collapsing differently across browsers, NOT resetting all the elements you are using (like the numbered headings), and you should look into the "condensed" versions of properties like margin or font.
... and the fixed width layout with FIXED side margins is really bad from an accessibility standpoint.
You're values are just all over the place -- setting family and size here, margins over here, colors over here... Condense that down to make it easier to maintain and to prevent you from declaring the same things more than once. You've got line-heights smaller than the font-size (which usually doesn't work -- IE will ignore that)...
... and the lack of a MEDIA attribute means your 'screen' style is being sent to everything. I'd put media="screen,projection,tv" on that so that you aren't wasting people's ink on print, and so things like handheld just get the semantic markup instead of trying to give them a layout too big for their displays. (or make a tuned handheld.css to apply little more than FaC - Fonts and Colors)
Not all of that is related to your issue, it's just what I'm seeing.
Once we get down to the markup your heading orders make no sense -- that H2 is NOT starting a new subsection of the page, you're using double breaks to do paragraphs job, you seem to have a div#header element for no good reason, a section of single line break items that LOOKS like it should be a list...
Also if you're going to have block level openings, don't stuff them at the end of excessively long lines... line them up properly -- I think you're missing a few opening tags, but I could simply just not be seeing them (and with the validator rejecting it's character encoding can't verify that).
... and not having the header stuff inside .container is likely why it's not lining up in all browsers here.
The inconsistent placement of comments could also trip bugs in legacy versions of FF/IE -- it kind-of looks like you were trying to place them to mitigate that, but missed it in a couple places (like 'end header')
Also, why say end? Can't we tell that </div> might be the end of something? Just saying...
Likewise you've got a bit of presentational/outdated markup going on (transitional doctype allows for it, doesn't mean one should do it) -- attributes like align or vspace on IMG for example -- much less the inlined style on said plate images.
... and you also have the accessibility failing of using px metric fonts on your content.
First order of business is to drag the markup into this decade by switching to strict, removing the handful of outdated/unneccesary properties, and making the markup a wee bit more semantic. REALLY for everything I just said, your HTML isn't too bad -- the 'content driven' nature of the page left plenty of wiggle room in that regard -- and that's a good thing. Content is king, and on the internet TEXT is the primary type of content.
So... for HTML I'd have:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
SOOPA - Similkameen Okanagan Organic Producers Association
<small>Similkameen Okanagan Organic Producers Association</small>
<li><a href="mailto:firstname.lastname@example.org">CONTACT US</a></li>
The Similkameen Valley is unique in having one of the highest concentrations of organic growers and processors in Canada.
The Organic movement started with small-scale farm growers who believed in healthy, natural, environmentally friendly farming. We have growers in the Valley that have been growing food without toxic chemical inputs for 30 years and longer. These pioneer organic farmers inspired others who moved into the area and began farming organically. They were concerned not only with producing wholesome harvests. They were also determined to improve the quality of the environment that their own food was grown in. Believing that toxic chemical sprays would be harmful to themselves and kill their beneficial insects, whose work they would then inherit, they abandoned the use of pesticides, herbicides and artificial fertilizers. Since healthy soil is the basis for plant health, a strong emphasis on soil building began to develop.
alt="S.O.O.P.A. Certified Stamp"
This new attitude that began developing within the farm community coincided with a heightened awareness of toxic chemical inputs and their damage to the environment. Rachel Carson’s book “Silent Spring” was one of the main influences in the increased interest in the concept of organic farming. There were no standards for organic farmers at this point in time and no definition of what an organic farmer was, there was just a persistent notion that if alternatives to toxic chemical controls were sought, they would very likely be found. In the Similkameen Valley, farm workers were becoming more vocal about their poisonous work environment and began to demand that farmers not spray while they were working in the orchard. A new attitude within the “farm workers community” was growing as well and it was represented by the formation of a Farm Workers Union that called for safer working conditions for people working around toxic chemicals commonly used on farms. Shortly after this the WCB developed the pesticide applicators course, which is designed to teach farm workers about safe application of toxic pesticides and other toxic chemical inputs.
<h2>The Development of Certification Programs & the Formation of SOOPA</h2>
Following the trend developing in the organic industry, the Similkameen Valley organic growers followed suit in 1986 when 10 founding members initiated the formation of the Similkameen Okanagan Organic Producers Association (SOOPA).
SOOPA was formed to develop a certification process and draft standards for our local organic farm community and to give some definition to a way of farming.
Certification had developed in the United States with the formation of the organization called the California Certified Organic Farmers (CCOF), which was founded in 1975. The Organic Crop Improvement Association (OCIA) was founded at about the same time and they were followed by the formation of many other certification organizations. These organizations were in the process of defining the term “organic” by drafting standards that would guarantee quality assurance to their customers.
SOOPA encouraged, and still encourages, a high level of participation from its members
alt="grapes on the vine, ready for picking"
...and the task of drafting comprehensive grower guidelines was undertaken. As a result of these guidelines its membership grew. Originally SOOPA had a 5-year transition period, a very limited material list of allowed substances and a rigid whole farm policy. The system of third party verification was developed within the industry, which led to the formation of the “Independent Organic Inspector Association”, the organization that oversees and trains our verification officers. Over time some of the policies that were drafted when the group first formed have been changed. These changes reflect an attempt to bring all standards for organic production into worldwide unity. In 1995 SOOPA changed from a 5-year transition period to a 3-year transition period. SOOPA was the first certifying organization in British Columbia. SOOPA has farmers in its program producing everything from fruit and grapes, to ground crops, livestock, greenhouse crops and processed products. SOOPA and other BC certification groups created the Organic Alliance, the provincial association of organic groups functioning up to 1993. The Certified Organic Associations of British Columbia (COABC) was founded in 1993 by the provincial government with the help of SOOPA and other BC certification groups using the Food Choice and Disclosure Act. SOOPA has served as a model and inspired other organizations in the area. Today the Similkameen Valley has the highest concentration of organic growers per capita in Canada and it is growing every year.
<h2>Sterile Insect Release Program</h2>
The history of organic farming in the Similkameen Valley is uniquely joined to the fate of the codling moth in this farming area. Codling moth cydia pomenella is the worm in the apple. An uncontrolled population will explode and render an apple crop unmarketable in two years. Agriculture Canada scientists used the Similkameen Valley to develop a non-chemical control method for the codling moth in the 1970’s. By releasing large numbers of sterile males into the wild population they were able to virtually eradicate the insect. In the absence of the persistent presence of the highly toxic chemicals normally used for codling moth control the populations of beneficial parasites and predators were able to grow and do their job of managing secondary pest populations. S.I.R. has proven to be very successful and is an ongoing program.
<h3>Then and Now</h3>
In 1999 SOOPA adopted the COABC standards.
In 2001, at the SOOPA AGM, a resolution was passed to redefine SOOPA’s Whole Farm Organic Policy.
COABC- Certified Organic Associations of BC
<h2>The definition of the Whole Farm Organic is:</h2>
An organic farmer or processor must be committed to managing his/her land, growing or producing a crop or product without the use of harmful, toxic chemicals or substances.
A “farm” means any land used to produce any agricultural commodity.
“Commodity” means any article of trade. Commodities include but are not limited to: produce, farm products, livestock, medicinal and cosmetic materials.
No non-organic agricultural commodities can be grown on a farm.
WHOLE FARM ORGANIC reflects traditional farming methods, as it does not accept the use of toxic chemicals, synthetic fertilizers and genetically modified crops. In an attempt to approach the ideal model, Whole Farm Organic attempts to coexist with and respect all of nature.
<h2>Whole Farm Organic uses:</h2>
Few off-farm inputs
Green manures and fallow cycles for fertility
Spreading of crop residues or animal manures
Mulching and sheet composting
Acceptance of some crop loss due to insect cycles and other natural occurrences
Companion planting to enhance growth and combat insect infestation
There is an emphasis on mechanical and hand labour.
In 2002, a new certification body in BC, PACS , was created primarily for expediting international trade of BC organic products. Several larger SOOPA growers and handlers became members of PACS and SOOPA’s membership was reduced. At the 2002 AGM, a vote was held and it was decided to maintain SOOPA as a certifying body. SOOPA retained its fundamental role of certifying organic farms and continues to serve its members in this capacity.
As members of SOOPA, we pride ourselves on the integrity of our organic methods of farming and the quality of our products. Organic agriculture provides people with healthy, wholesome food. It is also an attempt to create a healthier environment for all living organisms. Hopefully, some day, many more people will realize the importance of healthy soils and clean air and water.
<strong>Happy Organic Farming and Eating</strong>
<!-- #content --></div>
© 2012 SOOPA<br />
BOX 577, KEREMEOS BC V0X 1N0<br />
<!-- #footer --></div>
<!-- #pageWrapper --></div>
I switched to ID's instead of classes on the 'big containers' so that if you want to index using hash, you can. I'd consider perhaps tossing verbose ID's on the various subsections for that reason, but that's up to you.
Gimme a few minutes and I'll belt out the CSS I'd be using with that.