Re: [WSG] How do you cater to users with disabilities?
I am not part of this conversation and don't understand why I received this e-mail. Ted Knoy On Tue, Aug 23, 2011 at 11:11 PM, Julie Romanowski julie.romanowski.l...@statefarm.com wrote: Mike, maybe you should have worded your question a little differently. At my company, we don't approach accessibility as catering to users with disabilities, but we work toward making applications accessible to the greatest number of users possible. No application will ever be 100% accessible, but following standards and WCAG 2.0 guidelines helps us to get as close to 100% as possible. To answer your question - Sticking to standards is not enough. Accessibility and usability testing are critical. At my company, we have both an accessibility lab and a usability lab. We have accessibility and assistive technology (AT) experts onsite who test using various AT, and who work with actual AT users to identify issues with applications. We also train designers and developers to identify accessibility issues early in the design and development lifecycle. There are several other companies I know of that are doing the same and so much more, such as Adobe, IBM, Microsoft and Yahoo. As for developers not caring about people with disabilities, I disagree. There is a large community of developers who take accessibility seriously and are striving to make applications accessible to people with disabilities. -Original Message- From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Mike Kear Sent: Tuesday, August 23, 2011 2:54 AM To: wsg@webstandardsgroup.org Subject: RE: [WSG] How do you cater to users with disabilities? The conclusion I am coming to, with 5 days since I asked this and no-one actually saying they do ANYTHING to cater for people with disabilities, is that even after all this time, no one really spends much time thinking about users with special needs, other than to code to standards and hope that does the trick. No one either agreed or disagreed with the proposition that sticking to standards IS in fact enough. I asked this question, wondering if someone would say 'yes we have a usability lab' or 'we have a consultant who runs our sites through his screen reader for us' or 'we have meetings before launch specifically to discuss' or something. But no one has said they do anything at all for users with disability. The only responses I've had to this question are people referring me to documents on line that I found long ago with google. I was interested that none of the people who gave me those URLS (except Josh Street) said they actually used the advice in the documents themselves. Josh wasn't specific about how he caters to people with special needs, but seems to speak with some knowledge so I'm assuming he caters to Dyslexics in his designs. I guess it's going to take another law suit like that one against the Olympics2000 site to get anyone to take users with special needs seriously and actually lift a finger to cater to their needs. The conclusion I'm being forced towards is that developers are basically saying that users with special needs will have to swim for themselves and it's up to them to find some software of their own to get around all the obstacles the A/Bs put in their way. I'm glad at least property developers have been forced to change that attitude. Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion 9 Enterprise, PHP, ASP, ASP.NEThttp://asp.net/hosting from AUD$15/month -Original Message- From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Mike Kear Sent: Thursday, 18 August 2011 11:12 PM To: wsg@webstandardsgroup.org Subject: [WSG] How do you cater to users with disabilities? How to the rest of you a/b people (i.e. able bodied) cater to users with various forms of disability? Up until recently, I've tended to rely on keeping my code to standards, eliminating tables except for their proper purpose of tabulating data, and hoping that will give the accessibility level required. Do you go to the step of accessing your sites with JAWS or something similar to see how the site works for users with screen readers? I remember in the 1990s when I was working at Australian Consumers Association (choice.com.au) we had someone come and bring his PC with JAWS. The web team all sat in the boardroom getting ever more glum looks on our faces as we saw to our horror how terrible our new design was for this poor guy. We thought we'd got a terrific new design, and were about to launch it, when he did this demo for us. We had to go back and recode everything. This was before anyone was talking about standards though - it was back when the normally accepted method of laying out pages was to use tables, and buttons were nearly always images. I remember being
Re: [WSG] media queries can't understand body tag
My name is Ted Knoy and I have been receiving your company's e-mail for some time. I assume that this is confidential company information so I don't understand why I have been receiving your e-mail for nearly two months now. You should report this to Google or change your e-mail settings. On Thu, Sep 29, 2011 at 11:50 AM, tee weblis...@gmail.com wrote: Hi Hassan, Thank you for your patient. I did figure it after my post, from xcode's web inspector, a feature I never used before until today. From the this inspector I could see the difference from the one from Safari. Some people are kind and patience by nature (you), some never afraid to show his stupidity and ignorance publicly (I'm talking about myself), and some are snarky by nature, which is David :-) Luckily the world is big enough to for everyone. Tee On Sep 28, 2011, at 5:27 PM, Hassan Schroeder wrote: but I have never seen an article that tells how you can test what elements get loaded in the mobile Safari Maybe the third time's the charm -- Set up your test page and access it from your iOS device while *watching the server log*. Did the device request the image in question or not? Is there something confusing or ambiguous about that? -- *** 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] which tag to use for link to reference?
These e-mails aren't intended for me, but I keep on receiving them. Ted Knoy On Mon, Jul 2, 2012 at 10:52 AM, tee weblis...@gmail.com wrote: Thanks David. I think ePub3 and HTML5 support is still not here. When converting the HTML5 doctype files to ePub, Sigil (an ePub editor) forces ePub2 version and stripped all HTML5 tags. Converting to mobil format for Amazon Kindle is even worse, I feel as if dealing with the IE6 7. Tee On Jun 30, 2012, at 3:16 AM, David Dorward wrote: On 30 Jun 2012, at 11:04, tee wrote: I thought maybe I can use hyperlink for monolithic instead of adding 3 (which will be directed to Appendix), but this often is not desirable because in other sections of paragraphs where citations are used, there aren't alway clear sentences to hyperlink. A hyperlink (to an aside) is the closest thing HTML has AFAIK. This is for an ebook project, it's different from the webpage, and the readers are more accustom to the footnotes, but footnote doesn't work for ebook format, because devices' sizes vary, and portrait vs landscape view affects text flow too so strictly speaking there isn't pagination. The example syntax given in the EPUB specification[1] is: html … xmlns:epub=http://www.idpf.org/2007/ops; … p … a epub:type=noteref href=#n11/a … /p … aside epub:type=footnote id=n1 … /aside … /html [1] http://idpf.org/epub -- David Dorward http://dorward.me.uk *** 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 ***
Re: [WSG] HTML5 input type=date / and you
These e-mails aren't intended for me, but I keep receiving them.
Ted Knoy
On Mon, Jul 2, 2012 at 9:57 AM, James Ducker james.duc...@gmail.com wrote:
The only issue I've found so far is that Safari's implementation of the
date type sucks. It gives you little up/down chevrons which add or subtract
one day at a time. So my working code also treats Safari as
datepicker-not-implemented.
For me, as I make use of the valueAsDate property when it's available, it
made more sense to check its existence directly.
Also, Chrome's date picker is pretty annoying when you're trying to enter
DOBs. As far as I can see there's no quick way to jump forward/backward by
decades at a time.
On 2 July 2012 11:11, Patrick H. Lauke re...@splintered.co.uk wrote:
On 02/07/2012 01:55, James Ducker wrote:
element.valueAsDate
This property is designed to solve your locale woes, and it is also an
easy way to feature-detect a browser's native support for the date input
type. I haven't gone through all current browsers yet, so if you do use
this method, make sure to check that none of your browsers support the
property without implementing a date picker.
.valueAsDate, as you might have guessed, returns the input's value as a
Date object. Here's a super-simple feature detect:
if ( !myElement.valueAsDate ) {
// Implement my JavaScript datepicker
}
You can also simply test if the type of your input is reported as
date. Older browsers that don't implement the new HTML5 types simply fall
back to changing them - in the DOM itself - to type=text
if (!myElement.type === text) {
// fallback
}
--
Patrick H. Lauke
__**__**__
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com |
http://flickr.com/photos/**redux/http://flickr.com/photos/redux/
__**__**__
twitter: @patrick_h_lauke | skype: patrick_h_lauke
__**__**__
***
List Guidelines:
http://webstandardsgroup.org/**mail/guidelines.cfmhttp://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe:
http://webstandardsgroup.org/**join/unsubscribe.cfmhttp://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberhelp@webstandardsgroup.**orgmemberh...@webstandardsgroup.org
***
--
*James Ducker*
james.duc...@gmail.com
+61 404 838 470
***
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
***
