>It does take more time and effort for the programmer.
Even after the learning process is completed?
big help-thanks
kvnmcwebn
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.
> I spoke with programmers today.
> They were more receptive than i'd expected.
> They agreed give standards a go by
> easing into css based design one step at a time.
Tell those programmers we are ready for their questions. :-)
--
--
C Montoya
rdpdesign.com ... liquid.rdpdesign.com ... montoya.r
lop over time
while the programmers understand the importance and get used to working with
standard and accessible code.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of kvnmcwebn
Sent: Thursday, 3 November 2005 9:00 a.m.
To: wsg@webstandardsgroup.org
Subject:
props to everyone who provided feedback on this post earlier.
(regarding designing accessible sites
for non standards savy programmers to mark up)
I spoke with programmers today.
They were more receptive than i'd expected.
They agreed give standards a go by
easing into css based design one step
thanks for all the brillant feedback!
I will try putting a page or two through a screen reader for them.
Also I will show them how much easier it is to do a redesign with
a standards based website as they do this quite a bit.
On top of that a lot of thier contracts specify accesibility as a
require
> > That and clean XHTML is easier to hand-code than tables...
> Without wanting to open a can of worms here; how so? Do you mean in
> conjunction with CSS, or just that XHTML markup is cleaner than that of
> HTML?
Just that XHTML markup is faster to type by hand than nested tables
and font tags.
Paul Noone wrote:
That and clean XHTML is easier to hand-code than tables...
Without wanting to open a can of worms here; how so? Do you mean in
conjunction with CSS, or just that XHTML markup is cleaner than that of
HTML?
I read him to mean that any clean mark-up is easier to hand code tha
> hello all,
> Ive started designing sites for this company that specilizes in .net
> databases driven/xml feed type sites. I just give them a graphics file and
> they slice it up. Anyway they asked me yesterday if i could do this
> particular job with web accessability in mind. But heres the thin
> That and clean XHTML is easier to hand-code than tables...
Without wanting to open a can of worms here; how so? Do you mean in
conjunction with CSS, or just that XHTML markup is cleaner than that of
HTML?
**
The discussion list for http://web
> i dont know if i will be able to sell them on
> it. I was going to try the angle that web standards are helpful/essential
> for accessability-which they get alot of requests for these days. The
> programmers dont want me to do any coding or as little as possible-so as not
> to step on thier toes.
Quoting Mike Brown <[EMAIL PROTECTED]>:
> There's not at the moment. It would be great to have some, but I haven't
> any experience in captioning and not sure what's involved or how long it
> might take. Any volunteers? :)
Sadly I am about to leave the Australian Caption Centre but I would be mor
Leslie Riggs wrote:
We are hoping to have this available online as a Quicktime file soon.
When it is, it's definitely worth showing to people. Jonathan is a
wonderful speaker and funny speaker, and I guarantee that no one will
see his presentation and go away feeling the same about accessibil
Leslie Riggs wrote:
Um, I'm kind of afraid to ask, but would there be any captioning on that
for us poor deaf folk who won't hear this but do work for hearing clients?
Hmmm...should I fire up my SMIL-a-tron again? (which has been busy
recently...watch out for an announcement soon...)
--
Pat
We are hoping to have this available online as a Quicktime file soon.
When it is, it's definitely worth showing to people. Jonathan is a
wonderful speaker and funny speaker, and I guarantee that no one will
see his presentation and go away feeling the same about accessibility!
Mike
for Web S
Mark Harris wrote:
At a WSG meeting in Wellington, earlier in the year (see
http://www.gooduse.co.nz/thegoodnessarchives/000113.html), Jonathon
Mosen did a live demo of JAWS to an audience of web developers. Watching
the light bulbs go on as it read out an interminable database URL from
an Ama
Graham Cook wrote:
Having been in your position for some time until recently (I was standards
manager for Telstra), I found that the best way to achieve change toward
accessibility was to meet with the stakeholders and either take a
transcript, or play directly a Jaws readout of a page that had b
November 2005 10:10 AM
> To: wsg@webstandardsgroup.org
> Subject: RE: [WSG] standards, accessability and validation?
>
>
> > The programmers dont want me to do any coding or as
> > little as possible-so as not to step on thier toes.
>
> Don't just step, STOMP!
> The programmers dont want me to do any coding or as
> little as possible-so as not to step on thier toes.
Don't just step, STOMP! If they're not going to do their job right then let
it be known there is someone who can...and provide the reasons why. At the
end of the day, if it can save time and
Having been in your position for some time until recently (I was standards
manager for Telstra), I found that the best way to achieve change toward
accessibility was to meet with the stakeholders and either take a
transcript, or play directly a Jaws readout of a page that had been sliced
and diced
Having a validating vs non-validating site doesn't make much of a
difference in accessibility, as long as the errors are minor. What
-does- make a huge difference is semantic vs non-semantic. Having a
list marked up as a list but missing a (in a DTD that requires
it) it still much much more acce
Here's some things to think about that will keep accessibility in mind:
* resizable text (designer)
* sufficent contrast (designer)
* associate labels with form controls (designer/developer)
* meaningful link text (content owner)
* content chunks with good headings (content owner)
Accessibility d
> Seona Bellamy
> I know that there were some really good articles floating around on
> the list a while back when someone was asking how to sell web
> standards to clients.
MACCAWS is fairly nice http://www.maccaws.org/kit/
Just to give my GBP0.02 on the issue, I usually (unless clients
specifi
On 01/11/05, kvnmcwebn <[EMAIL PROTECTED]> wrote:
> Thanks seona and josh,
You're welcome. :)
> -thats a key point, i design with standards in mind but they've been slicing
> my ai files into a tables and calling it a day. I am meeting with them this
> week to talk about this. I will try and talk
Thanks seona and josh,
".although when they say "accessibility" they are probably thinking of
screen readers and users who can't use a mouse, accessibility also
includes being able to access the information and basic functionality
of a site in numerous browsing devices.
On 11/1/05, kvnmcwebn <[EMAIL PROTECTED]> wrote:
> hello all,
> Ive started designing sites for this company that specilizes in .net
> databases driven/xml feed type sites. I just give them a graphics file and
> they slice it up. Anyway they asked me yesterday if i could do this
> particular job w
On 01/11/05, kvnmcwebn <[EMAIL PROTECTED]> wrote:
> I told them that they need to start with
> web standards and get thier pages to validate before they start on
> accessability.
> Was that sound advice?
Well, while validation might not be seen as technically essential to
accessibility, I'd say th
26 matches
Mail list logo
