Accessibility Techniques you've learnt this year (Full Version)

All Forums >> [Web Development] >> Accessibility



Message


Tailslide -> Accessibility Techniques you've learnt this year (11/8/2005 4:54:04)

Yes I know it's the same question as in the post in the CSS thread - but it's a different topic.

Before this year my chief contribution towards accessibility in my websites was to use CSS for layout rather than tables and not using fixed font sizing. It's really only this year that I've seriously looked into other techniques to increase the accessibility of my sites.

So a similar question to the one posted on the CSS thread.

What "Accessibility Techniques" have you learnt/started including in your sites this year?

My list:

1. Skip Links
2. Accessibility Statements/info
3. label tags for forms.




jaybee -> RE: Accessibility Techniques you've learnt this year (11/8/2005 5:19:18)

You're doing this on purpose. Sheeesh, more thinking.......

1. Not spending hours trying to find unique access keys and realising that as this subject is so new that sometimes the recommendations are just plain crazy and actually make things worse for the readers rather than better.

2. Goes off to get a cup of coffee and have a thunk




jaybee -> RE: Accessibility Techniques you've learnt this year (11/8/2005 6:04:41)

No it didn't take 30 minutes to get a coffee, the shopping was delivered so I had to put that away as well. (I love the internet!) [:D]

2. Accessibility pages rather than just compliance icons. (I need to go back and redo old sites).

3. Obvious way to make text bigger rather than relying on the user to know about text resize in their browser. I prefer an instruction page rather than a button that just does it.

4. Put a divider in between links to make it clear to readers that the links are separate. I use | and make it hidden.




womble -> RE: Accessibility Techniques you've learnt this year (11/8/2005 10:22:28)

The importance of designing with accessibility in mind from the start, rather than trying to add it in later.




Nicole -> RE: Accessibility Techniques you've learnt this year (11/8/2005 14:28:17)

That's the thing Womble. It's the whole thing!

Nobody when they're building a house considers that the doorways may need to be wider someday, that the front step should be a ramp and other things like that. It's later on when people are older or have suffered the accidents or illlnesses that they then have to tack these things onto their house. That's when it looks ugly and costs money, and that's why people think accessibility is going to look ugly and cost them money to add to their websites.

But if it is considered from the beginning, and designed by a designer that adds these things inconspicuously from the start, they neither look ugly nor cost more.

In response to Tail's question, considering this time last year my business site was laid out using frames, i've learnt everything I know about proper coding, accessibility and css this year.

Nicole




womble -> RE: Accessibility Techniques you've learnt this year (11/8/2005 14:58:30)

quote:

But if it is considered from the beginning, and designed by a designer that adds these things inconspicuously from the start, they neither look ugly nor cost more.

My point precisely, and your house-building example's an excellent analogy - I work in housing a know some about the cost of adapting homes (though infact here in the UK we have a new 'Lifetime Homes' standard that requires all new builds to take account of accessibility needs, that homes are designed and built to take into account the changing needs of people throughout their lifetime, so in the future the issue of expensive adaptations won't be so much of an issue - it's like WCAG Priority 1/2 in the real world) (OMG! Going into 'work mode' outside office hours! Arggh!)

Back on the subject of accessibility and the web though, as you say, if it's built in from the start, it's not going to cost any more (certainly not Priority 1 anyhow), and now I know about accessibility issues it's just automatic that I design with accessibility in mind.




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
6.640625E-02