CSS Problem!

Hello

Can anyone figure out how I can make my page work correctly -
http://www.bangor.ac.uk/~absc04/nwetp/dev_02.htm

The problem is that the CSS Dropdown list/menu is clashing with the
text in a separate <div> container.

HELP!!

Thanks
Chris

In article Chris wrote:

Hello

Can anyone figure out how I can make my page work correctly -
http://www.bangor.ac.uk/~absc04/nwetp/dev_02.htm

The problem is that the CSS Dropdown list/menu is clashing with the
text in a separate <div> container.

Well, I can't see that problem using Opera 7.22. I see problem in that
content starts only at 3/4 way down on page. Maybe you meaned that?

Please describe better what you want to archieve, and what is the
problem, and in what browser the latter.

HELP!!

I sure hope this is just some copy pasted half implemention, as it is not
at all as accessible as it says. It doen't pass A-level WGAG, doesn't
validate. Your CSS has lots of no good stuff.


--
Lauri Raittila <http://www.iki.fi/lr> <http://www.iki.fi/zwak/fonts>
Saapi lähettää meiliä, jos aihe ei liity ryhmään, tai on yksityinen
tjsp., mutta älä lähetä samaa viestiä meilitse ja ryhmään.

Chris wrote on 17 nov 2003 in comp.infosystems.www.authoring.stylesheets:

Can anyone figure out how I can make my page work correctly -
http://www.bangor.ac.uk/~absc04/nwetp/dev_02.htm

The problem is that the CSS Dropdown list/menu is clashing with the
text in a separate <div> container.

add a z-index to:

#menuList ul {
margin: 0px;
padding: 0px;
z-index:1000;
}


--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

Thanks, I will try this. My pages pass BOBBY Priority 1, 2 and 3 - and
work very well in Screen readers such as LYNX - they are accessible!!

C


"Evertjan." <exjxw.hannivoort (AT) interxnl (DOT) net> wrote

Chris wrote on 17 nov 2003 in comp.infosystems.www.authoring.stylesheets:

Can anyone figure out how I can make my page work correctly -
http://www.bangor.ac.uk/~absc04/nwetp/dev_02.htm

The problem is that the CSS Dropdown list/menu is clashing with the
text in a separate <div> container.


add a z-index to:

#menuList ul {
margin: 0px;
padding: 0px;
z-index:1000;
}

absc04 (AT) bangor (DOT) ac.uk (Chris) writes:

Can anyone figure out how I can make my page work correctly -
http://www.bangor.ac.uk/~absc04/nwetp/dev_02.htm

Doesn't validate. I assume this is something you've broken recently,
since it claims to and it's only a single error.

Thanks, I will try this. My pages pass BOBBY Priority 1, 2 and 3 - and
work very well in Screen readers such as LYNX - they are accessible!!

Lynx isn't a screen reader, it's a text browser. Unless there's a
screen reader by the same name that I'm not aware of.

Incidentally, passing the automatic Bobby checks doesn't guarantee
accessibility by a long way - though most of the checks will be steps
in the right direction if passed. By and large the page _is_
accessible, though.

http://www.cs.tut.fi/~jkorpela/www/acctools.html is worth reading on
browser stuff.

There's some more accessibility checking tools linked to from
http://www.dur.ac.uk/its/services/we...ibility/tools/
(though I need to update the advice on installing IE)

--
Chris

In article Chris wrote:

Thanks, I will try this. My pages pass BOBBY Priority 1, 2 and 3 - and
work very well in Screen readers such as LYNX - they are accessible!!

Can you find this text in that image without seeing image: "Community
University of North Wales"? (it's longer but I don't bother retype more,
as text is not available as text anywhere in
http://www.bangor.ac.uk/~absc04/nwetp/dev_02.htm). So you are hiding this
text from people not viewing images. That is against A-level. Bobby
doesn't spot this as it can't know that you are using background image in
CSS for content. Exept that there is spot where it states that "Is
content accessible whitout CSS" etc, that you have to answer yourself. If
you lie to Bobby, it can't tell you truth.

But they don't work on my browser if I disable images, or use narrow
window. They are invalid, even if there is valid XHTML logo on bottom.
Lynx is not screen reader. Accessibility is not only about blind, deaf or
otherwise disabled, but for everybody else too. Text in that image that
is not shown, is so small that practicaly no-one with high dpi screen is
able to read it. Good thing I had low res screen.

Bobby is just tool. It won't really do anything good, if you don't know
what it is and how to use it. It even includes serious flaws (google
back), as well as does WGAG (language markup etc.). You have pixel widths
in your CSS for font size. They might prevent people using high dpi to
read pages. You use fixed width, so I can't read your page. Opera SSR
doesn't find that image either, and it is only way to access net in many
devices. Links and lynx also misses information that is available in only
image mode. This fails bobbys subjective test.

Notice that this message looks like normal message, but is harder to
understand as sentences are not in logical order. No automatic too can
check that. (No, that was not problem with your site. Yes, real reason
for that was not demonstrating. )

--
Lauri Raittila <http://www.iki.fi/lr> <http://www.iki.fi/zwak/fonts>
Saapi lähettää meiliä, jos aihe ei liity ryhmään, tai on yksityinen
tjsp., mutta älä lähetä samaa viestiä meilitse ja ryhmään.

Hmmm - your site isnt perfect either at http://www.student.oulu.fi/~laurirai/

It validates just like mine pal - so whats your point?

And the CSS does what I want it to do - and it validates!

Nuff said


Lauri Raittila <lauri (AT) raittila (DOT) cjb.net> wrote

In article Chris wrote:
Hello

Can anyone figure out how I can make my page work correctly -
http://www.bangor.ac.uk/~absc04/nwetp/dev_02.htm

The problem is that the CSS Dropdown list/menu is clashing with the
text in a separate <div> container.

Well, I can't see that problem using Opera 7.22. I see problem in that
content starts only at 3/4 way down on page. Maybe you meaned that?

Please describe better what you want to archieve, and what is the
problem, and in what browser the latter.

HELP!!

I sure hope this is just some copy pasted half implemention, as it is not
at all as accessible as it says. It doen't pass A-level WGAG, doesn't
validate. Your CSS has lots of no good stuff.

In article Chris wrote:

Hmmm - your site isnt perfect either at http://www.student.oulu.fi/~laurirai/

True. And I don't say that it is. I'm constantly working on it, instead
of thinking it would be perfect. I have never seen webpage that I could
not find 25 lines of problems, and my own certainly aren't exeption.

But, it doesn't have any images with text in them, exept those stupid
Bobby, Valid HTML and Valid CSS buttons on
http://www.student.oulu.fi/~laurirai/tietoja.html
- must get rid of them, even if they have good alt texts.

It validates just like mine pal - so whats your point?

Yours didn't validate. Try it yourself.

And the CSS does what I want it to do - and it validates!

Gee, CSS validates. Too bad that it has nothing to do with accessibility.
In fact, incorrect CSS is about as likely to cause better than worse
accessibility.

Nuff said

Yes. No need to answer.

--
Lauri Raittila <http://www.iki.fi/lr> <http://www.iki.fi/zwak/fonts>
Saapi lähettää meiliä, jos aihe ei liity ryhmään, tai on yksityinen
tjsp., mutta älä lähetä samaa viestiä meilitse ja ryhmään.

Such an expert then! Okay, can you work out the dropdown menu problem
then? And answer my original question...over to you - EXPERT!


Lauri Raittila <lauri (AT) raittila (DOT) cjb.net> wrote

In article Chris wrote:
Hmmm - your site isnt perfect either at http://www.student.oulu.fi/~laurirai/

True. And I don't say that it is. I'm constantly working on it, instead
of thinking it would be perfect. I have never seen webpage that I could
not find 25 lines of problems, and my own certainly aren't exeption.

But, it doesn't have any images with text in them, exept those stupid
Bobby, Valid HTML and Valid CSS buttons on
http://www.student.oulu.fi/~laurirai/tietoja.html
- must get rid of them, even if they have good alt texts.

It validates just like mine pal - so whats your point?

Yours didn't validate. Try it yourself.

And the CSS does what I want it to do - and it validates!

Gee, CSS validates. Too bad that it has nothing to do with accessibility.
In fact, incorrect CSS is about as likely to cause better than worse
accessibility.

Nuff said

Yes. No need to answer.

Chris wrote:

Lauri Raittila <lauri (AT) raittila (DOT) cjb.net> wrote


In article Chris wrote:

Hmmm - your site isnt perfect either at http://www.student.oulu.fi/~laurirai/

True. And I don't say that it is. I'm constantly working on it, instead
of thinking it would be perfect. I have never seen webpage that I could
not find 25 lines of problems, and my own certainly aren't exeption.

But, it doesn't have any images with text in them, exept those stupid
Bobby, Valid HTML and Valid CSS buttons on
http://www.student.oulu.fi/~laurirai/tietoja.html
- must get rid of them, even if they have good alt texts.


It validates just like mine pal - so whats your point?

Yours didn't validate. Try it yourself.


And the CSS does what I want it to do - and it validates!

Gee, CSS validates. Too bad that it has nothing to do with accessibility.
In fact, incorrect CSS is about as likely to cause better than worse
accessibility.


Nuff said

Yes. No need to answer.

Such an expert then! Okay, can you work out the dropdown menu problem
then? And answer my original question...over to you - EXPERT!

Why should he solve CSS problems for an agressive and arrogant person
like you that obviously doesn't want to learn something? There are far
more rewarding problems to solve.


Matthias