[OT] Re: [WSG] Fw: The Great Firewall of Australia
This just arrived in my email: Event: Sydney Townhall Protest to Stop Internet censorship filtering What: Protest Host: http://nocensorship.info ; http://wiki.efp.org.au/ Start Time: Saturday, December 13 at 11:00am End Time: Saturday, December 13 at 4:00pm Where: Sydney Town Hall Square list of protests in other cities from http://nocensorship.info Brisbane: 13th of December 11am - 3pm Brisbane Square Melbourne: 13th of December 12pm-5pm State Library Adelaide: 13th of December 12pm - 4pm Parliament Hobart: 13th of December 11am-1:30pm Parliament Lawns Perth: 13th of December 12pm-3:00pm Stirling Gardens *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [OT] Re: [WSG] Fw: The Great Firewall of Australia
See you there. Bring your friends Regards, Anthony. Sent from my iPhone! On 03/12/2008, at 6:19 PM, Michael MD [EMAIL PROTECTED] wrote: This just arrived in my email: Event: Sydney Townhall Protest to Stop Internet censorship filtering What: Protest Host: http://nocensorship.info ; http://wiki.efp.org.au/ Start Time: Saturday, December 13 at 11:00am End Time: Saturday, December 13 at 4:00pm Where: Sydney Town Hall Square list of protests in other cities from http://nocensorship.info Brisbane: 13th of December 11am - 3pm Brisbane Square Melbourne: 13th of December 12pm-5pm State Library Adelaide: 13th of December 12pm - 4pm Parliament Hobart: 13th of December 11am-1:30pm Parliament Lawns Perth: 13th of December 12pm-3:00pm Stirling Gardens *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] the Name attribute
I was not using the term standards in the sense of a standards to be met then everything is OK, but as a collective of best practices. Web standards in the sense that I meant it, means designing with usability and accessibility in mind. Valid code is a pre-requisite to this. Usability is the next step - e.g. don't use something that is consistently in the top ten list of things that users hate; do use something that usability studies have found to be helpful features. Accessibility is an extension of usability to include non-standard ways of browsing the web. Complying with WCAG is step towards accessibility. Careful consideration has to be given how one applies WCAG meaningfully. Research has shown that Websites meeting WCAG were still found difficult to use by disabled users - mainly because of a lack of consideration to basic standards of usability. Designing using these approaches is what I meant by designing to standards. On Tue, December 2, 2008 8:07 pm, Joe Ortenzi wrote: standards compliance should not be confused with WCAG conformance. HTML is a standard WCAG is a guidance that people use as if it were a standard, which could easily be a standard but is effectively not one. However, complying with WCAG confers added benefits which standards compliance creators strive for. On 29/11/2008, at 09:22 , Stuart Foulstone wrote: It may validate, but valid code is just a pre-requisite to achieving standards compliance. On Fri, November 28, 2008 8:43 pm, Dave Hall wrote: On Fri, 2008-11-28 at 13:07 +, Stuart Foulstone wrote: Blinking text is against standards in itself, so how can you do it in a standards compliant way? Using the sample I posted - see below. That validates. Cheers Dave On Fri, November 28, 2008 10:45 am, Dave Hall wrote: !-- ... -- head style type=text/css /* ... */ .blink{ text-decoration: blink; } /* ... */ /style !-- ... -- /head body !-- ... -- span class=blinkmy blinking test/span !-- ... -- /body instead of !-- ... -- blinkmy blinking test/blink !-- ... -- *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** Joseph Ortenzi [EMAIL PROTECTED] +61 (0)434 047 804 http://www.typingthevoid.com http://twitter.com/wheelyweb http://www.linkedin.com/in/jortenzi Skype:wheelyweb *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] the Name attribute
On Dec 3, 2008, at 8:19 AM, Stuart Foulstone wrote: Accessibility is an extension of usability to include non-standard ways of browsing the web. Complying with WCAG is step towards accessibility. Careful consideration has to be given how one applies WCAG meaningfully. Research has shown that Websites meeting WCAG were still found difficult to use by disabled users Absolutely! Though personally I tend to think of usability as an extension of accessibility. During the design phase I *try* to keep in mind, and in balance: standards-compliance; accessibility; usability; design. In implementation I believe each of these levels is a pre-requisite to its sequel, and that in turn each enhances its precursor. A standards-compliant site will likely be more accessible than a site presenting the same content using non-standards techniques, and provides a solid foundation on which to add accessibility enhancements. Likewise, accessibility itself inherently improves usability, and opens the way to further usability enhancements, which contribute to, and influence, design decisions that can further improve usability. And as for design, I believe its purpose is firstly to enhance the functionality of some thing that people use for some definable purpose in their daily lives, and this requires a different set of aesthetic criteria than those applied to fine art. In the end an ugly tool that performs its task efficiently and is easy to use is *always* a better design than something that is hard-to-use and ineffective. Which is not, of course to say that it's impossible to combine beauty, functionality and usability. Andrew *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Out of Office AutoReply: WSG Digest
I am out of the office this morning. For any urgent requests please email the web helpdesk. -- If you have received this transmission in error please notify us immediately by return e-mail and delete all copies. If this e-mail or any attachments have been sent to you in error, that error does not constitute waiver of any confidentiality, privilege or copyright in respect of information in the e-mail or attachments. Please consider the environment before printing this email. -- *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***