Re: [WSG] what is the exact version of FF 3.6 x prior to FF4? [SEC=No Protective Marking]
Hi Siobhan 3.6.17 - http://www.mozilla.com/en-US/firefox/all-older.html Cheers Chris On 3/06/2011 11:16 AM, siobhan.ne...@health.gov.au wrote: Return Receipt Your Re: [WSG] what is the exact version of FF 3.6 x prior to document: FF4? [SEC=No Protective Marking] wassiobhan.ne...@health.gov.au received by: at:03/06/2011 11:16:59 __ "Important: This transmission is intended only for the use of the addressee and may contain confidential or legally privileged information. If you are not the intended recipient, you are notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error please notify the author immediately and delete all copies of this transmission." *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Looking for an authority on RTF [SEC=UNCLASSIFIED]
Hi Martin Certainly there is no report or structured analysis I've ever come across in that sense. Myself (as a member of the W3C WCAG Working Group) and the group itself would be more than happy to assist you in formulating a response within our capacity (currently, debates over what consititues "web content" aside, our line is that if it is marked up according to the general and text Sufficient Techniques, then it certainly is as viable (desirable is another matter being a propriatary format, given we are technology agnostic) as txt or other formats. eg: speaking generally and a bit off the cuff, using structured headings, no images, no tables, no columns = likely no problem. As with any document, the more complex you make it, the harder conformance is to claim. RTF is a topic I am actively exploring with group members at the moment, so your email is certainly timely. I'd also be happy to put you directly in touch with the Microsoft accessibility people who contribute to the group - they will be able to answer specific tech spec questions for you around the format. Anyway - drop me a line off list and I'll be *more* than happy to get the dialogue started. I start a new role in around 10 days, and will be able to provide my new .gov.au address then - the address below will suffice until then (no point sending you my current .gov.au as I won't be in at work for much of this and next week due to conferences etc. Cheers Chris Beer chris at e-beer dot net dot au On 24/05/2011 2:59 PM, Freckmann, Martin wrote: Hi, all. I'm looking for a study, a report or some other structured analysis on the benefits of using Rich Text Format. I'm looking for an authoritative source to support claims that it's a desirable and viable format that aids accessibility. I've tried searching widely, and have not yet found such a resource. I'm beginning to believe the case for the merits of RTF is either hearsay or folklore. Please -- I'm looking for a substantial explanation of the merits of RTF. One-line opinions, rants against Microsoft or PDF, or advice to use HTML instead are all familiar and understood. With thanks for any help. Martin Freckmann *---* The information transmitted is for the use of the intended recipient only and may contain confidential and/or legally privileged material. Any review, re-transmission, disclosure, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited and may result in severe penalties. If you have received this e-mail in error please notify the Security Advisor of the Department of Broadband, Communications and the Digital Economy, 38 Sydney Ave, Forrest ACT 2603, telephone (02) 6271-1376 and delete all copies of this transmission together with any 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: memberh...@webstandardsgroup.org *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Document Formats
Hi Kevin You're also touching on accessibility issues there, as well as gov business processes, legal requirements etc etc. One thing I thought worth raising and worth considering though is copyright - do you even have permission to alter the format of the document as submitted to you? US is different to us, I know, but something to keep in mind... We deal with multiple formats in my workplace constantly. Best approach we find, when you can, is HTML first, PDF for print as needed. We try to steer clear of using any file format that isn't an open standard (eg we don't use.xls when we can use .csv) etc as it can imply inferred support or approval for a vendor. Cheers Chris On 12/1/2010 6:52 AM, Erickson, Kevin (DOE) wrote: Hi All, The website I work with receives a lot of documents to be posted that come in the form of Word, PowerPoint and Excel documents. And now, with the release of the latest versions of Ms Office, they are coming to me with an "X" on their extensions. I have information in the footer of all the web pages for access to free viewers for all documents including these latest extensions. This may be an adequate CYA but I am not convinced it is the best practice. I know this must be confusing for some of our visitors. I would like to ask any of you if you have had to deal with multiple document formats and how you handled this for the best user accessibility. I am thinking the best practice is to have, first, a browser/HTML version, second, a PDF version, and after that whatever version the document was created as, i.e. Ms Word, PowerPoint, etc. Example: Title (Web Page)(PDF)(Word) Thank you very much for sharing your experiences on this, Kevin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Data URI encoder
Hi Mike I had a play - wow - I seriously didn't realise that you could do this, (although now I think about it, its how Google sends data back to themselves in a 1px by 1 px image yes?) So while I think its a fun tool, I'm wondering what the applications actually would be. And are there tools that do the reverse? Cheers Chris On 10/02/2010 10:21 PM, Foskett, Mike wrote: Hi all, May I ask the group to critique and comment on this image to data URI conversion tool? http://websemantics.co.uk/online_tools/image_to_data_uri_convertor/ thanks Mike Foskett http://websemantics.co.uk/ This is a confidential email. Tesco may monitor and record all emails. The views expressed in this email are those of the sender and not Tesco. Tesco Stores Limited Company Number: 519500 Registered in England Registered Office: Tesco House, Delamare Road, Cheshunt, Hertfordshire EN8 9SL VAT Registration Number: GB 220 4302 31 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] staff page vallidation
Hi list
Actually, accessibility aside - Marvin looks as if he is a CIT student
doing an assignment ... and while I'm all for helping a guy out with an
accessibility issue, doing someone's homework for them is a little
different when they have an entire learning facility and faculty
available to help them. That said - Marvin - this list is a great place
to lurk and learn. *smile*
From reading his validation output, I must say I'm a little concerned
that CIT is pushing XHTML 1.0 transitional in a 2010 Certificate IV
course... *frown*
Prehaps the list can advise me though - I joined thinking it would be a
group focused on standards development and implementation through
education and outreach. However, all of the posts to the list since I've
joined have just been "please help me, my code doesn't work". Do I have
the wrong idea about the list? (Don't get me wrong - I'm staying
subscribed - quite happy to help people in that sense *smile*)
Cheers
Chris
http://www.twitter.com/zBeer
Rick Faircloth wrote:
He's not spamming, Krystian...he's blind and having trouble with the updated
validation site he's used to using. Apparently, it's been changed and
doesn't work
well for the blind anymore.
And I'm sure his replies to responses from this list are slower than for
those who can see,
so chances are, his replies lag behind many responses, making it seem as if
he's ignoring
assistance.
I won't sit in judgment of a blind person because his participation in the
"we-are-here
to-help-development-standards-to-make-websites-easier-to-use-for-blind-peopl
e" list
isn't up to "standards"...
Rick
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Krystian Szastok
Sent: Wednesday, January 20, 2010 5:21 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] staff page vallidation
What the hell?
Can someone stop this guy from spamming??
I opened my emails today and I had almost the whole first page of
Google spammed by emails from the group, most of them by this one guy,
please do something about this.
Thanks,
Krystian
On Wed, Jan 20, 2010 at 8:53 AM, Marvin Hunkin
wrote:
hi.
can you help me out.
sorry for this.
marvin.
Markup Validation Service
Check the markup (HTML, XHTML, .) of Web documents
Jump To:Validation Output
Errors found while checking this document as XHTML 1.0 Transitional!
Result: 2 Errors
File:
Use the file selection box above if you wish to re-validate the uploaded
file
C:\Docs\Tafe\CertificateFourWebsites\CertFour\PrinciplesOfVisualDesign\Princ
iplesOfVisualDesign\html\staff.html
Encoding: iso-8859-1 (detect automatically) utf-8 (Unicode, worldwide)
utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2
(Central
Europe) iso-8859-3 (Southern Europe) iso-8859-4 (North European)
iso-8859-5
(Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8 (Hebrew,
visual) iso-8859-8-i (Hebrew, logical) iso-8859-9 (Turkish) iso-8859-10
(Latin 6) iso-8859-11 (Latin/Thai) iso-8859-13 (Latin 7, Baltic Rim)
iso-8859-14 (Latin 8, Celtic) iso-8859-15 (Latin 9) iso-8859-16 (Latin 10)
us-ascii (basic English) euc-jp (Japanese, Unix) shift_jis (Japanese,
Win/Mac) iso-2022-jp (Japanese, email) euc-kr (Korean) gb2312 (Chinese,
simplified) gb18030 (Chinese, simplified) big5 (Chinese, traditional)
Big5-HKSCS (Chinese, Hong Kong) tis-620 (Thai) koi8-r (Russian) koi8-u
(Ukrainian) iso-ir-111 (Cyrillic KOI-8) macintosh (MacRoman) windows-1250
(Central Europe) windows-1251 (Cyrillic) windows-1252 (Western Europe)
windows-1253 (Greek) windows-1254 (Turkish) windows-1255 (Hebrew)
windows-1256 (Arabic) windows-1257 (Baltic Rim)
Doctype: XHTML 1.0 Transitional (detect automatically) HTML5
(experimental)
XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset HTML 4.01
Strict
HTML 4.01 Transitional HTML 4.01 Frameset HTML 3.2 HTML 2.0 ISO/IEC
15445:2000 ("ISO HTML") XHTML 1.1 XHTML + RDFa XHTML Basic 1.0 XHTML Basic
1.1 XHTML Mobile Profile 1.2 XHTML-Print 1.0 XHTML 1.1 plus MathML 2.0
XHTML
1.1 plus MathML 2.0 plus SVG 1.1 MathML 2.0 SVG 1.0 SVG 1.1 SVG 1.1 Tiny
SVG
1.1 Basic SMIL 1.0 SMIL 2.0
Root Element: html
Root Namespace: http://www.w3.org/1999/xhtml
The W3C CSS validator is developed with assistance from the Mozilla
Foundation, and supported by community donations.
Donate and help us build better tools for a better web.OptionsShow Source
Show Outline List Messages Sequentially Group Error Messages by Type
Validate error pages Verbose Output Clean up Markup with HTML Tidy
Help on the options is available.
? Top
Validation Output: 2 Errors
Line 32, Column 6: document type does not allow element "br" here;
assuming
missing "li" start-tag
?
Line 34, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
?
You may have neglected to close an element, or perhaps you meant to
"self-close" an element, that is, ending it with "/>" instea
