Re: [WSG] site check in IE6 - c7designs.com
I know everyone will disagree with me :) I think it is better to put each pair of labels and textfields in a div. I know, it's extra mark up without any actual meaning, but you can't guarantee that your presentation (CSS) will work, and without the CSS and the divs, those elements are all inline and look a right mess. Kat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Clearing floats with overflow
I seem to be almost a year behind on this (11 months at least), but I just spotted it this morning in an ALA article. Can someone please please please explain it to me (in very simple terms)? If children of a container are floated, as far as I understand, they are then taken out of normal flow and the container collapses. Now, if overflow:hidden is applied to the parent container, then the height of the parent container is adjusted to include the heights of the floated children. http://www.w3.org/TR/2004/CR-CSS21-20040225/visudet.html#q22 This is where I get lost: I understand overflow to describe what should happen to children/content that 'overflows' the parent container. Since the floats are out of normal flow, how come overflow applies at all? Have I misunderstood the basic concept of floats or overflow or something else altogether? Are the children now back into normal flow or has the container been taken out of normal flow or what is going on? Confusedly, Kat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] No. abbreviation glyph
Andrew Cunningham wrote: Christian Montoya wrote: Ben Buchanan wrote: > Personally I think glyphs/entities in HTML should have been tags with > alt or title attributes. I assume when Ben wrote "glyph" he meant "character". A glyph is a visual representation of character that can vary between languages, geographic regions and typographic traditions, etc. And browsers, the character comes out very differently between IE 6 and Firefox 1.5 If you used the Unicode character , this is a character (part of the data or text) and not an abbreviation. BUT, at the same time, it is. . - _ ^ & are not abbreviations, I accept that. But No. is an abbreviation for number. It's just that there is a special character/glyph for that particular abbreviation. So do you mark it up as an abbreviation or not, or is the abbreviation implied in the use of that character? Kat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Art and accessibility
Jermayn Parker wrote: I read this discussion and I think it's strange. The universitys and tafes are usually taught by lecturers who have no formal understanding or knowledge themselves about web standards etc. But there are many practitioners out there doing fantastic things without formal knowledge either. Formal here I have taken to mean tertiary courses in the area. Formal knowledge in a realm so new isn't that important - yet. It also is hard for them to change the content of their units as they usually get revised every 5 odd years, also the lecturers are not paid for study and revising the units, they only get paid for class time. So why should they do extra unpaid work for ungrateful students??? In the realm of science, things are updated all the time. This is the norm and is expected. Science university courses are frequently re-written. It is also the norm that lecturers are expected to revise and update the course as when needed. It's part of their job. University educators are expected to do research as well, as well as keep up their professional habits of continually updating themselves. So they *should* be up to date. If they are not, then perhaps it is us who has somehow failed them in helping to update them. We need to find out how we have failed them, and how we can best help them to stay at the fore-front. But the strangest thing of all is this: In this debate, we totally write off current practitioners who are in the field today, as though they were a lost cause. Can you imagine if the medical or law fraternity made a decision like this? We may still have trepanning! Or doctors recommending smoking for relaxation ;) As web developers, information architects and designers, we should have the skills amongst ourselves to be able to profile who it is we want to target, how to best target them, and bring them into the standards fold. This is hard for us to do on an individual level. What we lack is a professional body that is strong to enough to want to promote professional habits of up-skilling to all Web Industry Professionals, through various methods. I have a lot of hope that WIPA will fill this void. btw incase your wondering im not a lecturer - lol... I have raised this issue with my previous lecturers and they informed me of these government standards on lecturers [EMAIL PROTECTED] 25/01/2007 10:02:12 am >>> Doesn't the ACS (In Australia) claim to be our peek standards body? (Also assuming that Web Dev comes under the "Computing" banner). Wouldn't they (or somebody like them) be the ones to issue a certificate? (One look at their web site will tell you how seriously they take web standards.) The attitude seems to be that web development isn't real IT. The funny thing is that people in the webby area also seem to feel this way. I brought this up on another list and quite a few were adamant that an IT professional was one that hooked up networks. To me, an IT person is someone who can work with either information or computer systems, from either the technical or human standpoint. That would then include web developers, information architects, usability consultants, and many other titles of those who work with the web. WIPA should take this up with the ACS and get some recognition! :) Kat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Title attributes
Barney Carroll wrote: I was recently told by an automated accessibility test that my navigation was not up to scratch because it simply consisted of a plain ul at its highest level. It penalised me for not having a preceding heading to give some kind of indication of what the ul was about. Now I've never seen a navigation marked 'navigation', and even in the most of eccentric sites I've always been correct in the assumption that the first list of links with category denominations is some kind of navigation tool. I'd like to know what people think about that first of all - does anybody give headings to their navigation? Your post really reminded me of an older post that talked about this: http://www.usability.com.au/resources/ozewai2005/ May I asked which automated accessibility test? Hope that helps. Kat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] AIMIA finalists
Gday, So is anybody on this list one of the finalists? http://www.aimia.com.au/i-cms?page=2649 I notice a very interesting phenomenon: CSS is widely used, but validation is not considered important, for either CSS or HTML, and I don't think accessibility has been given a high priority either amongst these pages. Does anyone know why? Why have many of them made similar choices? Kat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Legitimate uses of and
2) Language usage such as Latin as this is a long standing convention in print and must be retained (thus not styled via CSS). Example: Lorem ispum I actually come across this situation from time to time and I have ummed and ahhed over what the best thing to do is. My final answer is to place it in spans, such as lang="latin">Echium plantagineum because: 1. The span offers flexibility: I have air-head moments where I decide these things should be italic, and bold, and in a different font, and then I decide the background should be a different colour. I can never predict what sort of air-head moments I have from year to year, and CSS allows me to cover for these moments quite easily. So I can change them to these stupid settings and then quickly change them back again :) 2. The web is essentially about semantic text. The audience reading your pages may not necessarily be human, and you need to open up your data to be available to your audience. Placing these sorts of semantic data in your code opens it up. The web is not about visual presentation, but about data. This is a really scary but powerful concept, that I believe will become even more important in the years to come. 3. All in code is evaluated by Google (a non-human audience member), and that includes the class name of the span. Your quality rating goes up, and SEOs could say more, but I believe also your listing for 'species Echium plantagineum' goes up because of the inclusion of the word 'species':) So my argument is if you find you need to present it visually different from surrounding text, ask yourself why. Why is this special, and then mark it up with spans using that speciality. Kat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] [OT] Web Standards as an Honours Project
Gday, I'm sorry this is a bit off topic! I am looking to do honours next year in Comp. & Inf. Science and I was wondering if anyone had any ideas about any honours topics involving web standards? Kat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] The Decline of Print Styles
I suspect the best way to create serious (from a design-for-print standpoint) web-to-print systems is to install a php-based pdf generator, because at the end of the day no matter how sophisticated web technologies get, printing from within the browser is always going to leave a world's worth of factors out of your control. I believe Adobe have a very nice system based on this principle. I thought part of the whole web standards thing was joyously embracing the lack of control, and creating styles, for various formats (screen, print, etc) with the fore-knowledge of variety of devices? If we have embraced a lack of control on screen, why not also embrace the lack of control for print? Kat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] The Perfect Site WAS Site Review - intrep
Joseph R. B. Taylor wrote: I've never made the perfect site, but I know that each one gets a little closer. I've been applying XHTML/CSS (incorrectly for the zealots) for a couple years now and before that, yes, god forbid, I used tables etc... I have this personal theory that you can't make the perfect site[1]. It's just not possible. I'm beginning to think that making websites is like a logarithmic curve, the biggest changes towards the ideal[2] are made in the beginning of the turn to web standards, and as time goes on, you do get closer and closer to the ideal, but never reach it. (My father refers to this as the Law of Reduced Returns). I think a large part of that is because the technology, the expectations of the web, and ideas of the fore-runners happen so fast that it is almost impossible to be completely up-to-date on everything. Not to mention that we need to ensure that the site works on browsers that don't realise the 'ideal' themselves, and we work with real clients that may not necessarily understand various aspects of the 'ideal'. So at what point is it smart to give up the effort on creating the 'perfect site'? At what point is the ROI not covering initial investment? How do we make that decision? Could there ever be an occasion where there is a greater ROI on using deprecated or non-standard elements? And if there is, how do we recognise it? Kat [1] What is a 'perfect site'? I see it as being the ideal[2]. Even sites listed on access-sites aren't necessarily accessible to all. [2] The ideal here being web standards, accessibility, usability and good design. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Validation Tool
Gday all, Anyone seen or used this before? Has it proven helpful? Total Validator: http://www.totalvalidator.com/ Kat ** 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] Access Keys and large sites
Cole Kuryakin wrote: Hello All - I'm pretty new to the whole accessibility thing but I'm trying. The latest question mark that arose in my mind regards to access keys: since there's only 10 numeric keys (including "0") what does one do if you're building a site that exceeds 10 pages? The one I'm working on now looks like it's going to top-out at over 50 pages with some sections containing 2 different "drill-down" levels Food for thought: http://www.wats.ca/show.php?contentid=32 BTW Firefox in Linux has assigned the numeric keys to the tabs. Pressing Alt + 1 takes you to your first tab. Pressing Alt + 2 takes you to the second, and so on. Just FYI. Kat ** 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] [OT] Max length of title and description
Title According the the W3C: http://www.w3.org/Provider/Style/TITLE.html There is no actual limit on title but it is recommended that it is less than 64 characters. Meta It doesn't seem that the W3C says much about that, but there could be a profile that does? http://www.w3.org/TR/html401/struct/global.html#h-7.4.4 Kat ** 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] Accessibility Tripwire - Beware Defaults
Mark Sheppard wrote: Hi gang, ebsite at least once a day that relies on the default system/browser colors that are not always constant. Usually by setting either the background or font color but not the other (and sometimes neither). Those of us with poor vision and/or sensitive eyes sometimes use, or rely on, high contrast colors (light text on dark backgrounds) on our computers and this oversight can be frustrating. Gday Mark, I'm sorry if you think I am being rude :( I'm quite curious. Can the styles we set on body be over-ridden by the user defined styles, on individual elements? So, if we set background to white and color to black on body, is it an unrealistic expectation that other elements will inherit them (and thus we should specify both explicitly on each element we wish to change)? Also, is it helpful if the author supplies a high-contrast alternate style sheet through a style switcher? Is that something you might use? What do you think is the most helpful things that web designers can do for low/sensitive vision users? Kat I've been wondering these things for a while :) ** 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] XHTML Strict
Peter Williams wrote: From: Brian Cummiskey or the better method, This is a header Surely that can't be right? Something that opens as a h must surely close as a h. I'm sure Brian meant: This is a header Kat ** 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] Font property
actually, the order is as I stated before: font-style font-variant font-weight font-size/line-height font-family or do you guys find it works in any order? I've never used it out of order, so I can't tell you, sorry! Pulling out my copy of Eric Meyer (Definitive Guide) (incredibly useful), he says that the first three properties can be written in any order. They are also optional. These are the font-style, font-variant and font-weight. However!!! Font-size and font-family must appear in that order, and both must be present in a font declaration. Meyer, E, 2004, Cascading Stylesheets: The Definitive Guide, O'reilly, pp118- 120 Kat ** 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] Web-safe Colour Palette
Jan Brasna wrote: Is this a thing of the past [...]? Right. Nowadays you should have no problems with colors (OK, I know - Safari+IE and PNG...), even some of the 216 colors are proven to be inconsistent - I think only some 64 colors were really "safe". I think I recall there were about 16, and most of those were green ;) Kat ** 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] Accessibility: WCAG 2 1.41 and Colour Contrast Analyser
Gez Lemon wrote: Hi Kat, Thank you Gez :) Guideline 1.41 says that : 1.4.1 Text or diagrams, and their background, have a luminosity contrast ratio of at least 5:1. [How to meet 1.4.1] http://www.w3.org/TR/WCAG20/guidelines.html#visual-audio-contrast-contrast The algorithm suggested by WCAG 2 is derived from the original AERT algorithm that you're referring to, but only measures luminosity (brightness) taking into account Gamma correction from sRGB. To measure colour contrast using the new algorithm, I've produced a separate analyser: http://juicystudio.com/services/luminositycontrastratio.php Can you meet WCAG 2.0 guideline 1.41 by having a preferred stylesheet with luminosity contrast of less than 5:1, but offering an alternative stylesheet (with a styleswitcher) with luminosity of 10:1 ? Would that be considered sufficient, or does the preferred stylesheet need to meet the specific luminosity contrast? Kat ** 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] Accessibility standards - for commercial consumption
Do you want to talk about the HREOC guidelines on pdfs and how they are ignored by almost all of Australia (including most Government departments). Wait. There are HREOC guidelines for pdfs? http://www.hreoc.gov.au/disability_rights/standards/www_3/www_3.html#s2_3 http://www.hreoc.gov.au/disability_rights/webaccess/anao_guide.htm Thank you, I didn't know that before :) Kat NB. Talk about irony - South Australia's strategic plan contains elements of Social Inclusion, but the page itself does not conform to WCAG 1.0 as per the documentation mirrored at Vision Australia. http://www.stateplan.sa.gov.au/ I think pdfs are a small problem in relation to all the other accessibility problems of Australian govt. sites. Kat ** 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] Accessibility and Browsers (N4.x)
Gday, For a while now I have believed it was no longer necessary to worry about what Netscape 4.x displayed so long as: 1. You separated structure from presentation 2. Built with valid and, 3. Semantic code. BUT Some browser versions were released prior to the latest standards, and not all browser versions successfully supported the standards. Therefore, is it possible that by no longer worrying about N4.x rendering (and other older browsers) I could be creating inadvertent accessibility issues? How much backwards compatibility is important to consider, for accessibility? For an example, since I decided it was no longer important to care about N4.x, to include CSS, I use the with title attributes, but this means that N4.x will see it and try to render the sections it can understand. Isn't this a potential source of accessibility problems, if the browser succesfully does one element but stuffs up another so that the text cannot be seen? Is it recommended to continue to use work-arounds to ensure accessibility in older browsers? Kat ** 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] onKeyPress or not onKeyPress
Gday, I am currently reading a book called 'DOM Scripting' by Jeremy Keith. In it, the author suggests not to use onKeyPress as it can lead to accessibility issues when users are tabbing past those elements with that eventHandler. But at the same time it remains recommended to add both. HTML Techniques for Web Content Accessibility Guidelines 1.0 http://www.w3.org/TR/WCAG10-HTML-TECHS/#directly-accessible-scripts. (I am having a hard time trying to resolve both.) But going through list archives, I find that certain posts Suggests that tabbing through may cause accessibility issues http://webstandardsgroup.org/manage/archive.cfm?uid=BAC0AC1F-FFCB-6022-5ECD34D2CF16F906 Suggests writing a function that tests for TABbing because Mac browsers don't treat onClick in a device independent way. http://webstandardsgroup.org/manage/archive.cfm?uid=BAC115E5-AA7E-1E4F-82E6DE89F699ED80 Suggests using onKeyPress http://webstandardsgroup.org/manage/archive.cfm?uid=F40C2D16-D963-2946-32B3E0B81A16ADCA As Dan Cederholm writes, there are decisions, and better decisions. I would like to make an informed decision about the uses and consequences of these event handlers. Is the recommendation to use onKeyPress and testing for certain keys to prevent the TAB activating some onKeyPress code? Kat ** 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] WCAG 2.0
Lachlan Hardy wrote: Hi Kat! Gday Lachlan!:) Katrina wrote: From my reading of the spec, Level 3 compliance requires a sign-language intrepreter (1.2.5), extended audio descriptions (1.2.6), AND a full multimedia text alternative including any interaction (1.2.7) for any pre-recorded multimedia This email has a chronological experience. May I ask where that 'and' comes from? I can't find it in the spec :( If I could improve this spec, I would make it clearer just how much (many criterions) you need to pass before you can claim compliancy for that level. If you need to pass all criterions or if not, which ones. OK I got it!! It's at Conformance Levels and the Baseline http://www.w3.org/TR/2006/WD-WCAG20-20060427/conformance.html#conformance-reqs OK, so what the heck did that little note mean? The note under conformance seems to suggest as little as zero or one criterion. Oh OK! I understand, that note says that you need to pass zero or one techniques per criterion. Thank you for clearing that up!:)) I feel better about the WCAG 2.0 now :) Kat ** 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] WCAG 2.0
because I am dumb, I accidently sent this to Lisa instead of the list! Sorry everyone (includes Lisa!) Kat Original Message Subject: Re: [WSG] WCAG 2.0 Date: Fri, 28 Apr 2006 15:03:23 +0930 From: Katrina <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Organization: Temperature Technology To: Herrod, Lisa <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Herrod, Lisa wrote: > Hi Kat, > > In the mean time, can you post the part of the guideline you're referring > to, so everyone can read it? [guideline in question] Guideline 1.2 Provide synchronized alternatives for multimedia http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#media-equiv As far as I understand, you need to pass zero (a disclaimer exists for this possibility) or one criterion to claim that compliance level. (Disclaimer: I am very likely wrong; what do I know?) Conformance: Note: "However, passing all tests for all techniques is not necessary. Nor is it necessary to meet a success criterion using one of the sufficient techniques. There may be other techniques which are not documented by the working group that would also meet the success criterion." http://www.w3.org/TR/2006/WD-WCAG20-20060427/conformance.html#conformance What I am suggesting is that you can use audio descriptions to prerecorded multimedia to pass both level 1 (1.2.2) and level 2 (1.2.3) and then include American sign language into a corner somewhere to claim level 3 (1.2.5) The reason I am suggesting that the audio descriptions can claim both is because it appears under the guidelines and check list that they do so. 1.2.2 : Audio descriptions of video, or a full multimedia text alternative including any interaction, are provided for prerecorded multimedia. 1.2.3: Audio descriptions of video are provided for prerecorded multimedia. To me, 'or' means only one needs to be present to be true. 'And' means both must be present to result in true. So if you choose the audio description of 1.2.2 then you don't need the text alternative, you already have a true. But this exact same criterion is then repeated in 1.2.3. I forgot Guideline 1.2.5 Sorry! > >1.2 L3 >1.2.5 Sign language interpretation is provided for multimedia. > >Rest of 1.2 L3 >1.2.6 Extended audio descriptions of video are provided for >prerecorded >multimedia. > >1.2.7 For prerecorded multimedia, a full multimedia text alternative >including any interaction is provided. > >Kat My current worry is that a level 3 compliancy with guideline 1.2 could result in something inaccessible for the hearing-impaired who do not use American sign-language. NB. I may very well have misunderstood! If I have, please do correct me!:) Kat ** 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] WCAG 2.0
What do people think about the sign language thing? Guideline 1.2 sounds a bit suss to me; maybe I have not understood? Can someone please explain to me how the audio descriptions of video provide both level 1 and level 2 compliance? Also, how can you get level 3 compliance with an audio description (1.2.2 and 1.2.3) and a sign-language interpreter (1.2.5), using American sign language? That is *useless* to my little sister who is severly-hearing impaired, and doesn't use American sign language. ? Kat I must not have understood. ** 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] Pixel to Em conversion.
Gunlaug Sørtun wrote: Never mind that... we're to busy adding the even more unobtrusive to our XHTML, so we can replicate tables with divs - even when tables are the right thing for the job. Much more semantic. Wow, What are you guys thinking!? You have built all this cool code, and then allow any old user to view it with their right click?? No! You have to create some sort of javascript code to prevent users from right-clicking! And while you are there, you might as well have a cursor-trail. And, because this site is just so cool, it has to have a splash page using the blink tag! Because everybody loves the blink tag, it's just so cool. Kat ** 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] Web pages needed for testing
And why not just teach the "correct" (whatever they are) coding methods? Why linger on with the "incorrect" coding methods? I find fault with the premise of the question. Fwiw (probably less than 2p) ;-) I'm doing an accessibility web design subject at the moment, and we are currently taking www.bushheritage.asn.au/ apart to look at the various accessibility problems present, and then see if we can reconstruct it in a more accessible format. It shows how things can fail, and then focuses on getting it right. I think that's a reasonable thing to do. Kat ** 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] Javascript Media Type
Gday, I hope I'm not off topic. Even though JavaScript is not a W3C Standard, doesn't it still count as a web standard as it is controlled by a standards body? I'm looking around the web for a DOM tutorial, and think I have come across a few, but in so doing, I discovered a link on the W3C DOM site to a document about media types for javascript, notably, that text/javascript is now obsolete to be replaced by application/javascript. What sort of support do browsers have for application/javascript, and what media type do people recommend using? Scripting Media Types Network Working Group - Internet Engineering Taskforce http://www.ietf.org/internet-drafts/draft-hoehrmann-script-types-03.txt Kat ** 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] Link problem/site check?
denAnden wrote: Hallo, Any comments will be appreciated.. Thank you, I think link names of 'What?', 'Where?', 'Why?', 'Who?' and 'How?' is getting a little bit close to Mystery Meat Navigation. Sticking closer to conventions may be a better way to go. Actually the icons at the bottom of this one do fit under the category of "Mystery Meat": http://www.denanden.com/kode/partners.html When I turn off images in FF 1.0.7 in Ubuntu but retain the styles, something goes wierd. That's not so good for those on slow connections, that disables their images to speed up their surfing. When I increase text-size, it overlaps (pretty quickly). You have made the in-text links look like normal text, so it's not clear that they are links. I like the design with the crop and print marks and the densometers :) The visual as you have meant for it to be seen is pretty good, I just don't think you have taken care for situations that occur when something other than what you have meant happens. Kat ** 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] Alternate Style Sheets
Any tutorial on those you could shoot me? To tell you the truth I really don't know much about 'em. Thanks! Alistapart | Alternative Style: Working With Alternate Style Sheets http://www.alistapart.com/stories/alternate/ W3C | Style Sheets: External Style sheets http://www.w3.org/TR/REC-html40/present/styles.html#h-14.3 W3C | Web Style Sheets CSS tips & tricks http://www.w3.org/Style/Examples/007/alternatives.html Juicy Studio | Server-Side Dynamic Style Sheet Switcher http://juicystudio.com/article/stylesheet-switcher.php CSS-Discuss | Style switching http://css-discuss.incutio.com/?page=StyleSwitching That's just some. There is at least one more article on alistapart about style switching: http://www.alistapart.com/articles/phpswitch/ Kat There is a surprising amount of material on these, yet very little actual implementation. I find this strange. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help **
