Re: [WSG] Looking for help and critiques on a new site
Seona
Your page seem to have a problem with horizontal scrolling, I noticed it when I tried
to tab through your menu and
ended up off the main screen after hitting the 'Bathroom' heading... I don't know
enough about CSS (yet :) to work out
why this happens so I hope someone else will be able to help you.
Checked on PC in IE 5.5, Netscape 7.1, Firefox and Opera 7.51 (in the last two
browsers the nav menu didn't work very
well and in the last three browsers the base font comes out much too small)
One more thing... the menu resizes badly in 800x600 res.
cheers
Iza
[EMAIL PROTECTED] 04/07/04 12:36
Seona,
Messages get missed. People are busy and help when they can. Don't read
anything into it :)
1. your first problem is due to this:
a name=topnbsp;/a
Take out the non-breaking space and your columns will sit against the top of
the viewport.
It affected the left and middle column because they are in normal flow and
did not affect the logo in the top right corner as it was absolutely
positioned (out of normal flow). Email me offlist if this is still unclear.
To troubleshoot these sort of problems, the ultimate method is to gradually
delete items off the page until you fix the problem. Then restore gradually
once you have isolated to offending css rule of html code. And yes, there
may be times when the last line left on the page is the offending one. :)
2. your other problem is the bottom left corner. The method you are using
requires you to use a non-transparent top rounded corner image (rather than
a transparent image) otherwise the parent divs background will show through
(as it does in your sample).
You might be better off taking off the orange colour and border off and
applying them using another method.
#specials_panel {
border-right: 2px solid #FF; /* remove */
background-color: #FFCC00; /* remove */
margin-top: 10px; }
Again, if this makes no sense (writing it a bit of a rush here) email me
offlist
Critiques? Apologies that these are all negative but here goes...
1. Your page suffers from what many refer to as id-it is (unnecessary ids
scattered around the page. Use descendant selectors to achieve the same
result without the need for additional ids
2. The edges of some of your images dither badly against the background
image - leaving a slight halo of unwanted colour. Hard to overcome when
applied on top of a patterned background but if you cut the images out of a
similar colour to the background you will achieve a better result.
3. some issues to do with absolute positioning and static content when the
viewport is very narrow.
4. the right nav dropdown breaks in Safari (haven't tested any other
browser)
HTH and good luck!
Russ
So I'm left with a few possible conclusions:
a) The questions weren't on-topic enough to be worth answering - don't think
this one is the case.
b) The questions weren't interesting enough to be worth answering.
c) I'm just chatting to myself here - really hope this one isn't the case.
Anyway, the page can be seen at:
http://216.119.123.23
It's still very much under construction, so most of the links don't work yet
- just a warning. :)
The css is at:
http://216.119.123.23/_styles/sample.css
So, help, advice and critiques are greatly welcomed.
Cheers,
Seona.
*
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
*
*
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
*
RE: [WSG] 508??
I think Judy Brewer, the Director of WAI hit the nail on the head when she said: In no case can automated Web accessibility evaluation tools determine conformance to all WCAG 1.0 Checkpoints at a given priority level. Therefore, manual evaluation by a knowledgeable expert using a variety of approaches is always an essential aspect of any conformance evaluation. Her full article Web Accessibility Highlights and Trends, 18 May 2004, is available from http://doi.acm.org/10.1145/990657.990667 cheers Iza [EMAIL PROTECTED] 01/07/04 5:33 In an effort to not drown the list-serv with constant replies, let me use this single reply. Captioning of SMIL, Magpie or the like will always be a human reviewer test. There's no way an automated evaluator can test image presentation. Search engines can't do it and certainly a less costly program won't be able to. At least not at this point. Regrettably, the only thing automated evaluators can do is tell you where you have fouled up (sometimes) and where you need to check (sometimes). Like Joe Clark says, they can't tell you when you've done something right. The only thing that can tell you when you've done something correctly is through experience and testing. You'll be surprised at how easy it becomes once you learn the little tricks of the trade. Jesse, you might be interested in The Globe and Mail on June 16, 2004. I think that's Canada's national newspaper. There's an article about accessible web sites, namely about YouSearched.com. I hope this was of some help. Sincerely, Lee Roberts http://www.roserockdesign.com http://www.applepiecart.com -Original Message- From: ckimedia [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 30, 2004 9:56 AM To: [EMAIL PROTECTED] Subject: Re: [WSG] 508?? Hi, Thanks I wasn't aware my question had ominous tones. Nonetheless, humble voice I appreciate your suggestion. /humble voice On Wednesday, June 30, 2004, at 08:04 AM, Patrick Lauke wrote: ominous voiceComprehensive Accessibility Text/ominous voice, as the field is constantly evolving and changing. What you can get, though, is books covering the majority of the basis, and follow that up with good practice examples. They're out there, you just need to look in the right places (and frequent lists like the above featured WAI-IG, or forums such as www.accessifyforum.com for instance). * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help * * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help * * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] As Good As the Weakest Link
It is also important to use proper markup for lists (and every other element) to
ensure accessibility compliance, see WCAG checkpoint 3.5
http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-list-structure.
cheers
Iza
[EMAIL PROTECTED] 29/06/04 12:01
I believe its because, when you style it in CSS.
And make the LINKS, BLOCK ELEMENTS - without using ul's.
Without the stylesheet, the links will bunch up without any spaces or gaps.
So you use a ul and li's - just for the fact that it will be
backwards compatable with browsers which dont support CSS, and also its
just better formatted when you view your code... - thats my opinion...
:)
Ted Drake wrote:
ol gives your links the number 1, 2, 3, etc.
On this line, how do I change it to A, B, C, a, b, c, etc.
Ted
-Original Message-
From: ckimedia [mailto:[EMAIL PROTECTED]
Sent: Monday, June 28, 2004 4:10 PM
To: [EMAIL PROTECTED]
Subject: [WSG] As Good As the Weakest Link
Hi,
When styling a group of links one can simply change the display of the
a:link and a:visited state to display block, making a simply line of
links into a list. What is the advantage of using a ol for links as
opposed to the aforementioned, if any?
#navbar a:link, #navbar a:visited {
display: block;
color: #7e7e7e;
background-color: #ff;
border-bottom: solid 1px #00;
padding-bottom: 3px;
padding-top: 3px;
}
Complexity is good, complicated is bad.
*Paolo Soleri
Chris
*
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
*
*
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
*
*
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
*
*
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
*
Re: [WSG] Accessability testing
hi James, These articles might be of some help: A Review of Free, Online Accessibility Tools http://www.webaim.org/techniques/articles/freetools/ Do-It-Yourself Accessibility http://www.sitepoint.com/article/yourself-accessibility/2 cheers Iza [EMAIL PROTECTED] 24/06/04 15:37 Hi - does anyone still use Bobby these days? I ask because we really have only used: Cynthia* Says - Web Content Accessibility Report (http://www.contentquality.com/) On a site we are developing we pass all Checklist items up to and including Priority 3 Verification with Cynthia, however our client is testing using Bobby and Usablenet, stating these are the 'industry standard'. Is this the case? If not could anyone hit me with a nice list objective comparison? Thanks James -- James Cowperthwaite [EMAIL PROTECTED] * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help * * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
