Site on extreme accessibility

[cms-hispano.org]

i'm building a site about extreme accessibility, i.e.: how (and why)
to get sites to become fully accessible, *beyond* W3C Web
Accessibility Initiative guidelines. it's far from being completed (i
just started it off!), so i'd very much appreciate any comment on the
site/issue: www.accessibility.ws

(fyi: i a non-commercial, personal research project)

cheerio!

[Steve Pugh]

"cms-hispano.org" <mi*********@gmail.comwrote:

>i'm building a site about extreme accessibility, i.e.: how (and why)
to get sites to become fully accessible, *beyond* W3C Web
Accessibility Initiative guidelines. it's far from being completed (i
just started it off!), so i'd very much appreciate any comment on the
site/issue: www.accessibility.ws

<h1>Welcome to Accessibility.ws home page, the most accessible portal!
Please, choose through the following links what you want to do in this
site; none of them will open in a new window or lead you to
non-accessible sites: I want to skip navigation | I want to read news
about Accessibility.ws | I want to browse through your accessibility
tutorials page | I want to read more about you | I want to contact
you</h1>

That's one hell of an <h1and probably not great accessibility.

You're also using <span class="bold"where you should be using <h2>
or <h3(the "Tutorial number one: Accessibility and capabilities"
heading); using <acronymwhere you should be using <abbr(WWW isn't
pronounced as a word and so isn't an acronym); and the tutorial page
fails validation. So at the moment you don't even meet WAI Level AA,
to say nothing about going "beyond WAI guidelines".

Sorry to focus on the technicalities, but with only two short pages of
fairly non-specific content it's hard to give any feedback on anything
else.

Steve
--
"My theories appal you, my heresies outrage you,
I never answer letters and you don't like my tie." - The Doctor

Steve Pugh <st***@pugh.net <http://steve.pugh.net/>

[Bergamot]

cms-hispano.org wrote:

i'm building a site about extreme accessibility, i.e.: how (and why)
to get sites to become fully accessible, *beyond* W3C Web
Accessibility Initiative guidelines.
www.accessibility.ws

<h1><span class="bold">Welcome to Accessibility.ws home page, the most
accessible portal!</span><br>
Please, choose through the following links what you want to do in this site;
none of them will open in a new window or lead you to non-accessible sites:
<a href="#MainContent" title="Skip navigation">I want to skip navigation</a>
| <a href="#News" title="News">I want to read news about
Accessibility.ws</a>
| <a href="tutorials.html" title="Tutorials">I want to browse through your
accessibility tutorials page</a| I want to read more about you | <a
href="contact.html" title="Contact">I want to contact you</a></h1>
What's wrong with this code? Pretty much everything. I don't think you
should be writing about web accessibility until you learn a lot more
about it, or at least about proper HTML symantics.

"Design and aesthetics are not a must within the WWW."
Yeah, but they don't hurt if you're trying to impress anyone. ;) A
completely unadorned design just promotes the lame excuse that one can't
make an accessible site that is also attractive.

--
Berg

[Stan Brown]

Sun, 18 Feb 2007 19:34:41 +0000 from Steve Pugh <st***@pugh.net>:

"cms-hispano.org" <mi*********@gmail.comwrote:

i'm building a site about extreme accessibility

Is it just me, or do others find that "extreme" as an adjective
correlates highly with the bogus?

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

[Martin Clark]

cms-hispano.org wrote...

>i'm building a site about extreme accessibility, i.e.: how (and why)
to get sites to become fully accessible, *beyond* W3C Web
Accessibility Initiative guidelines. it's far from being completed (i
just started it off!), so i'd very much appreciate any comment on the
site/issue: www.accessibility.ws

You have spelt "accessibility" wrong three times on the first page.
--
Martin Clark

[Jim Moe]

Steve Pugh wrote:

>
[...]; using <acronymwhere you should be using <abbr(WWW isn't
pronounced as a word and so isn't an acronym); [...]

Likely the gaffe is because the most used browser, IE, does not support
<abbr>.

--
jmm (hyphen) list (at) sohnen-moe (dot) com
(Remove .AXSPAMGN for email)

[Jukka K. Korpela]

Sub titulo Re: Site on extreme accessibility
scripsit Jim Moe:

Steve Pugh wrote:

>>
[...]; using <acronymwhere you should be using <abbr(WWW isn't
pronounced as a word and so isn't an acronym); [...]

Likely the gaffe is because the most used browser, IE, does not
support <abbr>.

I have no intentions of defending the bogus "site on extreme accessibility"
(which looks like malevolent bashing of accessibility, even if I keep saying
to myself "never ascribe to malevolence anything that can be conveniently
explained as stupidity or ignorance"), and I only wish to make technical
comments on <abbrsupport, so I've changed the Subject line.

IE lacked any support to <abbrup to and including IE 6, to the extent that
it does not even recognize the tags. After all, a browser could well conform
to HTML specs as regards to <abbr(and <acronym>) simply by parsing the
markup; no specific rendering or behavior is required. But IE just discarded
the tags, so you could not even use your own styling for the <abbrelement.

This changed in IE 7, which recognizes <abbrthough renders it as normal
text by default (which is quite sensible if you ask me, and even if you
don't). It shows the value of an eventual title="..." attribute as a
tooltip, as expected, since that's what it does to the attribute in all
elements. From the IE 7 perspective, <abbris much like <span>.

(Actually <abbrand <acronymare much like <awithout attributes, except
that <abbrand <acronymhave strange default renderings on some browsers
and might get even wilder if some implementor takes the "sample style sheet
for HTML 4"*) in the CSS 2.0 specification seriously. Since <ais much
shorter and avoids the twisty question "what's an acronym, BTW?", we could
use <a title="World Wide Web Consortium">WWW</aand use CSS for any styling
we like. I'm not entirely serious. :-) )

( *It has: ABBR, ACRONYM { font-variant: small-caps; letter-spacing:
0.1em }
which is a really bad joke.)

You can use
abbr { border-bottom: dotted 2px; }
if you want to have a simulated dotted underline on IE 7 as by default on
some other browsers.

--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/

[Andy Dingley]

On 18 Feb, 19:15, "cms-hispano.org" <[e-mail]:

i'm building a site about extreme accessibility,

I suggest that you learn how to _do_ it first. That site's pretty bad.

Try reading the already existing excellent Joe Clark site.

[Chaddy2222]

On Feb 19, 6:15 am, "cms-hispano.org" <[e-mail]:

i'm building a site about extreme accessibility, i.e.: how (and why)
to get sites to become fully accessible, *beyond* W3C Web
Accessibility Initiative guidelines. it's far from being completed (i
just started it off!), so i'd very much appreciate any comment on the
site/issue:www.accessibility.ws

I agree with what has already has been said, plus "here" is not a very
informative link name for a link in the middle of a block of text when
your tabing through the text.
Read the following:
http://dev.wave.webaim.org/Output.js...ontent&md=nils
I hope that helps.
--
Regards Chad. http://freewebdesign.cjb.cc