RE: [WSG] Re: Use of Fieldsets other than in form?

I totally disagree with Lucien. It's nonsensical to suggest you can just ignore parts of a sentence that you find inconvenient. The definition is totally unambiguous - it states "group thematically related controls and labels", not "group thematically related content such as controls and labels".

RE: [WSG] Re: Use of Fieldsets other than in form?

Jackie, you said "I really didn't want a whole load of div classes with headers & p tags etc churned out repeatedly down the page". Why not? It is clearly the most appropriate way to mark up that content. And what would the use of fieldsets change? You would still have the same quantity of markup e

RE: [WSG] Re: Use of Fieldsets other than in form?

I can't generalise about screen readers, but JAWS would read the legend as if it were any other paragraph i.e. it would not differentiate it from the other text in the way it does with headers. The user may or may not work out for themselves that it is the start of a new section of content. JAWS'

RE: [WSG] What does Semantic mean?

JAWS reads legends in 'virtual cursor mode' and in 'forms mode' but it reads them differently in the two modes. In 'virtual cursor mode', which is the normal mode of operation for websites and PDFs, it will simply read the legend when it reaches that element. It does not announce the element type

[WSG] JAWS Screen Reader Demo - Monday 25 June 2007

want to come early. We are scheduled to finish at 5:30pm but you are welcome to stay afterwards to get some hands-on experience or look at some more websites. If anyone would like to attend this demo or a future one please fill in the form at http://www.accessibility.co.uk/free_jaws_demo.htm. Steve

RE: Accessible auto-submit dropdowns [WAS: Re: [WSG] WCAG Samurai Errata]

Internet Explorer users can use Alt+Down Arrow to open the SELECT element and then use the arrow keys to navigate within it without triggering the onChange event. One of our JAWS users does this as a matter of course for every combobox because he cannot know if they have an onChange event attached

RE: [WSG] WCAG Samurai Errata

The Samurai Errata have no official status so there are no certificates or validators. They have "authority tone" because that's Joe Clark's style, not because they have any authority. They are some good ideas written by some clever people (or one clever person if you believe some of the theories).

RE: [WSG] Screen Reader Accessible Navigation Suggestions

That's not a big site so I would expect that two lists for the primary and secondary navigation would be sufficient. Use a third list if you need a third level of navigation. I would advise against nesting the second and third level navigation lists, which is what people often do. It may be semanti

RE: [WSG] Screen Reader Accessible Navigation Suggestions

[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Green Sent: Wednesday, June 13, 2007 1:50 PM To: wsg@webstandardsgroup.org Subject: RE: [WSG] Screen Reader Accessible Navigation Suggestions That's not a big site so I would expect that two lists for the primary and secondary

RE: [WSG] Usability & Accessibility Over Design?

I would like to agree with you Joe but I currently have a battle with several design agencies who work for a multinational client of ours. Historically they have produced websites that are predominantly Flash-based or sliced and diced from PhotoShop. Our client wants to achieve WCAG AA and the agen

RE: [WSG] Usability & Accessibility Over Design?

Our customer is one of the largest corporations in the world. They have several hundred brands, each of which is valued at upwards of $100M. Most of these brands are many decades old and have historically been advertised in traditional media such as print, TV, billboards etc. Style is everything, p

RE: [WSG] Usability & Accessibility Over Design?

"Explain to them how much more money they can make..." Just how much can they make? Where's the proof? That's what they always ask and that's what we can't answer. There are no plausible case studies to support this. It's pure conjecture. Yes I do know about the Legal & General case study but so m

RE: [WSG] Usability & Accessibility Over Design?

The http://www.fosterandpartners.com is not a good example at all. I can see at a glance that it violates at least three WCAG Priority 2 checkpoints, and that's without even looking at the code. Some pages violate Priority 1 requirements too. That's a shame because I really need stunning examples

RE: [WSG] Usability & Accessibility Over Design?

I am one of Accessites' partners, so I am very familiar with the Showcase. There are certainly some very good sites there, but in the 18 months or so that the site has been live only 5 have achieved the Classic rating and none has achieved the top rating of Timeless. The 5 Classic sites are very g

RE: [WSG] IE & help

I have IE7 on Windows XP SP2 and all the Zip files download ok. Some of them contain Word documents, and the machine opens these in WordPad because I don't have Word on it. I get the error message "Unable to load graphics conversion filter", which is probably to be expected. The document still open

RE: [WSG] Accessible Adobe Photoshop and flash With Jaws

One of our trainers tells me that only 4% of blind people have no sight at all. Some may not be able to see a few feet in front of them and need a guide dog to walk up the street, yet they can see a screen close-up and may not even need a screen reader (although they would probably benefit from usi

RE: [WSG] Levels of 508 compliance

http://www.w3.org/TR/WCAG10/full-checklist.html contains a checklist. This page links to others that explain the individual checkpoints in more (but not necessarily adequate) detail. http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web Checkpoints a. to k. correspond directly to WCAG

RE: A: [WSG] Target Lawsuit - Please Make Yourself Heard

I find it hard to believe I'm reading this in the WSG. The Target website is truly appalling - we use it to illustrate some the worst possible design practices when we run training sessions. It discriminates against anyone who has to use a non-graphical user agent (not just blind people), and this

RE: A: [WSG] Target Lawsuit - Please Make Yourself Heard

I think you'll find the people of Tibet didn't build Mount Everest and weren't even able to influence its design. Target chose to design their site the way they did, and a professional designer would have known that they were excluding some people from using the website. In the face of such wilfu

RE: A: [WSG] Target Lawsuit - Please Make Yourself Heard

Because it was explicitly designed to be accessible. And because it is relatively easy and the incremental cost is small. As it happens, a Braille version of a publication is one of the least useful things you can do. In the UK only 2% of registered blind people read Braille. However, many have a

RE: A: [WSG] Target Lawsuit - Please Make Yourself Heard

"can anybody help me understand where the idea that accessibility costs money comes from?" It certainly can do depending on the content of your site and the target audience. I would concede that it probably doesn't cost more to produce a standards-compliant static website (i.e. has semantic struct

RE: A: [WSG] Target Lawsuit - Please Make Yourself Heard

"I suspect that this lawsuit was premature" The WCAG were published 8 years ago. How long should we wait? I don't know when Section 508 came into law but the UK's DDA was passed in 1995. Seems like long enough to me. "But if this judge's decision becomes du jour..." It won't. Courts will assess

RE: A: [WSG] Target Lawsuit - Please Make Yourself Heard

eph Ortenzi Sent: 04 October 2007 12:16 To: wsg@webstandardsgroup.org Subject: Re: A: [WSG] Target Lawsuit - Please Make Yourself Heard Sorry I have to disagree some of these points. Comments among your text >> On Oct 04, 2007, at 01:56, Steve Green wrote: > "can anybody help

RE: [WSG] Cost of Accessibility

"The cost of adding accessibility should really be zero." Statements like this illustrate a total lack of understanding that I am dismayed to encounter in this group. Standards compliance does not equal accessibility. It's just one part of it, and arguably the easiest part. "As a designer/develo

RE: [WSG] Cost of Accessibility

It is, but compliance with the WCAG doesn't automatically guarantee an accessible site, so my statement stands. To build websites that are truly accessible it is necessary to understand how people perceive the content and interact with it. The WCAG are a good start but they only get you so far. St

RE: [WSG] Cost of Accessibility

http://www.dave-woods.co.uk [EMAIL PROTECTED] On 08/10/2007, Steve Green <[EMAIL PROTECTED]> wrote: > "The cost of adding accessibility should really be zero." > > Statements like this illustrate a total lack of understanding that I > am dismayed to encounter in this gr

RE: [WSG] source order

The only research on this was on a tiny number of screen reader users (18 as I recall) and they had a very slight bias towards haing the navigation first. However, there were differences between people of differing ability. Experienced users tended to just deal with whatever was thrown at them, whe

RE: [WSG] source order

Another thought. Are you planning to position the navigation at the top of the page even though it is at the end of the source? If so, I would say unequivocally that is the wrong thing to do. This will adversely affect anyone who uses keyboard navigation, because the tab sequence will not be anyth

RE: [WSG] source order

"i wonder how many people using screen readers ever make it down there to the footer/copyright" In my experience they often do, although that's not because they are looking for it. Remember that a screen reader user has no idea how long a page is until they get to the end. They may be one line fr

RE: [WSG] Which screen reader to test with?

This raises several issues. Firstly, screen readers are not all the same, so you cannot test with one and assume the others will work just as well. Some announce the presence of some semantic structure, some don't announce any at all and some (I'm thinking primarily of Firevox) announce too much. T

RE: [WSG] Title attribute and screen readers

I use keyboard controls a lot too, and generally regard the use of tabindex as a sign that a site was not designed properly in the first place. It causes a number of problems such as being unable to predict where the focus is going to go next. How can the designer predict what the user will want to

RE: [WSG] Minimum width help

visibility: hidden does hide the content from screen readers the same as display:none does. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Woods Sent: 24 October 2007 22:04 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Minimum width help Actual

RE: [WSG] skip to content: care of accessibility causing usability

"Most disabled users, particularly sight impaired, will use your header markup to navigate the page rather than skip links" Really? How will they do that? And what makes you believe that this is the case? "...an accessible browser like Firefox which allows them to display a header list..." No it

RE: [WSG] Skip nav links, tab through

There's no reason why you shouldn't be able to tab through the links in Firefox. Links are not on the tab sequence in Safari by default, but you can turn that on in the Preferences. I have no idea if users actually do in practice. Steve -Original Message- From: [EMAIL PROTECTED] [mailt

RE: [WSG] AccessResearch // Page Check

People with assistive technologies rarely benefit from 'title' attributes. They are not displayed by text browsers, they are not accessible using keyboard navigation (or devices that emulate keyboards) and they are not read by screen readers with default settings. They are only accessible to someon

RE: [WSG] AccessResearch // Page Check

they are the minority". Every user counts. If a user wants to magnify the screen there are alternative methods for making link text bigger, there is no alternative method for a user to make sense of link text. James On Nov 18, 2007 5:44 PM, Steve Green <[EMAIL PROTECTED]> wrote: &g

RE: [WSG] Iframe navigation accessibility question

The accessibility issues relating to frames are often overstated, although they can cause difficulties with user agents that only support one window, such as Lynx. You can usually still use the site but it is not as convenient because you have to keep going back to the list of frames in order to ac

RE: [WSG] SIte Maps?

Not at all. You know that the site only has 15 pages but your visitors don't. The sitemap gives the visitor an immediate indication of the size of the site, so why deny them that? It can be a big help in determining their strategy for browsing the site. Steve -Original Message- From: [

RE: [WSG] Accessible likert scale (disagree/agree/strongly agree/etc) forms

I don't recommend that solution. We have tested this kind of form with a highly proficient screen reader user, and he could not understand it at all. In fact it was one of the few tasks he has ever failed to complete. This is one of those cases where marking up content so it is semantically correct

RE: [WSG] Accessible likert scale (disagree/agree/strongly agree/etc) forms

The problem with the code below is that the content of the will be read before every . That makes it very difficult for a screen reader user to read it fast. I would just have the question in a or possibly even a header element. Once the user has read through a few questions and realises that th

RE: [WSG] Accessible likert scale (disagree/agree/strongly agree/etc) forms

Undoubtedly it's the cleanest way to achieve the required functionality, and there are fewer accessibility issues. However, it is less easy for a user to quickly review their answers because they have to read the text rather than just look at the physical position of the selected radio button. Als

RE: [WSG] Accessible likert scale (disagree/agree/strongly agree/etc) forms

ey will be able to navigate quickly. Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patrick H. Lauke Sent: 04 December 2007 00:00 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Accessible likert scale (disagree/agree/strongly agree/etc) forms S

RE: [WSG] Article: "Vocalize Firefox" (text-to-speech extensions for Firefox)

A year ago I started to evaluate FireVox 2.6 and had a dialog with Charles Chen, its creator. At that time there is no way I would describe it as "full-fledged screen reader" as it had many shortcomings. I got the impression it was really just a hobby project, and Charles said he had pretty much a

RE: [WSG] Article: "Vocalize Firefox" (text-to-speech extensions for Firefox)

A year ago I started to evaluate FireVox 2.6 and had a dialog with Charles Chen, its creator. At that time there is no way I would describe it as "full-fledged screen reader" as it had many shortcomings. I got the impression it was really just a hobby project, and Charles said he had pretty much ab

RE: [WSG] Article: "Vocalize Firefox" (text-to-speech extensions for Firefox)

would it compare for a developer that is making an effort to correctly mark up their html just to get an impression of how it would work for a screen reader user? Steve Green wrote: > A year ago I started to evaluate FireVox 2.6 and had a dialog with > Charles Chen, its creator. At that time

RE: [WSG] jaws (ot?)

Read the license terms - they are very clear. You can only use the demo version to help you assess whether you are going to purchase the full version. Nothing else. You explicitly cannot use the demo version for testing your websites. Once you have decided that you are not going to purchase the

RE: [WSG] semantic list with explanations

I think that definition lists would be appropriate semantically but in the real world I don't know of any user agent that does anything useful with a definition list or any user group that derives any benefit from them. Certainly they make no sense when read with a screen reader because you cannot

RE: [WSG] semantic list with explanations

ogic, we should be using basic table markup for layout to give people using old visual browsers a better experience. If we cheat with the markup to please user agents what's the incentive for SR manufacturers to take care of the problem? -- Regards, Thierry | http://www.TJKDesign.com

RE: [WSG] semantic list with explanations

The desire for semantic purity is only one of many factors when deciding how to mark up a page. Other factors include (but are not limited to) UA support, the user experience, the time available to implement the design and the expected life of the website. I would expect a professional designer to

RE: [WSG] standards-compliant designers

Of course I made up that 1% figure but I don't suppose it's far out. Just look at the phenomenal number of crap websites out there. There are something like 100,000 people offering web design services in the UK (10,000 in London alone) yet GAWDS membership (which is global) is only around 500 and I

RE: [WSG] semantic list with explanations

I have a big problem with the term 'best practice', especially when it is used to effectively terminate a discussion. It implies that not only is there currently no better solution, but that there never will be. I believe that the most appropriate solution invariably depends on the context, and fi

RE: [WSG] semantic list with explanations

19 To: wsg@webstandardsgroup.org Subject: RE: [WSG] semantic list with explanations > On Behalf Of Steve Green > > I have a big problem with the term 'best practice', especially when it > is used to effectively terminate a discussion. It implies that not > only is ther

RE: [WSG] Test Plans

documentation. I have many other resources that may be useful so I'll contact you off-list. Steve Green www.labscape.co.uk _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Jeffery Sent: 15 January 2008 12:09 To: wsg@webstandardsgroup.org Subject: [WSG] Test Pla

RE: [WSG] Test Plans

ans I'd love to see the stuff online. I think this is a very important part of web standards. QA should not be an afterthought but an integral part of the process. Michael Horowitz Your Computer Consultant http://yourcomputerconsultant.com 561-394-9079 Steve Green wrote: > When yo

RE: [WSG] long description and its implementation

Such as? JAWS (which has something like 50% market share) has a high level of JavaScript support and I believe that the other professional screen readers (WindowEyes and HAL/SuperNova) also do. Free and cheap screen readers generally don't have JavaScript support. In our experience screen reader

RE: [WSG] long description and its implementation

fused. Do they usually have Flash installed? I thought that screen readers would default to whatever is suppose to be replaced with the Flash when using SWFObject. Maybe it defaults because the Flash isn't enabled... Though, I guess that could be wrong as well. Steve Green wrote: > Such

RE: [WSG] long description and its implementation

Subject: RE: [WSG] long description and its implementation Quoting Steve Green <[EMAIL PROTECTED]>: > Screen readers do not read Flash content that is embedded using > unobtrusive techniques such as SWFObject. I expect they would read the > content that is supposed to be repla

RE: [WSG] long description and its implementation

: RE: [WSG] long description and its implementation Quoting Steve Green <[EMAIL PROTECTED]>: > Screen readers do not read Flash content that is embedded using unobtrusive > techniques such as SWFObject. I expect they would read the content that is > supposed to be replaced, b

RE: [WSG] long description and its implementation

; [mailto:[EMAIL PROTECTED] On Behalf Of Steve Green > Sent: 04 February 2008 14:23 > To: wsg@webstandardsgroup.org > Subject: RE: [WSG] long description and its implementation > > I checked www.salford.ac.uk with JAWS 7.10 and 9.0, and neither of > them see either the linked

RE: [WSG] Styling forms

There may be specific cases where it would be right to mark up a form as a list, although I can't think of one. As a general rule it would be wrong. The argument against marking up a form as a list is that a form is not a list. A form is one or more groups of form controls, and the fieldset elemen

RE: [WSG] an accessible question: server-side vs client-side validation

In my experience client-side validation works fine with screen readers but you need to be careful how you present any error messages. It is increasingly common to see them slid in silently, and this is a big problem not only for screen reader users but also for magnifier users because they are both

RE: [WSG] PDF Accessibility

PDFs can be more accessible than was previously possible but there are lots of gotchas, and it's way too big a topic to cover in this reply. Note that by default, PDFs are not tagged, so they are only marginally more accessible than before. Maximum accessibility is obtained by tagging them, but tha

RE: [WSG] re: generate data

"Accessibility, though in a sense is trivially easy once you know it" That would not even be true if it was possible to 'know it', which it isn't. Accessibility isn't just a bunch of facts that you have to learn, and it's not just about compliance with the WCAG checkpoints. That's a good starting

RE: [WSG] Web Browser Testing and the Practicality of Testing other OSs

This kind of testing is our core business, and I have to say that these days there is very little difference when running a particular browser version on different Windows versions. One difference that comes to mind is that Windows 2000 has native 56-bit encryption, and this is not increased even

RE: [WSG] The correct way of placing a swf file into a XHTML webpage

No it can't. Flash content that is embedded using techniques such as UFO and SWFObject is not visible to screen readers - they don't even know it's there. If the content is important, you need to provide an accessible alternative. It need not necessarily be visible on screen, and it is common to hi

RE: [WSG] nest heading properly

During user testing I have not seen this cause any problems, particularly when only one level is skipped. It is certainly odd when you jump from an or to an or , but users generally take even extreme cases like this in their stride (yes, we do come across sites like this!). In general, coding te

RE: [WSG] Rogue text appears in IE6.

It's the well known IE6 duplicate text bug. http://www.positioniseverything.net/explorer/dup-characters.html _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Enslin Sent: 03 April 2008 10:51 To: wsg@webstandardsgroup.org Subject: [WSG] Rogue text appears in IE6.

RE: [WSG] accessibility and brower compatibility for Kiosk mode?

-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 17 April 2008 15:36 To: wsg@webstandardsgroup.org Subject: RE: [WSG] accessibility and brower compatibility for Kiosk mode? >Please help me with another question, with multiple li

RE: [WSG] The Problem of adjacent links

The rationale for this checkpoint seems to have been long forgotten, and I don't know of any user agent that has a problem with adjacent links. Nor does anyone else it seems, which is why the WCAG Samurai recommended that the checkpoint should be ignored. It certainly isn't a problem for any scre

RE: [WSG] Firefox 3 candidate

You can still get some old versions from the Mozilla FTP site at http://releases.mozilla.org/pub/mozilla.org/firefox/releases/ It's ludicrous that they have removed some old versions - can they really not afford the disk space? Obviously users should not be installing old versions but developers

RE: [WSG] Browsers and Zooming

"I have never encountered a friend, family member or other "civilian" who has a problem scrolling in either direction if necessary." A horizontal scrollbar does not prevent users from accessing content but it reduces the efficiency with which they can do so. Not only does zooming introduce the hor

RE: [WSG] Browsers and Zooming

Well here's a guy who has done a bit of usability testing. To quote from the article: "We know from user testing that users hate horizontal scrolling and always comment negatively when they encounter it". http://www.useit.com/alertbox/20050711.html Of course he could be entirely wrong but I don'

RE: [WSG] ADA Compliant Flash

accessibility tester / consultant. This is a mid-level to senior position based on London and I am offering a substantial finders fee for anyone who can introduce a candidate that we recruit. Full details are available on request. Steve Green Labscape www.labscape.co.uk -Original Messa

RE: [WSG] ADA Compliant Flash

Thanks for the clarification Dennis. If it turns out that ADA does cover websites, what would be the test for compliance? Or is it likely to be similar to the DDA in the UK, which is concerned with actual outcomes rather than a technical standard? Under the DDA it doesn't matter if a website is AA

RE: [WSG] Reverting to older version of flash for testing purposes.

You can get an uninstaller from the Adobe website - http://www.adobe.com/support/flashplayer/downloads.html#uninstaller You can get every old Flash version at http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_14266

RE: [WSG] Shopping cart - who does what

On Aug 14, 2008, at 3:09 AM, Krystian - Sunlust wrote: >> > > It costs £300 man, I would prefer to get an open source solution, > community > paid support. Try getting support from Magento, likely £300 is comparably very inexpensive, considering that commercial software ought to give you suppo

RE: [WSG] Shopping cart - who does what

I thought that "UK DDA" is based on the WCAG AA guideline no? One time I did a template coding for a UK company, and was asked to follow WCAG AA guideline. As for Section 508, my impression is that, despite the additional requirements, it doesn't even quite meet the WCAG A. In the early years of

RE: [WSG] Shopping cart - who does what

Thanks Steve for the clarification. OK, in the risk of showing more ignorant, I still have question. My understanding on WCAG guidelines, are the fundamental principle of DDA, Section 508 and similar law in other countries correct? When a website is to be DDA or Section 508 compliant, for lack

RE: [WSG] Google chrome... Accessibility coming very soon???

Yes, this is the case. There has been a lot of talk about this in GAWDS, and Steve Faulkner has written about it at http://www.paciellogroup.com/blog/?p=92. Basically it looks like there's no MSAA support. If they don't address this, many large organisations (at least in the UK) will not use it. I

RE: [WSG] Google chrome... Accessibility coming very soon???

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Martin Sent: 04 September 2008 23:33 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Google chrome... Accessibility coming very soon??? Hey guys... it is great that talk about accessibility and chrome has been raised - but I do

RE: [WSG] Looking to source a JAWS version

w the software is used, but how screen reader users create a mental model of web pages and the strategies they use for navigating within them. Without that knowledge there is little value in doing the testing yourself. Steve Green

RE: [WSG] WCAG2 in general

Further to the discussion regarding WCAG 2.0 in government, I am interested in the reasons why organisations are or are not choosing to adopt WCAG 2.0. Would anyone care to share their thoughts? Are you adopting it just because it's new and presumably better? Or have you reviewed it thoroughly and

RE: [WSG] Fieldsets & Legends

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 03 October 2008 10:03 To: wsg@webstandardsgroup.org Subject: [WSG] Fieldsets & Legends Hi, I'm trying to educate developers to add fieldsets and legends to their code when building applications. Jaws 5.0 ha

RE: [WSG] Big Browsing Issues on clients PC Laptop AOL

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Pennell Sent: 18 October 2008 20:22 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Big Browsing Issues on clients PC Laptop AOL On Sat, Oct 18, 2008 at 7:19 PM, Kristine Cummins <[EMAIL PROTECTED]> wrote: I just laun

RE: [WSG] Text-only version

Betsie does a lot more than just display the page without styles. It was designed to improve the accessibility of the crappy websites that were the norm a decade ago, and it is less useful on a website that is coded properly but it still has some value. The technical spec is at http://www.bbc.co.uk

RE: [WSG] Text-only version

EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patrick H. Lauke Sent: 20 November 2008 20:54 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Text-only version Steve Green wrote: > You can do a lot of what Betsie does using CSS but the one thing you > can't do is replace

RE: [WSG] Text-only version

t: 20 November 2008 21:07 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Text-only version On Thu, Nov 20, 2008 at 3:40 PM, Steve Green <[EMAIL PROTECTED]> wrote: > > You can do a lot of what Betsie does using CSS but the one thing you > can't do is replace the images wi

RE: [WSG] Text-only version

ssage- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Dorward Sent: 20 November 2008 21:06 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Text-only version Steve Green wrote: > You can do a lot of what Betsie does using CSS but the one thing you > can't d

RE: [WSG] Text-only version

hristian Montoya Sent: 20 November 2008 21:33 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Text-only version > On Thu, Nov 20, 2008 at 3:40 PM, Steve Green > <[EMAIL PROTECTED]> > wrote: >> >> You can do a lot of what Betsie does using CSS but the one thing yo

[WSG] jQuery problems

I would be grateful if any JavaScript (specifically jQuery) experts could contact me off-list as I have a client who needs some remedial work done (for which they will pay). Also are there any more suitable places I could post this request? Steve

RE: [WSG] the Name attribute

Stuart's point is that blinking content violates checkpoint 7.2 of the W3C Web Content Accessibility Guidelines: "Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off)" Steve -Original Mes

RE: [WSG] jquery ui.slider keyboard navigation question

It is understood that some tasks will require two keys, such as Alt + down arrow to open a combobox. I presume you are testing on a Mac because I see slightly different behaviour than you describe in Windows browsers. In both Internet Explorer 6 and Firefox 2.0 the arrow keys alone are sufficient

RE: [WSG] credibility of accessibility validator and evaluator

Accessibility validators should make it very clear where a checkpoint is required by a standard (in which case they should provide a reference so you can check the precise wording) and where it is 'best practice' (according to who?). In this case the 'failure' is not a non-compliance with any stan

RE: [WSG] embedding quicktime .mov cross-platform

I don't allow QuickTime to be installed on any of our machines either. Is there a reason why you can't use a file format that has a larger installed user base? Most non-Mac users won't have QuickTime. Steve -Original Message- From: li...@webstandardsgroup.org [mailto:li...@webstandards

RE: [WSG] a WCAG 2.0 question

It's not just screen readers that have problems with new windows. Every user group we have tested with has had problems. Screen reader users sometimes do not notice that the screen reader has announced the opening of a new window. Screen magnifier users frequently cannot tell that a new window has

RE: [WSG] add to favorites?

It's not just replicating browser functionality - it's a call to action. As such I think it's perfectly reasonable. Steve -Original Message- From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Patrick Lauke Sent: 25 March 2009 13:36 To: wsg@webstandardsg

RE: [WSG] add to favorites?

From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Andrew Maben Sent: 25 March 2009 15:18 To: wsg@webstandardsgroup.org Subject: Re: [WSG] add to favorites? On Mar 25, 2009, at 10:10 AM, Steve Green wrote: It's not just replicating browser function

RE: [WSG] add to favorites?

-Original Message- From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Stuart Foulstone Sent: 25 March 2009 16:19 To: wsg@webstandardsgroup.org Subject: RE: [WSG] add to favorites? This list is aware of many "marketing practices" that are against Web Sta

RE: [WSG] Image Replacement and Accessabilty

-Original Message- From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]on Behalf Of Christopher Kennon Sent: 15 April 2009 01:40 To: wsg@webstandardsgroup.org Subject: [WSG] Image Replacement and Accessabilty Hi All, The text indent CSS property can render an h# eleme

RE: [WSG] The weirdest IE bug I've ever encountered.

Actually he won't see a bug free site at all. Correcting the doctype and other issues makes no difference. The bug does not occur in Internet Explorer 6. Something like this has been reported previously but the only references I can find are not directly applicable to this situation. http://foori

  1   2   >