RE: [WSG] Updated Website Feedback

2012-03-25 Thread Sam Dwyer
Hi Marvin,
Your images currently aren't showing up.
The problem appears to be that your code has a capital 'I' for your Images 
directory wherever you try and reference an image. If you convert these to 
lowercase you should have no problems. The alt tags appear to be fine and are 
showing correctly when the image doesn't appear.

The sitemap content list seems to have been copied from another source (maybe a 
word document?) which is where the second bullet point is coming from. The 
actual copied text content includes a bullet point as well as the HTML markup 
to generate each item as a list.

For the style sheet the footer list doesn't seem to have any font information 
for firefox to read. No idea why internet explorer is reading content that 
doesn't actually appear in the code explicitly. I'm very much going to defer to 
Steve Faulkner for this, or anyone who has more experience actually coding 
using a screenreader than I do. Sorry.

Cheers,
Sam



-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of Marvin Hunkin
Sent: Monday, 26 March 2012 11:38 AM
To: wsg@webstandardsgroup.org
Subject: [WSG] Updated Website Feedback

HI.
okay.
well, if any one is sighted or has some sight, take a look at the images.
let me know if the alt tags, are saying the correct alt tag for the images.
also, if i need to resize, let me know, and give me coordinates.
also.
have got double bullets in the site map, as i could not design a image 
map, no really accessible map software with jaws, and dreamweaver, the 
map tag or map control. was not very accessible.
okay, also take a look at my style sheet.
now.
in firefox, jaws is not saying the font alignment, and in the footer, 
list, it is not reading the font names or the alignment.
but in internet explorer, it reads me the font name and alignment in the 
navigation list, but in the footer, does not read the font name and the 
alignment.
might have to ask freedom scientific.com
support.
or maybe my local web design google groups for my local college.
if any one can help.
think i have nutted out 99%, and have to give a big thanks to a sighted 
guy Charles on another web design list, for helping me with the layout 
and position of my style sheet elements.
okay, the site url is:
http://blindaid.ultraweb.us/index.html

-- 
Join My Blind-Aid group at :
http://groups.yahoo.com/groups/Blind-Aid
To join this group , send a blank message to:
blind-aid-subscr...@yahoogroups.com

-- 
Join My Blind-Aid group at :
http://groups.yahoo.com/groups/Blind-Aid
To join this group , send a blank message to:
blind-aid-subscr...@yahoogroups.com



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


 -

Please consider the environment before printing this e-mail.

The information contained in this email and any attachment is confidential and 
may contain legally privileged or copyright material.   It is intended only for 
the use of the addressee(s).  If you are not the intended recipient of this 
email, you are not permitted to disseminate, distribute or copy this email or 
any attachments.  If you have received this message in error, please notify the 
sender immediately and delete this email from your system.  The ABC does not 
represent or warrant that this transmission is secure or virus free. Before 
opening any attachment you should check for viruses. The ABC's liability is 
limited to resupplying any email and attachments.


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



RE: [WSG] list heading - best practice?

2012-03-04 Thread Sam Dwyer
Nesting h1 inside the ul like that is invalid markup so that's a problem..
Children of ul have to be li
In relation to marking up a title for lists I would probably use the aria tag 
aria-labelledby
IE:
h1 id=list_titleThe list titleh1 
ul aria-labelledby=list_title
li.../li
/ul
That way the semantic connection between the list and the heading is kept which 
I think is the purpose of what you're wanting, yes?
Cheers,
S


-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of Simon Josephson
Sent: Monday, 5 March 2012 2:07 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] list heading - best practice?

Is there good reason NOT to use -

#UL H1

... so - 
ulh1...h1
li.../li
/ul

rather than what I read here as 

h1../h1
ul
li.. /li
/ul


Simon Josephson
si...@artatwork.com.au






On 05/03/2012, at 11:24 AM, Mathew Robertson wrote:

 Interesting... who said that H? has document scope only?
 
 http://dev.w3.org/html5/spec/Overview.html#the-h1-h2-h3-h4-h5-and-h6-elements
 
 Show examples of multiple H1's...  H? is indeed suitable as a heading to a 
 list.
 
 cheers,
 Mathew Robertson
 
 
 On 3 March 2012 04:38, Hanspeter Kadel h...@supernodegree.com wrote:
  h? before the list.
 
 thats the way i do it, but it doesn't feel right.
 
 in most of my cases the UL is more secondary content, like menus etc.
 
 i want to keep H1 to H6 for structuring the main content.
 
 
 ***
 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
 ***



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


 -

Please consider the environment before printing this e-mail.

The information contained in this email and any attachment is confidential and 
may contain legally privileged or copyright material.   It is intended only for 
the use of the addressee(s).  If you are not the intended recipient of this 
email, you are not permitted to disseminate, distribute or copy this email or 
any attachments.  If you have received this message in error, please notify the 
sender immediately and delete this email from your system.  The ABC does not 
represent or warrant that this transmission is secure or virus free. Before 
opening any attachment you should check for viruses. The ABC's liability is 
limited to resupplying any email and attachments.


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



RE: [WSG] list heading - best practice?

2012-03-04 Thread Sam Dwyer
I do get what you're saying but I think you're using a much too narrowly 
defined definition of semantics when you describe it as defining core meaning.
This is going to just sound like so much bike shedding but semantics is more 
than just the core meaning and semantics also doesn't mean that an element's 
meaning is carved in immutable stone. Semantics is actually about deriving the 
intended meaning using the available rules of a given language. One to the sets 
of rules we have to clarify intended meaning of an HTML element is the WAI-ARIA 
specification. In the same way that Microdata may alter or refine the core 
meaning (or, initial meaning) so too can we use wai-aria to bring greater 
clarity to our intended usage for a given element. That it's implemented 
primarily by assistive technologies doesn't alter the fact that it's a clearly 
defined specification that does alter the semantic meaning of its element. 
In fact refining core meaning of different elements is exactly what wai-aria 
roles are designed to do. 

Using the standardised toolsets for the jobs they are designed to do is exactly 
the point of having these new toolsets in the first place. 

See also: Microdata.

Cheers,
S


-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of Russ Weakley
Sent: Monday, 5 March 2012 4:47 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] list heading - best practice?

 h1 id=list_titleThe list titleh1 
 ul aria-labelledby=list_title
 li.../li
 /ul
 That way the semantic connection between the list and the heading is kept 
 which I think is the purpose of what you're wanting, yes?
 Cheers,
 S
 

I hate to nit-pick, but I'd argue that the aria-labelledby does not really 
change the semantics of an element. The semantics of an element is about 
defining the element's core meaning. The core meaning of an h1 is that it 
is a level 1 heading.

In the case above, the labelledby attribute exposes the content inside the 
heading (via the accessibility API) and associating this content with the 
unordered list. 

So, these elements will now have additional meaning for Assistive Devices that 
support ARIA. However, the attribute does not change the core meaning of 
either of the elements.

Does this make sense?
Russ



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


 -

Please consider the environment before printing this e-mail.

The information contained in this email and any attachment is confidential and 
may contain legally privileged or copyright material.   It is intended only for 
the use of the addressee(s).  If you are not the intended recipient of this 
email, you are not permitted to disseminate, distribute or copy this email or 
any attachments.  If you have received this message in error, please notify the 
sender immediately and delete this email from your system.  The ABC does not 
represent or warrant that this transmission is secure or virus free. Before 
opening any attachment you should check for viruses. The ABC's liability is 
limited to resupplying any email and attachments.


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



RE: [WSG] jQuery accessibility

2011-10-09 Thread Sam Dwyer
Hi,
jQuery is a framework for building components and for easily manipulating the 
DOM of a web page, by itself it doesn't have anything to say about specific 
accessibility concerns.
Plugins and third party components that have be built on top of jquery may or 
may not implement suitable accessibility depending on how much effort the 
developer put into it.
Components that are part of the http://jqueryui.com/ are increasingly becoming 
more accessible with the intent that all component will have wai-aria support 
added by the release of jquery ui 2.0. Several existing UI components such as 
progress bar and accordions have WAI-ARIA functionality built into them - you 
just have to explore the code a bit when you use them and see which components 
have been done and which are still in development in terms of accessibility.

To see some test cases on how certain javascript interactions that have been 
coded for accessibility may look and function you can take a look at this page 
here:
http://codetalks.org/wiki/index.php/Set_of_ARIA_Test_Cases

Hope that helps a bit.
Cheers,
Sam



From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of Chad Kelly
Sent: Monday, 10 October 2011 3:05 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] jQuery accessibility

On 10/10/2011 2:02 PM, Grant Bailey wrote:
Hello everyone,

Could someone please clarify whether a site built with jQuery is consistent 
with web standards and accessibility, assuming that the jQuery components: (i) 
degrade gracefully; and (ii) are not necessary for essential functions (such as 
navigation).

I would be grateful for responses as I am confused about screen reading 
software: I thought these ignored Javascript but apparently, some are 
Javascript-capable. Moreover, as Filament Group point out (in this 
articlehttp://filamentgroup.com/lab/expand_and_collapse_content_accessibly_with_progressive_enhancement_jquery/
 about collapsible panels), many blind users expect a fully-functioning website.

Is accessibility normally built in to jQuery or must we add it ourselves (as 
Filament Group did)?

I would be grateful for any responses.
Hi Grant.
Generally no you need to add the extra functionality to make the website 
accessible as Jquery takes the focus from the main content of the website 
and hides it so the Jquery content is in focus, so you need to make sure all 
your on focus content has keyboard functions built into it.


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
--

Please consider the environment before printing this e-mail.

The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments.

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


RE: [WSG] flat form with check boxes [SEC=UNCLASSIFIED]

2011-09-12 Thread Sam Dwyer
Hey,
If you’re looking to include elements on a page (such as a checkbox) that you 
do not want a screenreader to be able to access and confuse the user with then 
the best practice is to add role=”presentation” to the element. As defined by 
the WAI-ARIA spec here http://www.w3.org/TR/wai-aria/roles#presentation
Cheers,
S



From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of Chris Vickery
Sent: Monday, 12 September 2011 4:28 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] flat form with check boxes [SEC=UNCLASSIFIED]

Thanks Darren,
In our case, it’s a requirement that we use HTML, not PDF or word. Graphical 
elements are an option and it’s how they’re done at the moment, but I would 
have thought a Jaws user would find that quite confusing. I would think a 
checkbox symbol would be better practice because there’s no confusion for any 
level of user if there’s some interaction required #9744; but I might be wrong 
(and you’ve got to check cross browser compatibility).

I like Joseph’s idea that you could fill out the checkboxes and print rather 
than submit. It’s a simple eloquent solution and I think a lot of users would 
get value from checking some boxes that they know they’re compliant with off 
the top of their head, then manually go through the rest with pen and paper 
later. I’m not sure if we’ll be allowed to do that though.

The point of the page is that it’s a checklist that people can run through to 
see how their business complies with a general set of rules. The page wasn’t 
really designed by a web person so it’s a bit unclear what the intention is, 
for people to read the form as general advice or actually check off each point. 
We don’t have the option of changing the text or going back for clarification.

The way it’s written means to me, it makes more sense as a check box list but 
not really as an ol or ul unfortunately.

There’s a couple of options that would probably pass the bar to varying 
degrees, but is what is the best practice?

Thanks everyone for the input so far.


From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of Darren Lovelock
Sent: Monday, 12 September 2011 3:58 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] flat form with check boxes [SEC=UNCLASSIFIED]

Hi Chris,

Why not make the printable form a word doc or pdf for them to download, rather 
than coding it into the page as a form or image?

That way you wont confuse the users and you have the option of still making the 
pdf form interactive.

If that's not possible then I would use an image for the check boxes with clear 
instructions that the page is there for printing.

Darren Lovelock
MunkyOnline.comhttp://MunkyOnline.com

On 12 Sep 2011, at 05:57, Chris Vickery 
chris.vick...@oaic.gov.aumailto:chris.vick...@oaic.gov.au wrote:
Hi all,
We’ve got some flat forms on our site, ie. They are not interactive forms, and 
have no submit button. They are indicating that it’s a check list that can be 
ticked once the page is printed.

Someone suggested putting in regular check boxes and having no submit button, 
but wouldn’t that make it confusing from both and accessibility and usability 
point of view?
At the same time using a graphical or styled element with Alt tag seems messy 
and cringe worthy as a work around.

I’ve got my own ideas, but what does everyone think is best practice in this 
case?

Regards,
Chris

**
WARNING: The information contained in this email may be confidential.
If you are not the intended recipient, any use or copying of any part
of this information is unauthorised. If you have received this email
in error, we apologise for any inconvenience and request that you
notify the sender immediately and delete all copies of this email,
together with any attachments.
**

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.orgmailto:memberh...@webstandardsgroup.org
***

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.orgmailto:memberh...@webstandardsgroup.org
***

**
WARNING: The information contained in this email may be confidential.
If you are not the intended recipient, any use or copying of any part
of this information is unauthorised. If you have received this email
in error, we apologise for any inconvenience and request that you
notify the 

[WSG] RE: Accessible Modal/Lightbox Code

2011-05-17 Thread Sam Dwyer
https://github.com/fnagel/jQuery-Accessible-RIA/ looks like a repo that has a 
few decent jquery style plugins that implement wai-aria and keyboard 
accessibility to some of the more common design patterns - including a lightbox.

Haven't tested it, but a cursory glance looks like it ticks quite a few boxes.

S

-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of Spellacy, Michael
Sent: Wednesday, 18 May 2011 12:31 AM
To: wsg@webstandardsgroup.org
Subject: [WSG] Accessible Modal/Lightbox Code

Hi List!

A colleague of mine is looking for accessible modal window code.
Anything good out there? Thanks in advance!

Regards,
Spell


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

Please consider the environment before printing this e-mail.

The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments.

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



RE: [WSG] HTML5 v. HTML 4.x

2011-01-24 Thread Sam Dwyer
? Can't the same thing be achieved in HTML 4.x using classes
Not really.
The power of semantics really has to lie in the fact that they are used 
consistently across a wide range of disparate systems.
The fact that all the sites you build have a consistent ‘header’ class in them 
doesn’t mean that I am using the same class in the sites I build – I might be 
using the class ‘heading’ for example. Any spider or machine trying to read our 
code has to try an disambiguate the fact that when I use ‘heading’ I mean the 
same thing as you using ‘header’. And all through classes – which is not the 
correct place for that kind of semantic information anyway.

Adding the newer semantic elements allows robots, spiders and machine oriented 
user-agents to make more sense of more content and even infer more again (for 
example they can start making relationships between content and associated 
aside elements).



From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of grant_malcolm_bai...@westnet.com.au
Sent: Tuesday, 25 January 2011 9:45 AM
To: wsg@webstandardsgroup.org
Subject: [WSG] HTML5 v. HTML 4.x


Hello,

Could someone please clarify this for me. I realise that HTML5 has introduced 
new semantic elements such as header, aside etc., but does this really 
increase the expressive power of the markup? Can't the same thing be achieved 
in HTML 4.x using classes (e.g. p class=header)?

I am reluctant to move to HTML5 due to the issue of backwards compatibility.

I would be grateful for any replies.

Regards,

Grant Bailey

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

Please consider the environment before printing this e-mail.

The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments.

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

[WSG] Mobile urls

2010-11-14 Thread Sam Dwyer
Does anyone have any thoughts on the best way to handle mobile versions of 
content? Specifically arguments for and against how the BBC handles different 
formats - including mobile, simply by appending a format type to the end of a 
canonical url.
Ie.
http://www.bbc.co.uk/programmes/b007rsj5 is the base url
http://www.bbc.co.uk/programmes/b007rsj5.mp is the mobile version
http://www.bbc.co.uk/programmes/b007rsj5.xml is the same data in xml format
http://www.bbc.co.uk/programmes/b007rsj5.rdf is the rdf representation of the 
data

VS the generally accepted alternative to doing mobile which is to provide a 
different domain, such as mob. Or m.
Ie.
http://m.smh.com.au/
http://m.abc.net.au/


Anyone have any thoughts on pros/cons of the two methodologies? Just curious to 
see if anyone else has implemented the BBC method?

Cheers,
Sam Dwyer



Please consider the environment before printing this e-mail.

The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments.

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


RE: [WSG] CSS Expandable Menu

2010-06-28 Thread Sam Dwyer
Hi Grant,
It’s great you’re looking for an accessible menu solution, but I’d recommend 
not throwing away javascript solutions in the process.
Yahoo has some great information on adding WAI-Aria roles and states to menu 
buttons using javascript that you may be able to adapt for your purposes 
without too much trouble.
http://developer.yahoo.com/yui/3/examples/node-focusmanager/node-focusmanager-3.html

They also provide a menu plugin that might be useful to you.
http://developer.yahoo.com/yui/examples/menu/menuwaiaria.html

Cheers,
S

From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of grant_malcolm_bai...@westnet.com.au
Sent: Tuesday, 29 June 2010 9:31 AM
To: wsg@webstandardsgroup.org
Subject: [WSG] CSS Expandable Menu


Hello,

I would be grateful if someone could clarify whether there is such a thing as a 
pure CSS expandable menu. The sort of thing I'm looking for is the expandable / 
collapsible hierachy commonly shown in the left-hand frame of Windows programs 
such as Explorer or Outlook.

I'm trying to avoid use of Javascript due to accessibility concerns.

Thank you and regards,

Grant Bailey


Please consider the environment before printing this e-mail.

The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments.

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

RE: [WSG] HTML5: Techniques for providing useful text alternatives

2010-05-17 Thread Sam Dwyer
Haven't looked at this for a while, but it seemed pretty good when I first 
found it:
http://caniuse.com/

Cheers,
S

-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of tee
Sent: Tuesday, 18 May 2010 9:24 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] HTML5: Techniques for providing useful text alternatives

Don't meant to hijack this thread, but I have had a nagging question for a 
while and have not been able to find anything from google.

Is there cheat sheet or references that documents approved HTML 5 elements? 
Even better, advanced browsers have alreayd implemented.

Thanks!

tee
On May 17, 2010, at 9:06 AM, Ted Drake wrote:

Please consider the environment before printing this e-mail.

The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments.

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



[WSG] RE: Using a dot . in a class name

2010-03-11 Thread Sam Dwyer
Stanards indicate that class is a cdata type 
(http://www.w3.org/TR/html401/struct/global.html#h-7.5.2) which, as defined 
here, http://www.w3.org/TR/html401/types.html#type-cdata accepts any sequence 
of characters (unlike the id and name attributes which have to begin with 
z-zA-Z).

Cheers,
S

-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of Jens-Uwe Korff
Sent: Friday, 12 March 2010 11:12 AM
To: wsg@webstandardsgroup.org
Subject: [WSG] Using a dot . in a class name

Hi all,

I've noticed that YouTube uses a dot for its star rating:

button class=[...] ratingL ratingL-4.5

It seems to work in browsers, but I'd like to know if this character is valid 
and if it might have future implications if used that way.

Thanks,
Jens

Please consider the environment before printing this e-mail.

The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments.

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



RE: [WSG] Standards based Drupal WYSIWYG Editor

2010-02-28 Thread Sam Dwyer
I haven't had much of a look at the new CKEditor version but I was mightily 
impressed with the initial glance I had at it when he first released it. It 
looks like a *major* improvement on the original fckeditor. Cleaner code, more 
accessible and easier, cleaner ability to add plugins. If I was starting a new 
project that required a WYSWYG editor this would most certainly be the first on 
my list to evaluate.

I've spent the last couple of years wrestling with tinymce which used to be my 
editor of choice until I had to start writing proper plugins for it. It was an 
impressive offering 4-5 years ago and as a straight 'drop in' product it's 
still amazing, but given the leaps and bounds javascript has made in the last 
couple of years I simply can't recommend it anymore with a clear conscience. If 
you do know your way around javascript you'll find hacking tinymce to do what 
you want a frustrating experience. If you don't know your way around javascript 
then basically you won't be able to hack around under the hood of tinymce at 
all.

The only other editor I've looked at recently that I thought I'd be interested 
in was wymditor (http://www.wymeditor.org/) which is a 'what you see is what 
you mean' editor and may not be what some people require, but it is built on 
jquery (which should theoretically make extending it easier) and it does look 
quite nicely and cleanly done.

Hope some of that helps.

(Hi to the mailing list by the way, this is my first post since I joined, look 
forward to engaging with you all)

Cheers,
Sam Dwyer

Please consider the environment before printing this e-mail.

The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments.

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***