RE: [WSG] Quick accessibility question
> From: Hugh Todd > Just tried it with a preview version of Apple's Spoken Interface in > Safari. I stuck your code into the middle of a standard form > element to > see what would happen, and it read it as "S" "earch". I'd be > interested > to know why (how the reader determines what to read and how). Well, in simple terms, the readers will be looking for complete words. If something is interrupted - be it by a space, a , (probably even) , or indeed is broken up by separating bits of it in different elements (even if they're inline, like ) - it will be seen as two separate words. Simple as that... Patrick Patrick H. Lauke Webmaster / University of Salford http://www.salford.ac.uk * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *
Re: [WSG] Quick accessibility question
Richard Rutter wrote: If you want something doing... A script which uses the DOM to automatically underline the letter of a link text which matches its accesskey: http://clagnut.com/sandbox/dynamic-accesskeys/ Any use? In some ways this could be using JavaScript to increase accessibility, or least stop mark-up getting in the way. Smartass I hope you're gonna use that for your SkillSwap :-) Andy Budd * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *
Re: [WSG] Quick accessibility question
Andy, Just tried it with a preview version of Apple's Spoken Interface in Safari. I stuck your code into the middle of a standard form element to see what would happen, and it read it as "S" "earch". I'd be interested to know why (how the reader determines what to read and how). -Hugh Todd Here's a quick (and probably stupid) accessibility question regarding screen readers. Search I assume the a screen reader will read this out as "Search" and not "S earch". * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *
RE: [WSG] Quick accessibility question
Hey, that looks interesting, Richard. You got me thinking. Nice one :o) Mike Pepper (thoughtful) Accessible Web Developer www.seowebsitepromotion.com www.gawds.org -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Richard Rutter Sent: 15 June 2004 22:15 To: [EMAIL PROTECTED] Subject: Re: [WSG] Quick accessibility question On 15 Jun 2004, at 17:55, Richard Rutter wrote: > Anyone fancy a bit of fun making that work? Would it actually be > useful? > If you want something doing... A script which uses the DOM to automatically underline the letter of a link text which matches its accesskey: http://clagnut.com/sandbox/dynamic-accesskeys/ Any use? In some ways this could be using JavaScript to increase accessibility, or least stop mark-up getting in the way. Rich. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help * * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *
Re: [WSG] Quick accessibility question
On 15 Jun 2004, at 17:55, Richard Rutter wrote: Anyone fancy a bit of fun making that work? Would it actually be useful? If you want something doing... A script which uses the DOM to automatically underline the letter of a link text which matches its accesskey: http://clagnut.com/sandbox/dynamic-accesskeys/ Any use? In some ways this could be using JavaScript to increase accessibility, or least stop mark-up getting in the way. Rich. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *
Re: [WSG] Quick accessibility question
On 15 Jun 2004, at 12:34, Andy Budd wrote:
I agree with you. It's not the nicest way of doing this. I think
using the :first-letter pseudo-element selector would probably be a
better bet.
Much neater, until you need accesskeys for both Search and Services of
course. I'm sure some clever person could apply the underlining to
links with accesskeys via the DOM.
Assuming Andy is along the write lines with his tags (and I see
no reason why not), the pseudo code might be something like:
for each link in the document {
if link has an accesskey attribute {
split link text at first instance of accesskey value
wrap a span around the accesskey value
recombine the link text
write modified link text back into DOM
}
}
Anyone fancy a bit of fun making that work? Would it actually be useful?
Rich.
*
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
*
Re: [WSG] Quick accessibility question
Patrick Lauke wrote: Tested with JAWS 4.02, and yes, it reads it as "search". That's not to say, though, that all screenreaders behave this way... Let me guess...underlines for accesskeys ? That's the fella One thing that worries me about doing those sorts of things is that the result is very...non semantic. Not sure how, say, search engines would react to seeing Words broken up like that. Would they still index the word itself, or would they see an "S" and "earch"? (sure, in this case it doesn't make a difference, but I'm thinking in more general terms, e.g. headings using an image as an ornate initial or something - search engines would presumably not recognise the designer's intention - why should they? - and not see the word as a whole). Patrick I agree with you. It's not the nicest way of doing this. I think using the :first-letter pseudo-element selector would probably be a better bet. Andy Budd http://www.message.uk.com/ * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *
RE: [WSG] Quick accessibility question
Tested with JAWS 4.02, and yes, it reads it as "search". That's not to say, though, that all screenreaders behave this way... Let me guess...underlines for accesskeys ? One thing that worries me about doing those sorts of things is that the result is very...non semantic. Not sure how, say, search engines would react to seeing Words broken up like that. Would they still index the word itself, or would they see an "S" and "earch"? (sure, in this case it doesn't make a difference, but I'm thinking in more general terms, e.g. headings using an image as an ornate initial or something - search engines would presumably not recognise the designer's intention - why should they? - and not see the word as a whole). Patrick Patrick H. Lauke Webmaster / University of Salford http://www.salford.ac.uk > -Original Message- > From: Andy Budd [mailto:[EMAIL PROTECTED] > Sent: 15 June 2004 11:39 > To: [EMAIL PROTECTED] > Subject: [WSG] Quick accessibility question > > > Here's a quick (and probably stupid) accessibility question regarding > screen readers. > > Search > > I assume the a screen reader will read this out as "Search" > and not "S > earch". > > > Andy Budd > > http://www.message.uk.com/ > > * > The discussion list for http://webstandardsgroup.org/ > See http://webstandardsgroup.org/mail/guidelines.cfm > for some hints on posting to the list & getting help > * > > * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *
