Forum Moderators: open
However, with CFStudio 5 it puts in <em> instead of <i>, and <strong> instead of <b>. Are <em> and <strong> part of a new web standard or is CFStudio 5 acting the fool?
It is easy to speak with emphasis and to use a strong voice...
But a bit difficult to speak in italics while bold can easily be misinterpretted...
Similar issue - "requiring" alt attributes for all image tags. That's also all about awareness, IMO. Of course browsers won't fail if alts are omitted. And it is silly - even wasteful - to require alt="" for every little geegaw on the page.
Don't get me wrong - it isn't at all silly to ask designers to consider non-visual browsing. But I sense more spin than technical necessity in these particular changes.
Spin is right....
When it comes to CSS and you, I will be glad to play the follower. So, if you say find and replace, I will probably give it a try. Now I'll have to figure out how to get FP to use <em> and <strong> instead of <b> and <i>. ;)
By the way, how many Aural Browser users are out there? Can I distinguish them in the log files?
But, I must say I enjoy this debate. And I think it is very important to bring these questions and issues out. After all - we, as web designers, are in the end the ones with the power. :)
For me, the first step was migrating to XHTML and CSS, it seems like a logical step in moving towards coding for accessibility. Eliminating all the old bulky code is a good start.
I'm going to start researching the useage of aural browsers (and Braille) just to see how widespread their useage really is. I do believe however, that new user-agents that provide accessibility are becoming more user friendly so that there may be an increase in users accordingly.
It is easy to take things for granted, but as PDA's and other small personal Internet appliances become more readily available, isn't it logical that the same devices modified for those with phyisicall impairments might see a widespread growth as well? I bet they will.
Just as with CSS and Web Standards, we can wait until the need becomes a neccessity and then try to play "catch-up" or we can begin dealing with the inevitable and get a headstart. Personally, I like the idea of a headstart.
So, who is using aural browsers... how common are they? Does it really matter?
Older, slower pcs and less powerful software had to make the experience somewhat difficult.
Combine that with sites that were created with complex table designs, no alt tags, or ANY consideration for "accessibility browsers," it must've made surfing seem pretty chaotic.
If I can code a page that will help provide access to even one user, I would do it... and I will. But truthfully, from what I've seen so far, simply coding for Standards goes a long way towards achieving that goal.
As far as replacing <b> & <i> with <strong> and <em>, that remains to be seen... A lot depends on your page design. I can think of a few instances where I have an entire paragraph enclosed with <em> tags... I need to change that for the reasons Tedster mentioned.
We all should work on greater awareness of the WAI, I think it will make us better developers in the long run.
