Services & Products
or
Services & Products
Update:
views:
127answers:
4How popular screen readers and text only browsers will handle
+3
A:
You must escape the plain & with a character reference like & in order to have a valid XHTML document:
The ampersand character (
&) […] may appear in their literal form only when used as markup delimiters, or within a comment, a processing instruction, or a CDATA section. If they are needed elsewhere, they must be escaped using either numeric character references or the strings "&" […]
Gumbo
2010-04-08 09:52:57
+5
A:
In HTML — it doesn't matter (since the ampersand is followed by a space).
In XHTML — & is a well-formedness error and is completely unacceptable.
David Dorward
2010-04-08 09:53:15
metal-gear-solid
2010-04-08 10:40:32
It won't. The browser will parse the HTML or XHTML and generate a DOM which it will render. The screen reader will then read what is on the screen with hints from the browser.
David Dorward
2010-04-09 07:42:27
As a rule of thumb — write good HTML and don't expect screen readers to require you to make errors.
David Dorward
2010-04-09 08:09:16
A:
Always escape the ampersand character with the proper character encoding. In HTML it is & or &. In URI it is %26 and not either of the previous two. Not escaping syntax characters will cause XML to fail. If your HTML is ever to be integrated or interpreted by an XML engine your code will break.
Gumbo
2010-04-08 10:19:40
+2
A:
Screen readers will read "&" as "and", and text-only browsers will display it as "&".
The reason you write & is because "&" is a special character in XHTML and must be escaped. Any browser/screenreader that understands XHTML knows that & is the escaped ampersand ('&') and will display it as such, or read it aloud as "and".
If you're writing an XHTML document, it's not a case of how to make your alt-text more screenreader friendly - you must replace your bare ampersands with & or risk your document not validating and potentially displaying incorrectly.
meagar
2010-04-09 04:25:41