Re: [WSG] Multi Column Category Lists

2009-01-27 Thread Mustafa Quilon
I asked a similar question not too long ago:

http://archivist.incutio.com/viewlist/css-discuss/103365

-
Mustafa Quilon


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



Re: [WSG] Multi Column Category Lists

2009-01-27 Thread David Hucklesby
On Tue, 27 Jan 2009 19:29:52 +, James Jeffery wrote:
> Hey all,
>
> Quick question. I have some data pulled from a database (50 of the most recent
> categories/tags). These are positioned in a list in 2 columns (example below):
>
> -
> Category1Category5
> Category2   Category6
> Category3   Category7
> Category4   Category8
>

Quick answer -




Cordially,
David
--



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



[WSG] Help With My Front Page

2009-01-27 Thread Marvin Hunkin
Hi.
could some one take a look at http://tracs.co.nz/marvin
need help or show me how to fix maybe some possible layout and design, 
problems.
but cannot edit images, using jaws.
and maybe how to streamline my code.
so if some one has got the time and the expertise and can help me to get my 
front page working, then once got this working, then can transfer to my 
other pages, like copying and pasting code, and having similar design on all 
my other pages.
if any one can help, e-mail me off list.
cheers 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
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
***



Re: [WSG] Parenthesis around list counters

2009-01-27 Thread David Dixon
Either that or simply go down the PDF route and put the important  
legal information into a separate document.


I've found similar issues to this from legal teams who require a  
perfect translation from a word doc etc, and as Georg says, relying on  
individual browser support is often not acceptable (especially if  
regulatory bodies etc try to view them in a non fully compliant  
browser).


David

On 27 Jan 2009, at 19:25, Gunlaug Sørtun  wrote:


James O'Neill wrote:


We are a small county displaying our ordinances and parens are
important for legal notations and references.


If such details are important, they should be written in plain text.
Regardless of whether a method is found or not, one can not rely on
browsers support for HTML/CSS to "replicate importance" at such a  
level.


Simplest way to test if a method is acceptable or not for a particular
case, is to observe the outcome with CSS and script support off - in
Lynx for instance.

regards
   Georg
--
http://www.gunlaug.no


***
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
***



[WSG] Multi Column Category Lists

2009-01-27 Thread James Jeffery
Hey all,

Quick question. I have some data pulled from a database (50 of the most
recent categories/tags). These are positioned in a list in 2 columns
(example below):

-
Category1Category5
Category2Category6
Category3Category7
Category4Category8

Its important that these are listed in that order as they are alphabetical
going down the column.

Currently I split the results from the database, place them in an array, and
print 2 columns in separate lists. I was wondering if there is a way to do
it without creating 2 lists and do it with one. I have had a think and a
browse on google and couldn't find anything, so my last resort is to ask
here.

Ideas?


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

Re: [WSG] Parenthesis around list counters

2009-01-27 Thread Gunlaug Sørtun

James O'Neill wrote:


We are a small county displaying our ordinances and parens are
important for legal notations and references.


If such details are important, they should be written in plain text.
Regardless of whether a method is found or not, one can not rely on
browsers support for HTML/CSS to "replicate importance" at such a level.

Simplest way to test if a method is acceptable or not for a particular
case, is to observe the outcome with CSS and script support off - in
Lynx for instance.

regards
Georg
--
http://www.gunlaug.no


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



[WSG] Parenthesis around list counters

2009-01-27 Thread James O'Neill
Greetings all,
I am curious if it is currently possible to have a list item display its
list counter with parenthesis around it such as this:

 1. Item 1
   (a). sub item 1

The only way I can think of this is via CSS 3 which is not currently widely
supported, especially in our IE6/7 audience.
Does IE7/8 support this? Would implementing Deans IE7 help? Any other
thoughts on solving this?

We are a small county displaying our ordinances and parens are important for
legal notations and references.

Thanx

Jim
__
"All for one and one for all."

www.ArionsHome.com (Persona BLog)
www.FreeXenon.com (Web Site Consulting)
www.ItsAllAboutYou-Studio.com (Our Yoga Studio)


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

Re: [WSG] How to hide/show form questions with javascript while meeting WCAG 2?

2009-01-27 Thread Benjamin Hawkes-Lewis

On 27/1/09 05:19, littler...@internode.on.net wrote:
> I am starting to learn javascript/jquery and would like to use it to
> hide questions on a form dependant on the answer to another question.

Hmm. Can we explore the precise interaction a little bit more before 
jumping to solutions?


How will the same transaction be handled when JavaScript is unavailable, 
if at all?


If a user was to see all the questions all the time, would they still 
understand the form?


If not, would they understand the form if the wording of the questions 
was altered a bit?



I have seen plenty of working examples but am concerned that they
wouldn't be accessible or comply with WCAG 2.0.

Does anyone have an example of best practice or can advise on how
they deal with this issue?


There are three basic approaches to "hiding" and "showing" things that 
you should choose between based on the core WCAG principles 
(perceptibility, understandability, operability, robustness):


1. DOM mutation: remove elements from the DOM (removeChild, or 
innerHTML), store them in a variable, and then add them again later 
(appendChild/insertBefore, or innerHTML). In theory, this should "hide" 
things from all users. It's the most appropriate approach when the 
document would be nonsensical if the elements continued to be shown to 
the user.


2. "display" method: suggest that the elements are styled with "display: 
none;". In theory, this should "hide" things from any user from any 
users that are using user agents that support CSS (not all do), that are 
not rejecting publisher styles (some do), and that are not overriding 
that style. This is the most appropriate approach when the document 
would be understandable even if the elements continued to be shown to 
the user, but hiding them simplifies or prettifies the content.


3. Off-screen method: Suggest that the elements are styled so as to be 
positioned off-screen (e.g. "left: -9px; position: absolute;"). In 
theory this should "hide" things from any sighted users that are using 
user agents that support CSS (not all do), that are not rejecting 
publisher styles (some do), and that are not overriding that style. This 
is the most appropriate approach when the document would be 
understandable if the elements continued to be shown to the user, and 
hiding them from sighted users applying CSS simplifies or prettifies the 
content for those users, but the content must be shown to any group of 
users who are visually impaired or whose user agent or configuration 
does not apply that CSS.


A gotcha with techniques 1 and 2 is that assistive technology may not 
refresh its "buffer" or "cache" of the DOM immediately and so may not 
reflect your dynamic changes when representing your content to the 
end-user. Testing is crucial here. See also:


http://juicystudio.com/article/making-ajax-work-with-screen-readers.php

http://juicystudio.com/article/improving-ajax-applications-for-jaws-users.php

http://www.gwmicro.com/blog/index.php/all/?title=regarding_web_based_dynamic_content&more=1&c=1&tb=1&pb=1

http://wiki.codetalks.org/wiki/index.php/How_to_use_ARIA_Live_Regions_for_dynamic_content

http://www.paciellogroup.com/blog/?p=65

A gotcha with techniques 2 and 3 is that you must ensure that if a 
"hidden" element receives keyboard focus (whether by pressing an 
"accesskey", or moving through the tab order, or jumping to an element 
of a particular type, or being sent there dynamically), either focus 
must be automatically passed on to a visible element or the element must 
be made visible. ("focus", "blur", "DOMFocusIn" "DOMFocusOut", 
"focusin", and "focusout" UI events and ":focus" and ":active" 
pseudo-classes are the key tools at your disposals here.) Otherwise, the 
keyboard focus indicator will be hidden. That would be confusing to 
sighted keyboard users and a WCAG2 violation:


http://www.w3.org/TR/WCAG20/#navigation-mechanisms-focus-visible

Most JavaScript for "hiding" and "showing" content actually uses the 
"display" method, because it's easy, even when it's arguably 
inappropriate. A frequent mistake of this sort is to send the client an 
HTML form with error messages embedded directly in the HTML and styled 
with "display: none;", which are then styled "display: block" if a field 
fails form validation. This breaks horribly when your styling 
suggestions aren't applied, because the user will be confused by error 
messages that do not reflect actual input.


Hope that helps.
--
Benjamin Hawkes-Lewis


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



RE: [WSG] How to hide/show form questions with javascript while meeting WCAG 2?

2009-01-27 Thread Chris Taylor
Toggling the visibility of elements while respecting accessibility is one of 
the features of Performer (http://performerjs.org). A new site is currently in 
the works with much better documentation, but if you’re interested in using 
this drop me a line off-list and I’ll be glad to help.

Chris



From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of littler...@internode.on.net
Sent: 27 January 2009 05:19
To: wsg@webstandardsgroup.org
Subject: [WSG] How to hide/show form questions with javascript while meeting 
WCAG 2?

Hi everyone,

I am starting to learn javascript/jquery and would like to use it to hide 
questions on a form dependant on the answer to another question. I have seen 
plenty of working examples but am concerned that they wouldn't be accessible or 
comply with WCAG 2.0.

Does anyone have an example of best practice or can advise on how they deal 
with this issue?

The websites I have been looking at include:
http://www.quirksmode.org/dom/usableforms.html
http://www.frinity.com/posts/css/show-hide-form-field-selecting-a-radio-button-option

Thank you,
~Rachel

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

Click here to report 
this email as spam.


This message has been scanned for malware by SurfControl plc. 
www.surfcontrol.com

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