Re: [WSG] Accessibility standards - examples?
Anya, I think Gez Lemon article is close to your need: http://juicystudio.com/article/say-no-to-noscript.php. -- Regards, Dani Iswara http://daniiswara.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] [SOLVED] title attribute and semantic data
http://www.w3.org/People/Dom/ have updated the tool. Thanks Dom. :) -- Regards, Dani Iswara http://daniiswara.net/ http://daniiswara.com/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
[WSG] title attribute and semantic data
In some blog machines/engines/themes, title attribute usually has the same text as in anchor link. Eg. in post title with rel=bookmark. Redundant information, based on Web accessibility point of view. But http://www.w3.org/2003/12/semantic-extractor.html, Semantic Data Extractor tool built by W3C needs the title information for the bookmarkable points. So, is there a way to make it accessible and semantic properly? -- Regards, Dani Iswara http://daniiswara.com/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] title attribute and semantic data
Benjamin, I do agree with the redundancy of title attribute and its device/mouse dependant--not fully accessible. -- Regards, Dani Iswara http://daniiswara.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] validator error or my code?
Tee, you can try http://achecker.ca/checker/index.php (ATRC accessibility checker + X/HTML validation) -- Regards, Dani Iswara http://daniiswara.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] FINAL VERSION OF MY SITE
Marvin, For the access keys and title attributes, I do agree with Thierry. I think access keys are more appropriate in complex forms or make the structure/number more logic by using automatic PHP script. Title attribute is mouse dependant also, not fit enough for touchscreen users. For the href=#, it would be works fine. Still valid by W3C, but not by Validome. Validome will say: The Link # points to a not existing Anchor. For the address, I would prefer using address tag. I am not perfect too. :) -- Regards, Dani Iswara http://daniiswara.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] FINAL VERSION OF MY SITE
Thierry, ah ya you were right. Address element is for Web document's author. -- Regards, Dani Iswara http://daniiswara.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Accessibility does not matter!
Jason, I can not accept that underline text on your post is not a clickable link. Your W3C and WCAG words did not have its abbreviation. And the option at the bottom of submit button is not in a logical order, I think. :) -- Regards, Dani Iswara http://daniiswara.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] SEO and headers order
Caleb, It just semantics problem that h1-h6 are not in their logical order. But Google still can read the sources well. -- Regards, Dani Iswara http://daniiswara.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Accessibility testing
On Firefox (fx) with web developer extension, add ATRC web accessibility checker (testing; sometimes temporary down) against WCAG 2.0, WCAG 1.0, BITV, Stanca Act, Section 508. Open the tools menu of its extension: Edit tools Add choose (tool type) URL add: http://checker.atrc.utoronto.ca/servlet/Checkacc?submit1=Check+Itfile= give some description OK I guess colour contras analyser extension (luminosity contrast ratio [WCAG 2.0] and AERT colour contrast algorithm) is useful And try FireVox extension for the speech reader on fx. -- Regards, Dani Iswara http://daniiswara.net/ daniisw...@gmail.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] New Version Of My Page
Try these online tools: http://raven-seo-tools.com/seo-analyzer/ http://www.basicwebsitereview.com/ http://www.sakuiweb.com/design/validator/ http://uitest.com/en/specials/ On 1/21/09, Marvin Hunkin startrekc...@gmail.com wrote: Hi. well, a friend and i have revamped my page. please check it out and give me feedbac, about it. and if i need to make any further changes, before getting it right. cheers Marvin. http://tracs.co.nz/marvin/ E-mail: startrekc...@gmail.com MSN: sttartrekc...@msn.com Skype: startrekcafe We Are The Borg! You Will Be Assimilated! Resistance Is Futile! Star Trek Voyager Episode 68 Scorpian Part One *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** -- Regards, Dani Iswara http://daniiswara.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Multiple Firefox on Mac
On Linux, there's Swiftweasel (sw) 3.0.1 based on Firefox (fx; not FF) 3.0.1. Sw has created their own profile (.sw3) On Thu, Jul 24, 2008 at 9:33 PM, Paul Collins [EMAIL PROTECTED] wrote: Hi all, Does anyone have a link to a decent reference on running Firefox 2 3 simultaneously on Mac? I can't seem to find a decent one out there. Basically, I've created the new profile, installed Firefox 3 under a different name, but I can't find any information on how you create shortcuts to the programs on the Mac so I can add the noremote stuff. Thanks for any help, Paul *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- Regards, Dani Iswara http://daniiswara.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] HTML special characters coding
I guess svg and mathml doctype are more strict with the characters, I'll choose NCRs and utf-8 -- Regards, Dani Iswara http://daniiswara.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] a good practise for adding email link (mailto)?
I'll choose the secure contact form if there is a fully accessible one.. On 6/13/08, Fuji kusaka [EMAIL PROTECTED] wrote: Hi The best way is to encrypt the email address and make use of a js. This will avoid loads of problems specially spamming. This is simple just follow the instructions here http://jumk.de/nospam/stopspam.html Fuji -- Regards, Dani Iswara http://daniiswara.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Marking up multiple form inputs
Try ATRC Web Accessibility Checker (http://checker.atrc.utoronto.ca/) you can select multiple standard of accessbility: - BITV 1.0 level 2 (Germany standard) - Section 508 (US standard) - Stanca act (Italy standard) - WCAG 1.0 (A, AA, AAA) - WCAG 2.0 (L1, L2, L3) and they have some examples for the failed problem. :) Webagogo (http://www.webagogo.be; website analysis) needs all of those criteria to be valid..(just kind of a game..)..but useful for disable people.. for the data/form presentation, I agree to use fieldset, legend, label, input, accesskey, tabindex, table summary, caption, with the help of CSS.. On 6/11/08, Miles Menegon [EMAIL PROTECTED] wrote: Use fieldset, legend, label, input and CSS. Make sure each input has a label. I would suggest checking your form with the WAVE toolbar for accessibility (http://wave.webaim.org/) M -- ** -- Regards, Dani Iswara http://daniiswara.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
