![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Meaning I'm going to need to learn more about CSS....which I knew was in my future. <smile> Would you happen to know if this is something I can do in DW4, or will I need a separate CSS editor? |
#12
| |||
| |||
|
|
I use TopStyle Lite (http://www.bradsoft.com/topstyle/), a free version of which ships with DW (or at least with the suite). If it's not on your CD, you can d/l from the site - I hadn't realized, but it's up to v 3.1. |
#13
| |||
| |||
|
|
I've had W3C AAA pages fail with Bobby and vice versa. Realize that markup validation and accessibility validation can be mutually exclusive. Good, well formed markup usually makes the page easier to make accessible, but it isn't necessarily a direct correlation. -Darrel |
#14
| ||||||
| ||||||
|
|
If you can't make a page accessible, construct an alternate accessible version. |
|
If style sheets are ignored or unsupported, are pages still readable and usable? |
|
If this is a data table (not used for layout only), identify headers for the table rows and columns. (1 instance) Line 12 |
|
If you use color to convey information, make sure the information is also represented another way. (10 instances) Lines 16, 17, 25, 32, 42, 43, 51, 56, 64, 68 |
|
If an image conveys important information beyond what is in its alternative text, provide an extended description. (6 instances) Lines 16, 25, 51, 56, 64, 68 |
|
If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (1 instance) Line 12 |
#15
| |||
| |||
|
|
I just ran one of my websites (www.laneonbass.com) through http://validator.w3.org/ and got two errors: ----------------- 1. Line 1, column 61: invalid formal public identifier "-//w3c//dtd html 4.01 transitional//en": invalid public text class ...type html public "-//w3c//dtd html 4.01 transitional//en" 2. Line 10, column 37: there is no attribute "HEIGHT" table width="775" border="0" height="435" cellspacing="10" align="center" You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. ------------------------ So...my first question is :What type of document is this? I am *not* a hand coder to any extent, and honestly don't know how to tell what type of document this is. Is there an explanation that even non-technical types can understand? Second question: How do I solve error two? If I get the doc type correct, will it go away on its own? As for accesibility issues, isn't there a site that validates accessibility of pages? Or would someone here care to offer their feedback? As always, many thanks to everyone for the assistance and feedback. Lane |
#16
| |||
| |||
|
|
snip US Mornin' Dude UK Good afternoon Old Chap. BOBBY 508 A lot of ifs If you can't make a page accessible, construct an alternate accessible version. N/A If style sheets are ignored or unsupported, are pages still readable and usable? I can read it If this is a data table (not used for layout only), identify headers for the table rows and columns. (1 instance) Line 12 Not a data table so N/A If you use color to convey information, make sure the information is also represented another way. (10 instances) Lines 16, 17, 25, 32, 42, 43, 51, 56, 64, 68 I think Darrel gave the solution to this but I will stick my neck out here. You are not actually saying "click on the green button to continue" so, if you use css for formatting, it should remove the problem and Bobby should be OK with it. (too many shoulds) If an image conveys important information beyond what is in its alternative text, provide an extended description. (6 instances) Lines 16, 25, 51, 56, 64, 68 Some of the above are not even images. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (1 instance) Line 12 N/A Please note that N/A is short for "not applicable in my very humble opinion". This should validate for Section 508 which should be OK for now. Next step - WAI WCAG AAA If you want to hang on for a day or two I can send you my interpretation of the page, using css, for you have a look at. ( then we get the experts to add the finishing touches) Off to see the Osteopath now. Pay a guy £50 an hour to beat me up. CUL Terry |
#17
| |||
| |||
|
|
LANE! You've got to be kidding. Small world! Remember me? |
#18
| |||
| |||
|
#19
| |||
| |||
|
|
Follow-up: Terry, I finally figured out (I think!) how to implement Darrel's suggestion to use CSS to set color (Thanks Darrel!)...not only for the text in red, but also for the quotes used throuhgout the site. It seems to have solved many of the errors that Bobby reported. This should make it a bit simpler. Still not sure what to do about the other errors. Again, thanks for taking time to evaluate the site. www.laneonbass.com How'd the appointment go? Lane |
#20
| |||
| |||
|
|
I just ran one of my websites (www.laneonbass.com) through http://validator.w3.org/ and got two errors: |
![]() |
| Thread Tools | |
| Display Modes | |
| |