Accesibility article

[Monte Gardner]

I'm teaching a class on web authoring and html. I'm trying to find a
good reading article on accesibility issues. I'm trying to keep the
reading supplements to relatively light reading, so I don't want to
just point my students to the W3C's Web Accessibilty Guidline articles
(a little to heavy reading). Can any of you suggest an online article
out there that will explain why you need to think about accesbility and
some basic ideas on how to achieve it?

[Dan]

I discuss some related issues in my Web Tips site:
http://webtips.dan.info/

--
Dan

[Alan J. Flavell]

On Mon, 13 Dec 2004, Monte Gardner wrote:

I'm teaching a class on web authoring and html. I'm trying to find a
good reading article on accesibility issues. I'm trying to keep the
reading supplements to relatively light reading,
Oh dear. You ask what appears to be a plausible enough question, but
there's no simple answer. Well, I'd say there -is- a simple answer -
when you know that it is, and are receptive to it. But most of the
folks learning HTML will come to it with a ballast of preconceptions
that prevent them being receptive to it. Un-learning preconceptions
is, by experience, /far/ harder than learning completely new stuff.

There are quite a few contributors here whom you could learn from, but
you'd need to follow the discussions rather than popping up and asking
an apparently simple question...

As for my own inept contributions, I was tidying-up some files last
night and stumbled across a half-year-old half-written critique of a
course guide that I found for a supposedly "advanced" course in web
page design.[1]

There's a posting based on it, archived by goo-gropes at
http://groups.google.co.uk/groups?se...6.ph.gla.ac.uk

- which might be helpful at least as a positioning move.

[1] In the academic world it's often noted that books with "advanced"
in the title are at best aimed at secondary school level, whereas ones
with "elementary " in the title probably need a university degree,
maybe even a PhD, to even be able to understand them, let alone to
learn anything from them.
so I don't want to
just point my students to the W3C's Web Accessibilty Guidline articles
That's entirely understandable. There's a tendency for them to get
bound up in the minutiae of their interests, and lose sight of the big
picture.
out there that will explain why you need to think about accesbility
and some basic ideas on how to achieve it?

My "basic" idea is to go right back to the concept of logical
structure (even allowing for the fact that HTML is less than ideal
in that regard - but it's the best thing that we have access to, in
practical terms, so we use it, "warts and all").

The real WWW out there -will- decouple presentation from structure, no
matter whether you're in favour of it or not, and no matter those
precious designers who insist that their art is worthless if they
cannot impose both, in exactly the terms that they have conceived.

So learn what this decoupling involves - capitalise on it, exploit it,
make best use of the strengths of the medium to communicate the
content to the widest range of users and browsing situations. Don't -
as those pixel-precious graphic designers insist on doing - put
yourself at the mercy of its weaknesses.

good luck

[Nick Theodorakis]

On 13 Dec 2004 12:25:22 -0800, "Monte Gardner" <Mo***********@ asu.edu>
wrote:

I'm teaching a class on web authoring and html. I'm trying to find a
good reading article on accesibility issues.

[...]

<http://diveintoaccessi bility.org/>

Nick

--
Nick Theodorakis
ni************* *@hotmail.com
contact form:
http://theodorakis.net/contact.html

[Tim]

On Mon, 13 Dec 2004, Monte Gardner wrote:

I'm teaching a class on web authoring and html. I'm trying to find a
good reading article on accesibility issues. I'm trying to keep the
reading supplements to relatively light reading,
"Alan J. Flavell" <fl*****@ph.gla .ac.uk> posted:

[1] In the academic world it's often noted that books with "advanced"
in the title are at best aimed at secondary school level, whereas ones
with "elementary " in the title probably need a university degree,
maybe even a PhD, to even be able to understand them, let alone to
learn anything from them.
This has tickled my curiosity, I've heard comments like that a few times.
Is there some sensible reason for it, or is it some "in" joke?
out there that will explain why you need to think about accesbility
and some basic ideas on how to achieve it?

My "basic" idea is to go right back to the concept of logical
structure (even allowing for the fact that HTML is less than ideal
in that regard - but it's the best thing that we have access to, in
practical terms, so we use it, "warts and all").

As well as the technical aspects (simpler pages working more reliably in
more browsers, sometimes because of the many quite crap user agents that'd
do better with simpler page, not to mention people using fancy things in
really stupid ways), don't forget the human angle:

There's an *INCREDIBLY* large number of people in the world with some form
of disability or special needs, and when done *properly* HTML is one of the
few technologies that can *easily* accomodate them, and everybody else.
That's a big reason "why" you need to think about it.

--
If you insist on e-mailing me, use the reply-to address (it's real but
temporary). But please reply to the group, like you're supposed to.

This message was sent without a virus, please delete some files yourself.

[Stan Brown]

"Tim" wrote in comp.infosystem s.www.authoring.html:

There's an *INCREDIBLY* large number of people in the world with some form
of disability or special needs, and when done *properly* HTML is one of the
few technologies that can *easily* accomodate them, and everybody else.
That's a big reason "why" you need to think about it.

Yes, absolutely.

I had a student who was legally blind (he wore very thick glasses and
could read large print very close to his nose). The law and common
decency say that a public institution like my college should give him
reasonable accommodation. I didn't have to change any of the class
Web site for him; he just viewed the pages in his browser with his
chosen text size (which I'm sure was enormous).

That kind of stuff is actually easier to do IMHO that if one tries to
specify exact layout and sizes and then accommodate after the fact
for people who can't read it.

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://OakRoadSystems.com/
HTML 4.01 spec: http://www.w3.org/TR/html401/
validator: http://validator.w3.org/
CSS 2.1 spec: http://www.w3.org/TR/CSS21/
validator: http://jigsaw.w3.org/css-validator/
Why We Won't Help You:
http://diveintomark.org/archives/200..._wont_help_you

[CJM]

>

That kind of stuff is actually easier to do IMHO that if one tries to
specify exact layout and sizes and then accommodate after the fact
for people who can't read it.

I think that is lesson one.... make your site accessible from the start
rather than trying to bolt something on after the event.

Other than googling for a some more references, the only think I would add
is that to avoid reciting rather dry facts to them; I think it would be
better to present them with a good example and a bad example site - and run
through a comparison from the perspective of a person with visual [or other]
disability.

Chris

[Darin McGrew]

Alan J. Flavell <fl*****@ph.gla .ac.uk> wrote:

But most of the
folks learning HTML will come to it with a ballast of preconceptions
that prevent them being receptive to it. Un-learning preconceptions
is, by experience, /far/ harder than learning completely new stuff.

When I've taught brief "intro to HTML" workshops, I've started off by
trying to break the WYSIWYG preconceptions.

I ask for a show of hands: How many have ever viewed a web page? How many
have ever used more than one browser? How many regularly use more than one
browser?

Then I quickly show them a sample document in an assortment of browsers,
including a WebTV view, a handheld view, and speech synthesis.

With that understanding, we're ready to learn how to write web pages.
--
Darin McGrew, mc****@stanford alumni.org, http://www.rahul.net/mcgrew/
Web Design Group, da***@htmlhelp. com, http://www.HTMLHelp.com/

"FAILURE IS NOT AN OPTION. It comes bundled with the software."

[Stephen Poley]

On 13 Dec 2004 12:25:22 -0800, "Monte Gardner" <Mo***********@ asu.edu>
wrote:

I'm teaching a class on web authoring and html. I'm trying to find a
good reading article on accesibility issues. I'm trying to keep the
reading supplements to relatively light reading, so I don't want to
just point my students to the W3C's Web Accessibilty Guidline articles
(a little to heavy reading). Can any of you suggest an online article
out there that will explain why you need to think about accesbility and
some basic ideas on how to achieve it?

As far as the last point is concerned - achieving it, or at least
checking whether you've achieved it - I cover the basic accessibility
issues (and a couple of other issues) in my website checklist:
http://www.xs4all.nl/~sbpoley/webmatters/checklist.html

It might be of some assistance.

--
Stephen Poley

http://www.xs4all.nl/~sbpoley/webmatters/

[Genomega]

"Monte Gardner" <Mo***********@ asu.edu> wrote in message
news:11******** **************@ z14g2000cwz.goo glegroups.com.. .

I'm teaching a class on web authoring and html. I'm trying to find a
good reading article on accesibility issues. I'm trying to keep the
reading supplements to relatively light reading, so I don't want to
just point my students to the W3C's Web Accessibilty Guidline articles
(a little to heavy reading). Can any of you suggest an online article
out there that will explain why you need to think about accesbility and
some basic ideas on how to achieve it?

This is a good place to start.
http://www.accessify.com/tutorials/ten-quick-tests.asp
YPager genomega