Accessibility myths
Tue, Oct. 11th, 2011 10:10 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
I often see people whose goal is to be helpful and promote good, accessible design stating that one of the most important things when writing accessible HTML is to use <strong> and <em> instead of <b> and <i>. While using semantically meaningful tags is important to write semantically correct HTML, it has no effect on accessibility. In practice, no screenreaders distinguish between <strong> and <b> or <em> and <i>. Again, it's not a bad thing from a semantically correct HTML point of view, but it won't help your readers with disabilities.
I love the clearly written articles about accessibility at the WebAIM site, which talk in simple terms about not just procedures but principles. I suggest that everyone who cares about making more accessible fandom web resources take some article on that site when you have a free 5 minutes and read it. Any article that interests you. "Writing appropriate alternative text" might be particularly apropos to the questions many people have asked, because alternative text is an art, not a science.
I love the clearly written articles about accessibility at the WebAIM site, which talk in simple terms about not just procedures but principles. I suggest that everyone who cares about making more accessible fandom web resources take some article on that site when you have a free 5 minutes and read it. Any article that interests you. "Writing appropriate alternative text" might be particularly apropos to the questions many people have asked, because alternative text is an art, not a science.
(no subject)
Date: 2011-10-11 04:12 pm (UTC)