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
**
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
**
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
**
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
**
[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
begin:vcard
fn:Zachary Hopkins
n:Hopkins;Zachary
org:Hopkins Programming
adr:;;United States
email;internet:[EMAIL PROTECTED]
title:Owner
x-mozilla-html:TRUE
url:http://www.hopkinsprogramming.net/
version:2.1
end:vcard
Re: [WSG] WAI checkpoint 13.1 Help
The links on your page where you use image replacement do not contain
any text, this is what is causing the errors. Basically what the report
says is that you can't use the same link text with differing href's...
in your case the link text is an empty string.
Remove empty lines from your code so you can follow the line numbers as
reported, and it should all make sense.
You need to look at image replacement techniques.
see: http://www.google.com/search?q=css%20image%20replacement
Terrence Wood.
Zachary Hopkins wrote:
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
**
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
It seems that adding in hidden text would be the best way.
Thanks!
--Zachary
Terrence Wood wrote:
The links on your page where you use image replacement do not contain
any text, this is what is causing the errors. Basically what the
report says is that you can't use the same link text with differing
href's... in your case the link text is an empty string.
Remove empty lines from your code so you can follow the line numbers
as reported, and it should all make sense.
You need to look at image replacement techniques.
see: http://www.google.com/search?q=css%20image%20replacement
Terrence Wood.
Zachary Hopkins wrote:
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
**
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
begin:vcard
fn:Zachary Hopkins
n:Hopkins;Zachary
org:Hopkins Programming
adr:;;United States
email;internet:[EMAIL PROTECTED]
title:Owner
x-mozilla-html:TRUE
url:http://www.hopkinsprogramming.net/
version:2.1
end:vcard
