Accessibility issues
-
-
- Penn Wooding
- Elite Rocketeer
- Posts: 873
- Thanks: 0
-
I happened to comment on the size and colours of some text and font on a website that I is used sometimes. Basically, some of that text is very difficult to read. Anyway, somebody obviously didn't quite like my comments, even though they were quite polite. They posted the following about the homepage on my personal website. I wondered if someone with a little bit more experience about accessibility could give me their opinion on what is said. I can't say that I have a problem navigating my website, and I've never had any feedback from my visitors regarding accessibility problems.
www.tetraplegicliving.com/
The home page also contains 21 HTML errors, 55 CSS errors, and fails the most basic WAI accessibility level. It would prove very difficult to navigate for some disabled vistors - particularly blind visitors using a screen reader or those unable to use a mouse.
- http://www.Oscarfishlover.com - the website for great Oscar Fish advice and help
-
-
-
- JEM
- Preeminent Rocketeer
- Posts: 17917
- Thanks: 4
-
Supposedly the default template are compliant, but there's mention of some templates not being so.
I don't think there's a way to make something like, for example RokTabs, work with a screen reader.
In any case, if you were developing a site for the blind, you probably wouldn't be using tabs, scrollers, and other fancy features.
Tons of links for Joomla accessibility and 508 compliance standards, just google for further reading.
You can validate your site here:
validator.w3.org/ - Thanks,
jim
-
-
-
- Penn Wooding
- Elite Rocketeer
- Posts: 873
- Thanks: 0
-
interesting, I checked my personal website and add something like 150 errors. I checked my Oscar Fish website and only three errors. Does this mean anything to you?
# Line 577, Column 8: required attribute "action" not specified
<form>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
# Error Line 682, Column 39: document type does not allow element "script" here
</body><script type="text/javascript">
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
# Error Line 686, Column 31: document type does not allow element "script" here
<script type="text/javascript">
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error). - http://www.Oscarfishlover.com - the website for great Oscar Fish advice and help
-
-
-
- JEM
- Preeminent Rocketeer
- Posts: 17917
- Thanks: 4
-
Sorry Penn, not my specialty....
However, I did use a validator a few times which fixed the errors and allowed you to preview the site, I think it's a FireBug plugin.
If the change was OK, then you could change the code.
Anyway, it didn't fix everything and some changes messed up the site in the preview mode, but I was able to fix a bunch of stuff.
You might want to take a look at the FireBug plugins.
I'll check my computer when I go home to see which one it is and if it's not a plugin, try to find a link. - Thanks,
jim
-
Time to create page: 0.080 seconds