Layout problem/tag error

[mo]

Hi!

I've been fighting a problem for many hours now but I just can't see what's breaking the layout. Maybe some of the more experienced S9Y designers can help?

Blog address: http://www.eric-scheibler.de/blog/

Thanks for all advice!

[yellowled]

I've been fighting a problem for many hours now but I just can't see what's breaking the layout.

Apart from a lot of <br /> elements inside <ul>s (not valid), there seems to be a closing </div> too many. It often helps to simply run the w3c validator across the site. I'd recommend to fix the ul/br issue first since that will remove most of the current error messages.

YL

[mo]

Thanks. I have removed the inserted linebreaks now. I know about the validator, but in this case I just can't find the bug.

[yellowled]

I know about the validator, but in this case I just can't find the bug.

I see this is a modified BP in the sense that you put it in a seperate folder (/templates/eric/). Did you make any modifications to the .tpl files? (The entries.tpl would be a likely candidate for this particular error.)

If not, the error has to be in an entry text (unlikely since all entries look good in single entry view) or a sidebar plugin (also unlikely since you only use the standard ones and no HTML nugget or something).

Patience, we'll find it

YL

[mo]

Yes the error was introduced manually. The template has been adapted by a blind user who didn't notice the damaged layout. The default template is okay for usage by the blind, but not too good and can use several changes to make it more useable for screen readers.

[yellowled]

The default template is okay for usage by the blind, but not too good and can use several changes to make it more useable for screen readers.

After a quick glance at the code, I assume you're referring to WAI-ARIA landmark roles. I'm aware of those now (using them in my own blog template), but we weren't back then when be BP was still under active development.

Also, since WAI-ARIA is not part of HTML4 or XHTML, those landmark roles should probably be assigned using Javascript in order to keep the code valid.

YL