[program-java] Re: HTML: TAGS
- From: "Octavian Rasnita" <orasnita@xxxxxxxxx>
- To: <program-java@xxxxxxxxxxxxx>
- Date: Tue, 17 May 2011 21:48:48 +0300
In adition, I would add:
1. A temporary problematic html tag for JAWS 12 is the <pre> element.
JAWS 11 reads it fine, but JAWS 12 doesn't read the text between <pre> and
</pre> as it is formatted, but it reads it using the common html rules, so if
the lines don't end with <br>, JAWS reads the whole text as a single line,
which is not correct with <pre>.
2. A problem are the <select> combo boxes with javascript code that submits the
form automaticly after choosing an element from the list.
3. The biggest problem is the captcha that doesn't provide a sound as an
alternative, the captcha that provides sound but complex words which are very
hard to understand or guess.
4. Another problem are the complex tables with table headings which are not
mapped to their corresponding cells.
5. Another problem are the sites that use Flash which is not really 100%
accessible, or a bigger problem are the sites that use Silverlight, and another
problem are the Java applets.
An important problem are the Flash-based media players that doesn't offer
accessible fast forward, or pause/stop buttons.
6. A big problem are the sites that make a music play immediately after opening
the page.
7. Another problem are the sites that offer the information in PDF files, some
of them beeing not accessible because they contain images, some of them contain
text but they load very hard in Acrobat Reader, or some of them contain tables
and other information organized in more columns, without an accessible
correlation between the elements.
And there are others...
Octavian
----- Original Message -----
From: "Homme, James" <james.homme@xxxxxxxxxxxx>
To: <program-java@xxxxxxxxxxxxx>
Sent: Tuesday, May 17, 2011 7:14 PM
Subject: [program-java] Re: HTML: TAGS
Hi Jim C,
Mostly, it's not tags that is the problem, it's how they are used. If you can
get more specific about the problem, I will be happy to point you in the right
direction. To get you started, though, if I had to pick the top five things to
look for, it would be:
1. the alt attribute not used or not used properly to help screen readers
figure out what images are.
2. heading 1 through heading 6 tags not used to mark up document sections, or
misused to alter font sizes.
3. Related to this, sections marked with bold and big fonts, but not with
heading tags.
4. Form fields either not labeled, or labels not used properly.
5. Link text that makes no sense when viewed out of context.
Those five things are probably the most major things you can fix to
dramatically improve HTML accessibility.
But let's get more specific.
Jim
From: program-java-bounce@xxxxxxxxxxxxx
[mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Corbett, James
Sent: Tuesday, May 17, 2011 8:51 AM
To: 'program-java@xxxxxxxxxxxxx'
Subject: [program-java] HTML: TAGS
Hello all:
Could or would someone be able to provide me with a reference for html tags
that are especially problematic to screen readers or the same being problematic
by their over use?
I'm now sharing my time in two groups that being development and work on our
CLF / Accessibility Guidelines. The latter being just a new assignment and one
that I'm keenly interested in.
Jim
James M. Corbett
Programmer / Analyst |
Canada Revenue Agency | Agence du revenue du Canada
875 Heron Rd.
Ottawa, On.
K1A0L5
James.Corbett@xxxxxxxxxxxxx
Telephone | Téléphone: (613) 941-1338
Facsimile | Télécopieur: (613) 941-2261
Government of Canada | Gouvernement du Canada
"Due to the highly confidential nature of my job, I'm not allowed to know what
I'm doing."
________________________________
This e-mail and any attachments to it are confidential and are intended solely
for use of the individual or entity to whom they are addressed. If you have
received this e-mail in error, please notify the sender immediately and then
delete it. If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this e-mail without the author's prior permission.
The views expressed in this e-mail message do not necessarily represent the
views of Highmark Inc., its subsidiaries, or affiliates.
Other related posts:
