Re: [WSG] internet explorer font names

[Michelle Rawlins]

I'm not Marvin. Wrong email.

On Mon, Jan 18, 2010 at 4:46 PM, Russ Weakley  wrote:

> Hi Marvin,
>
> I've placed two valid examples online for you to check (will stay online
> for next 10 days or so only):
>
> HTML: 
> CSS: 
>
> Can you test these valid files and see if IE8 lets you hear/see the
> headings that were causing you issues?
>
> Some notes on your files:
>
> -
> CSS issues
> -
>
> In both errors you have used:
>
> background-color: left;
>
> The value of "left" is not allowed (it also does not make sense as you are
> trying to apply a colour).
>
> The allowed values include "transparent", "inherit" and the various colour
> options. The options are:
>
> Option 1: Color keyword values
>
> Example: p { color: black; }
>
> CSS 2.1 color keyword values must only include: aqua, black, blue, fuchsia,
> gray, green, lime, maroon, navy, olive, purple, red, silver, teal, white,
> and yellow.
>
> More here:
> 
>
> Option 2: Hexidecimal values
>
> Hexadecimal values use a '#' immediately followed by either three or six
> hexadecimal characters. The three-digit RGB notation (#rgb) is converted
> into six-digit form (#rrggbb) by replicating digits, not by adding zeros.
>
> Example 1: p { color: #f00; } with three number value or
> Example 2: p { color: #ff; } with siz number value
>
> Option 3: Functional notation values
>
> Functional notation values use rgb(' followed by a comma-separated list of
> three numerical values (either three integer values or three percentage
> values) followed by ')'.
>
> Example 1: p { color: rgb(255,255,255); } with three numeric values
> Example 2: p { color: rgb(100%, 100%, 100%); } with three percentage values
>
> -
> HTML issues
> -
>
> Many of your issues are associated with the use of the BR element and can
> be resolved by replacing  with .
>
> The BR element is considered an "empty" or "self closing element". When
> using XHTML (you are using XHTML 1.0 Transitional) self closing elements
> should include a trailing slash: 
>
> You have also placed several BR elements inside a UL element. This is not
> allowed. The only items that can be placed inside a UL element are LI
> elements.
>
> More here:
> 
>
> You have the following paragraph with no closing paragraph element near the
> end of your document:
>
> 
>
> Finally, your email address markup includes a subject "hack":
>
> mailto:i...@joes.com.au?subject=joe's Website Query
>
> If nothing else, the subject needs to be correctly encoded so all spaces
> are replaced with "20%".
>
> Example:
>
> mailto:i...@joes.com.au?subject=joe's%20Website%20Query"
>
> Read more on this here:
> 
>
> Regardless, this solution for email subjects is a far from ideal.
>
> Read more on this here:
> 
> >
> <
> http://shadow2531.com/opera/testcases/mailto/modern_mailto_uri_scheme.html
> >
>
> Final notes:
>
> 1. There are a range of cases where you have used BR elements where they
> are probably not needed. The same could easily be achieved using CSS by
> applying additional padding on one of the vertically adjacent elements.
>
> 2. Similarly, you have used the HR element in several instances and this
> could also be achieved using CSS by applying padding and borders to
> vertically adjacent elements. Not essential, but worth considering.
>
> 3. There are several instances where you have used a DIV or PARAGRAPH with
> the single purpose of clearing other content. Again, this could easily have
> been achieved by applying the CLEAR property to one of the existing
> following elements.
>
> 4. Finally, in two instances, you have used the TARGET attribute within an
> ANCHOR element - target="_top". There have been many discussions on this
> about this on the WSG list in the past. Rather than get bogged down in this
> again, two simple points:
> - this is not ideal as it not valid for XHTML 1.0 Strict (even though it is
> acceptable in your case it is a good practice to move towards strict)
> - leave these out and let the user control their experience!
>
> Thanks
> Russ
>
>
> On 19/01/2010, at 10:04 AM, Marvin Hunkin wrote:
>
>  hi.
>> what do you mean vallidate the css and the pages.
>> did do that a while back and it vallidated all.
>>
>
>
>
> ***
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: memberh...@webstandardsgroup.org
> ***
>
>
 PR: wait...  I: wait...  L:
wait... LD:
wait...  I: wait... wait...  Rank:
wait...  Traffic: w

Re: [WSG] internet explorer font names

[Russ Weakley]

Hi Marvin,

I've placed two valid examples online for you to check (will stay  
online for next 10 days or so only):


HTML: 
CSS: 

Can you test these valid files and see if IE8 lets you hear/see the  
headings that were causing you issues?


Some notes on your files:

-
CSS issues
-

In both errors you have used:

background-color: left;

The value of "left" is not allowed (it also does not make sense as you  
are trying to apply a colour).


The allowed values include "transparent", "inherit" and the various  
colour options. The options are:


Option 1: Color keyword values

Example: p { color: black; }

CSS 2.1 color keyword values must only include: aqua, black, blue,  
fuchsia, gray, green, lime, maroon, navy, olive, purple, red, silver,  
teal, white, and yellow.


More here:


Option 2: Hexidecimal values

Hexadecimal values use a '#' immediately followed by either three or  
six hexadecimal characters. The three-digit RGB notation (#rgb) is  
converted into six-digit form (#rrggbb) by replicating digits, not by  
adding zeros.


Example 1: p { color: #f00; } with three number value or
Example 2: p { color: #ff; } with siz number value

Option 3: Functional notation values

Functional notation values use rgb(' followed by a comma-separated  
list of three numerical values (either three integer values or three  
percentage values) followed by ')'.


Example 1: p { color: rgb(255,255,255); } with three numeric values
Example 2: p { color: rgb(100%, 100%, 100%); } with three percentage  
values


-
HTML issues
-

Many of your issues are associated with the use of the BR element and  
can be resolved by replacing  with .


The BR element is considered an "empty" or "self closing element".  
When using XHTML (you are using XHTML 1.0 Transitional) self closing  
elements should include a trailing slash: 


You have also placed several BR elements inside a UL element. This is  
not allowed. The only items that can be placed inside a UL element are  
LI elements.


More here:


You have the following paragraph with no closing paragraph element  
near the end of your document:




Finally, your email address markup includes a subject "hack":

mailto:i...@joes.com.au?subject=joe's Website Query

If nothing else, the subject needs to be correctly encoded so all  
spaces are replaced with "20%".


Example:

mailto:i...@joes.com.au?subject=joe's%20Website%20Query"

Read more on this here:


Regardless, this solution for email subjects is a far from ideal.

Read more on this here:




Final notes:

1. There are a range of cases where you have used BR elements where  
they are probably not needed. The same could easily be achieved using  
CSS by applying additional padding on one of the vertically adjacent  
elements.


2. Similarly, you have used the HR element in several instances and  
this could also be achieved using CSS by applying padding and borders  
to vertically adjacent elements. Not essential, but worth considering.


3. There are several instances where you have used a DIV or PARAGRAPH  
with the single purpose of clearing other content. Again, this could  
easily have been achieved by applying the CLEAR property to one of the  
existing following elements.


4. Finally, in two instances, you have used the TARGET attribute  
within an ANCHOR element - target="_top". There have been many  
discussions on this about this on the WSG list in the past. Rather  
than get bogged down in this again, two simple points:
- this is not ideal as it not valid for XHTML 1.0 Strict (even though  
it is acceptable in your case it is a good practice to move towards  
strict)

- leave these out and let the user control their experience!

Thanks
Russ

On 19/01/2010, at 10:04 AM, Marvin Hunkin wrote:


hi.
what do you mean vallidate the css and the pages.
did do that a while back and it vallidated all.




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

Re: [WSG] internet explorer font names

[Doug Burt]

Hey Marvin,

RE: http://www.raulferrer.com/joe/html/

It's really important that you validate your site everytime you make any 
changes, any changes at all on your site.  This it to insure that you're giving 
the browser's a chance to read everything that's on your site properly and 
avoid issues like you're running into right now. Here's links to some basic 
validator's for you (although there are others out there that you can purchase 
if you wish) that will do a pretty good job insuring that your code is valid.

X/HTML Validation:  http://validator.w3.org/
CSS Validation:  http://jigsaw.w3.org/css-validator/
Link Checker: http://validator.w3.org/checklink

Once you have all your errors repaired and working properly validated, I bet 
your site work's great for you. But at least that way we have a chance to try 
and help you, without having to go through your site and double check to make 
sure you haven't made basic mistakes first. Good luck getting the code cleaned 
up and then we can go from there with you.

Cheers,
DougB




> Marvin Hunkin wrote:
>> hi.
>> what do you mean vallidate the css and the pages.
>> did do that a while back and it vallidated all.


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

Re: [WSG] internet explorer font names

[David Laakso]

Marvin Hunkin wrote:

hi.
what do you mean vallidate the css and the pages.
did do that a while back and it vallidated all.
  




Please include url to your page in question each time you write.

RE: 


I suspect you have made some markup and CSS changes since the last time 
you visited the w3c validation service :-) .


There are currently 43 markup errors on your "home" page.


And there are currently 2 CSS errors.




marvin. 





  



Best,
~d

--
desktop
http://chelseacreekstudio.com/
mobile
http://chelseacreekstudio.mobi/



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

[WSG] internet explorer font names

[Marvin Hunkin]

hi.
what do you mean vallidate the css and the pages.
did do that a while back and it vallidated all.
now in internet explorer 7, it would read all the names on all elements.
it does not with internet explorer 8.
so how to fix this.
maybe can test in ie 7 and ie8.
and see if it is reading the font names.
well for the body.
thought it would read the other elements as well.
unless i need to put the font names for all elements.
please help me out.
or might just have to roll back to ie7, which i do not really want to.
so wonder if it is a internet explorer issue.
and trying to find the contact form for tech site on the microsoft site with 
a screen reader is a real pain.
marvin. 




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

[WSG] internet explorer font names

[Marvin Hunkin]

hi.
well here's the site.
how ot fix this.
still not reading the names in internet explorer 8
marvin. 




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***