Re: [WSG] Quirks mode vs Standards mode
Dear Sara, When a document begins with an ?xml version=1.0 encoding=utf-8? declaration. IE 6 for Windows doen't see the Doctype, so it lapses into quirks mode. Therefore I would suggest you not to use it. Kind regards, John S. Britsios Accessibility SEO Consultant, Usability Specialist Trainer Webnauts Net Koblenzer Str. 37a D-33613 Bielefeld Germany, Europe Telephone: (+49) 0521 - 305 10 20 Cellular: (+49) 0163 - 202 55 61 Email: [EMAIL PROTECTED] Homepage: http://www.webnauts.net Discussion Forums: http://www.webnauts.net/phpBB2/ User Interface Usability Checklist: http://www.webnauts.net/user-interface-usability-checklist.html Designing with Accessibility, Search Engines Usability in Mind - Original Message - From: Sarah Peeke (XERT) [EMAIL PROTECTED] To: WSG wsg@webstandardsgroup.org Sent: Friday, April 15, 2005 6:23 AM Subject: [WSG] Quirks mode vs Standards mode Hi all, I am interested in people's thoughts about using quirks mode (ie adding ?xml version=1.0 encoding=utf-8? before the doctype) vs standards mode. What do most people use? Which option requires *less* css hacks, and is *more* standards compliant across the widest range of modern browsers? Appreciate any feedback. Thanks Sarah -- XERT Communications email: [EMAIL PROTECTED] office: +61 2 4782 3104 mobile: 0438 017 416 http://www.xert.com.au/ web development : digital imaging : dvd production ** 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] Re: Object Mp3 into FF
Dear Helmut, You have two errors. Line 2: A quoted string cannot be immediately followed by text. It must be followed by a space or the end of the tag. Line 7: The EMBED element cannot be used here. It is not contained in an element that allows its use. Regards, John S. Britsios Accessibility SEO Consultant, Usability Specialist Trainer Webnauts Net Koblenzer Str. 37a D-33613 Bielefeld Germany, EU Telephone: (+49) 0521 - 305 10 20 Cellular: (+49) 0163 - 202 55 61 Email: [EMAIL PROTECTED] Homepage: http://www.webnauts.net Discussion Forums: http://www.webnauts.net/phpBB2/ Designing with Accessibility, Search Engines Usability in Mind - Original Message - From: Helmut Granda [EMAIL PROTECTED] Cc: wsg@webstandardsgroup.org Sent: Wednesday, March 09, 2005 11:16 PM Subject: [WSG] Re: Object Mp3 into FF I dont know if it is ok to post this kind of question here. I am trying to play a simple Mp3 file in the server, it works in IE, and I have read that if something works on IE but not in other browsers it is most likely because it is not writen properly. I have tested it extensibly in my machine and it is working. I have used the deprecated embed tag and the object tag, both work on my computer and on IE on the server, but not on FF. Could some one take a look and help me find where I am making the mistake? Web references are good too. I have been searching for nearly 3 hours in different sites but none that I have found cover mp3, I even found a way around to embed Media Player in FF. Here is my code: OBJECT CLASSID=clsid:02BF25D5-8C17-4B23-BC80-D3488ABDDC6B WIDTH=144HEIGHT=16 CODEBASE=http://www.apple.com/qtactivex/qtplugin.cab; PARAM name=SRC VALUE=MP3%20File.mp3 PARAM name=AUTOPLAY VALUE=true PARAM name=CONTROLLER VALUE=true EMBED SRC=MP3%20File.mp3 WIDTH=144 HEIGHT=16 AUTOPLAY=true CONTROLLER=true PLUGINSPAGE=http://www.apple.com/quicktime/download/; /EMBED /OBJECT TIA, Helmut // I apologize for stealing the previews thread. My mistake. ** 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] WAI checkpoint 13.1 Help
Zachary,
The only problems I see on you page is, that you are using redudant tabindex
tags and letters instead of numbers for you accesskeys.
About http://webxact.watchfire.com/ no need to worry!
That is the only tool of all I know and that I do not use.
Stick for automatic evaluations with Cynthia Says, WAVE and with some care
with Bobby.
Off topic: What are all those Meta Tags for?
Regards,
John S. Britsios
http://www.webnauts.net
- Original Message -
From: Zachary Hopkins [EMAIL PROTECTED]
To: Web Standards Group wsg@webstandardsgroup.org
Sent: Sunday, February 06, 2005 3:09 AM
Subject: [WSG] WAI checkpoint 13.1 Help
On my website, http://www.hopkinsprogramming.net/, I use CSS background
images instead of the img tag. So, I have hyper linked
background-images, if that makes sense, and they have no actual link
text. Watchfire's WebXACT (http://webxact.watchfire.com/) accessibility
validator is giving me an error with WAI Priority 2, Checkpoint 13.1. I
understand why I am getting the error, but I am not sure of the best way
to correct it, as I do not want text covering up the images.
Any suggestions?
= Sample Code of my link =
a href=http://place.com/; title=Link Title
style=display:block;width:80px;height:15px;background-image:url('img.png');
/a
==
-- Zachary Hopkins
--
The best way to predict the future is to invent it.
[EMAIL PROTECTED]
http://www.hopkinsprogramming.net
**
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] WAI checkpoint 13.1 Help
Zachary,
Me again. I also do not see your reason using a text-only version. It is
absolutely redudant! You did a too good work, to hang on your page a
text-version.
Also you are using CDATA sections which are not recommended due to poor
browser support (even some newer browsers fail to properly support it) and
due to other complications.
Your new window does not open on your privacy policy page to send you an
email, when JavaScript is disabled.
Have a look here to see how to solve this:
http://www.webnauts.net/new_window.html
Regards,
John S. Britsios
http://www.webnauts.net
- Original Message -
From: Zachary Hopkins [EMAIL PROTECTED]
To: Web Standards Group wsg@webstandardsgroup.org
Sent: Sunday, February 06, 2005 3:09 AM
Subject: [WSG] WAI checkpoint 13.1 Help
On my website, http://www.hopkinsprogramming.net/, I use CSS background
images instead of the img tag. So, I have hyper linked
background-images, if that makes sense, and they have no actual link
text. Watchfire's WebXACT (http://webxact.watchfire.com/) accessibility
validator is giving me an error with WAI Priority 2, Checkpoint 13.1. I
understand why I am getting the error, but I am not sure of the best way
to correct it, as I do not want text covering up the images.
Any suggestions?
= Sample Code of my link =
a href=http://place.com/; title=Link Title
style=display:block;width:80px;height:15px;background-image:url('img.png');
/a
==
-- Zachary Hopkins
--
The best way to predict the future is to invent it.
[EMAIL PROTECTED]
http://www.hopkinsprogramming.net
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
[WSG] Webnauts Net Accessibility, Usability and SEO forums online
Dear WSG members!Sincea few daysnow, our Accessibility, Usability and SEO forums are online.Therefore we would kindly like to inivite you to drop by, and we hope you will support us with your membership/contribution, promoting Accessibility, Usability and Search Engines issues.The forums may be found here: http://www.webnauts.net/phpBB2/index.phpFor the Webnauts Net TeamMy kindest regards,John S. Britsioshttp://www.webnauts.net
Re: [WSG] WAI checkpoint 13.1 Help
Zachary,
About Tabindex Tags read here:
http://www.wats.ca/articles/keyboardusageandtabindex/62
About Accesskeys problems using letters read here:
http://www.wats.ca/resources/accesskeysandkeystrokes/38
Sure there are some problems using numbers too, but not as with letters:
http://www.wats.ca/articles/accesskeyconflicts/37
Even though I still use accesskeys on my site.
About your Meta Tags, you just spoil your SEO. From all that stuff you only
need the title, description, keywords and the robots.
Besides, make your JavaScript and CSS external.
Kind regards,
John S. Britsios
http://www.webnauts.net
- Original Message -
From: Zachary Hopkins [EMAIL PROTECTED]
To: wsg@webstandardsgroup.org
Sent: Monday, February 07, 2005 10:55 PM
Subject: Re: [WSG] WAI checkpoint 13.1 Help
- I got the link text figured out.It just didn't link my hyperlinks w/
background images not having any link text.
- Redundant tabindex tags? (O.o)?
- What's wrong with letters?
- The meta tags hold keywords, page descriptions, author info, page
rating, time between search bot re-indexing, etc, etc
--Zachary
John Britsios wrote:
Zachary,
The only problems I see on you page is, that you are using redudant
tabindex
tags and letters instead of numbers for you accesskeys.
About http://webxact.watchfire.com/ no need to worry!
That is the only tool of all I know and that I do not use.
Stick for automatic evaluations with Cynthia Says, WAVE and with some
care
with Bobby.
Off topic: What are all those Meta Tags for?
Regards,
John S. Britsios
http://www.webnauts.net
- Original Message -
From: Zachary Hopkins [EMAIL PROTECTED]
To: Web Standards Group wsg@webstandardsgroup.org
Sent: Sunday, February 06, 2005 3:09 AM
Subject: [WSG] WAI checkpoint 13.1 Help
On my website, http://www.hopkinsprogramming.net/, I use CSS background
images instead of the img tag. So, I have hyper linked
background-images, if that makes sense, and they have no actual link
text. Watchfire's WebXACT (http://webxact.watchfire.com/) accessibility
validator is giving me an error with WAI Priority 2, Checkpoint 13.1. I
understand why I am getting the error, but I am not sure of the best way
to correct it, as I do not want text covering up the images.
Any suggestions?
= Sample Code of my link =
a href=http://place.com/; title=Link Title
style=display:block;width:80px;height:15px;background-image:url('img.png')
;
/a
==
-- Zachary Hopkins
--
The best way to predict the future is to invent it.
[EMAIL PROTECTED]
http://www.hopkinsprogramming.net
**
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 best way to predict the future is to invent it.
[EMAIL PROTECTED]
http://www.hopkinsprogramming.net
**
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] WAI checkpoint 13.1 Help
Zachary,
You are right. As I wrote in my previous mail, I use accesskeys. And mainly
for the reason you mentioned.
PDA, Mobile, etc devices. But I use numbers for accesskeys.
Kind regards,
John S. Britsios
http://www.webnauts.net
- Original Message -
From: Zachary Hopkins [EMAIL PROTECTED]
To: wsg@webstandardsgroup.org
Sent: Monday, February 07, 2005 11:02 PM
Subject: Re: [WSG] WAI checkpoint 13.1 Help
- Redundancy is key. I want no one left out, whether they have the
latest and greatest, oldest and moldiest, cell phone, PDA, whatever!
- CDATA is bad? How does it degrade?
- The contact links have been fixed to meet Priority 1 checkpoint 6.3
and Priority 2 checkpoint 10.1.
--Zachary
John Britsios wrote:
Zachary,
Me again. I also do not see your reason using a text-only version. It is
absolutely redudant! You did a too good work, to hang on your page a
text-version.
Also you are using CDATA sections which are not recommended due to poor
browser support (even some newer browsers fail to properly support it)
and
due to other complications.
Your new window does not open on your privacy policy page to send you an
email, when JavaScript is disabled.
Have a look here to see how to solve this:
http://www.webnauts.net/new_window.html
Regards,
John S. Britsios
http://www.webnauts.net
- Original Message -
From: Zachary Hopkins [EMAIL PROTECTED]
To: Web Standards Group wsg@webstandardsgroup.org
Sent: Sunday, February 06, 2005 3:09 AM
Subject: [WSG] WAI checkpoint 13.1 Help
On my website, http://www.hopkinsprogramming.net/, I use CSS background
images instead of the img tag. So, I have hyper linked
background-images, if that makes sense, and they have no actual link
text. Watchfire's WebXACT (http://webxact.watchfire.com/) accessibility
validator is giving me an error with WAI Priority 2, Checkpoint 13.1. I
understand why I am getting the error, but I am not sure of the best way
to correct it, as I do not want text covering up the images.
Any suggestions?
= Sample Code of my link =
a href=http://place.com/; title=Link Title
style=display:block;width:80px;height:15px;background-image:url('img.png')
;
/a
==
-- Zachary Hopkins
--
The best way to predict the future is to invent it.
[EMAIL PROTECTED]
http://www.hopkinsprogramming.net
**
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 best way to predict the future is to invent it.
[EMAIL PROTECTED]
http://www.hopkinsprogramming.net
**
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] Hello fellow Web Standards people!
Zachary welcome at WSG! My suggestions: To your page MarkUp: 1. HTML 4.01 and XHTML require the legend element in fieldsets. Use this element immediately after the fieldset start tag. To your page accessibility: 1. The input element (when type=image) requires the alt attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear. However, use alt= when appropriate, such as when images are intended to format a page (such as spacer images). [Section 1194.22 (a)] 2. The input element (when type=image) requires the alt attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear. However, use alt= when appropriate, such as when images are intended to format a page (such as spacer images). [P1, 1.1] John S. Britsios - Original Message - From: Zachary Hopkins [EMAIL PROTECTED] To: Web Standards Group wsg@webstandardsgroup.org Sent: Saturday, February 05, 2005 4:56 PM Subject: [WSG] Hello fellow Web Standards people! Hello! I've just recently joined the WSG to get some tips, and I just wanted to say hello and introduce myself. My name is Zachary Hopkins, I'm 17 years old and I've been working with XHTML, CSS, and accessible web standards such as WAI and 508 for about 6 months now, and I really like them! You can check my website out at http://www.hopkinsprogramming.net/. I'm doing my best to make sure that it is an accessible and standards based website. I welcome any comments or suggestions, as I love to learn about new things and new ways to do them. I have been trying to test how my site looks on Mac and *nix based systems, so if any of you have a free moment, perhaps you could open up my site in Camino, Konqueror or Safari and let me know how it looks? Thank you! --Zachary Hopkins -- The best way to predict the future is to invent it. [EMAIL PROTECTED] http://www.hopkinsprogramming.net ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Web site review please
Hi Web Standards Advocate. I would appreciate if you would review my web site, giving me some advices, critiques or comments to improve. Please see here: http://www.webnauts.net/ Notice: I am aware there is a minor problem with the "Jump to Navigation" link in Opera, which I am going to fix in the next days. By the way, thank you allin advance for your kind support. Kind regards, John S. BritsiosPrincipal Web Accessibility Consultant,Usability Specialist Trainerhttp://www.webnauts.net
Re: [WSG] Web site review please
Dear David,
Thanks for you kind critique/comment. Though I do not understand your point.
So far I am informed, accessible and usable web sites should have fonts with
a minimum
size equal to12px, and that they should be resizeable.
I am using 0.8em, which is resizeable, and that is equal, for example in IE
with 12,8 px.
Can you please be more specific? Am I getting something wrong here?
And at last, I have not claimed here that I am perfect, while if I did so, I
would not need to
ask for a review here, or elsewhere...
Thanks and regards,
John
- Original Message -
From: David Laakso [EMAIL PROTECTED]
To: wsg@webstandardsgroup.org
Sent: Tuesday, January 25, 2005 1:18 PM
Subject: Re: [WSG] Web site review please
On Tue, 25 Jan 2005 11:04:34 +0100, John Britsios [EMAIL PROTECTED]
wrote:
I would appreciate if you would review my web site, giving me some
advices, critiques or comments to improve.
Please see here: http://www.webnauts.net/
...
It seems peculiar to me, at least, that a -- Principal Web Accessibility
Consultant,
Usability Specialist Trainer -- takes the liberty of reducing my
default font setting by approximately 20%.
Your CSS reads:
body {width:
100.01%;color:#000;background:#FDFCFC;font-size:.8em;margin:0em;padding:0em;
font-family:arial,verdana,helvetica,tahoma,sans-serif}
Would you buy, instead?:
body {/*width:
100.01%;*/color:#000;background:#FDFCFC;font-size:/*.8em*/100.01%;margin:0/*
em*/;padding:0/*em*/;font-family:arial,verdana,helvetica,tahoma,sans-serif}
John S. Britsios
Principal Web Accessibility Consultant,
Usability Specialist Trainer
http://www.webnauts.net
David
--
http://www.dlaakso.com/
**
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
**
[WSG] Happy New Year!
Dear All! Here I would like to wish you all, your families, friends and associates a very Happy, Healthy and Successful New Year. Besides, I wish that everyone will go on supporting the World Wide Web Initiative, in making the Web accessible and usable to all! At last I wish, that all of us would will give our best effort to help the victims and their families who are in need, due to the disaster in the countries around the Indian Ocean. My kindest regards, John S. Britsios Principal Web Accessibility Consultant, Usability Specialist Trainer http://www.webnauts.net ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Bobby does not approve me
Hi everyone! Some of my pages do not validate with Bobby, and I can not see the errors. Could you please have a look and give me a hand? 1. Page: http://www.webnauts.net/accessibility2.html Bobby: http://bobby.watchfire.com/bobby/bobbyServlet?URL=""> 2. Page: http://www.webnauts.net/accessibility_seminar.html Bobby: http://bobby.watchfire.com/bobby/bobbyServlet?URL=""> 3. Page: http://www.webnauts.net/usability_seminar.html Bobby: http://bobby.watchfire.com/bobby/bobbyServlet?URL=""> 4. Page: http://www.webnauts.net/technical Bobby: http://bobby.watchfire.com/bobby/bobbyServlet?URL=""> 5.Page: http://www.webnauts.net/curriculum.html Bobby: http://bobby.watchfire.com/bobby/bobbyServlet?URL=""> 6. Page: http://www.webnauts.net/check.html Bobby: http://bobby.watchfire.com/bobby/bobbyServlet?URL=""> Thank you all in advance. John S. BritsiosPrincipal Web Accessibility Consultant,Usability Specialist TrainerWebnauts NetThielenstr. 2D-33602 BielefeldGermanyHome: http://www.webnauts.netCV: http://www.webnauts.netForum: http://forum.webnauts.net
[WSG] Tabindex tags not necessary here?
Dear all, I have a question: Doesn't my web site pages here http://www.webnauts.net have a logical navigation structure,thereforeI do need to use the "Tabindex" tags?I ask, because someone advised me against the use of tab indexing - using it only if the natural ordering is misleading. Thanks in advance for your kind support. John S. BritsiosPrincipal Web Accessibility Consultant,Usability Specialist TrainerWebnauts NetThielenstr. 2D-33602 BielefeldGermanyHome: http://www.webnauts.netForum: http://forum.webnauts.net
