Re: [WSG] skip links
Hi Julie - Original Message - From: Julie Romanowski To: wsg@webstandardsgroup.org Sent: Thursday, October 29, 2009 10:51 AM Subject: RE: [WSG] skip links Screen magnification users also benefit from skip links. Making these links visible help more than just screen reader and keyboard users. - - - - - - - - What I've settled for is as follows: div class=skip a href=#content accesskey=SSkip to Main Content/a /div Presumably, the accesskey caters for those folk also? ?? Bob *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] skip links
I'm a bit late but here are some good 'skip link' links: http://joeclark.org/book/sashay/serialization/Chapter08.html http://www.webaim.org/techniques/skipnav/ http://juicystudio.com/article/skip-links.php *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] skip links
On 29 Oct 2009, at 11:48, designer wrote: Screen magnification users also benefit from skip links. Making these links visible help more than just screen reader and keyboard users. div class=skip a href=#content accesskey=SSkip to Main Content/a /div Presumably, the accesskey caters for those folk also? Assuming they know the link is there. If it is styled to as to be invisible or off-screen, then it hurts more than it helps. -- David Dorward http://dorward.me.uk *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
[WSG] Out of Office AutoReply: WSG Digest
Hi - I'll be on leave and will return to the office Monday 2nd November. In that time Vikki Hsieh can help you with any matters relating to USiT. Cheers Chris Khalil, Director of User Experience, USiT *** This message and its attachments may contain legally privileged or confidential information. It is intended solely for the named addressee. If you are not the addressee indicated in this message or responsible for delivery of the message to the addressee, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by that company or any of its related entities. No warranty is made that the e-mail or attachments are free from computer virus or other defect. *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Re: WSG Digest
ピエールランリ・ラヴィン wrote:
Actually is not enough. Accesskey is a good way about the accessibility,
but it's not completed.
I didn't check the latest WCAG and the latest version of screen readers
but:
* Keyboards shortcuts depend from the UA (the specifications didn't
define it)
* Users may define preferences keys
* Most of the screen readers set the priorities to the website, so if
you use a key not defined by the user but already defined by the
browsers (like 'd'), you can private them from native functionalities
* A few screen readers like IBM Home Page Reader set the priorities to
the user so some accesskeys may be ignored in case of conflicts
* Exotic keys like \ ] ( most unused ) may not work.
So primary:
* Set in the head of html a bunch of primary links as link tag (link
rel=start href=http://www.mysite.com; title=Home Page /link
rel=help ...)
* At least a skip to content link on TOP of your page (means top of
the HTML page, not after iframe or ads or anything, just after the body.
I don't remember the book (maybe Mr Zeldmann), citing
http://www.jimthatcher.com/ (good example with focus only).
* an additional block of skipping links at the top of the page too, like
those defined by BBC - http://www.bbc.co.uk, great example too of skip nav
* Then a block of visible links like help, select a skin typically ideal
to introduce stuffs like style switcher, etc..
* Use correctly the titles h1, h2, h3, h4, h5, h6
* Use tabindex. you can play with tags like div - a, setting a tabindex
and a title attribute
* And of course write the 'help page' about how using your site
Accessibility depends from the country too, but I think in Europe most
the countries are using the following accesskeys:
Key 0: list of accesskeys , may be defined in the accessibility / help
page.
Key 1: home page (key not working with IBM Home Page Reader)
Key 2: news
Key 3: sitemap
Key 4: form, for example search form
Key 5: FAQ, glossary, etc...
Key 6: help about using the website
Key 7: email contact
Key 8: copyrights, license, ...
Key 9: guestbook, feedback
So accesskeys are great but only one of the way to enhance the
accessibility.
Great french article:
http://openweb.eu.org/articles/accesskey_essai_non_transforme.
One of the famous trick in css then is to use .off-left {
position:absolute; left:-9px; } for example instead of display:none,
to set content outside of the screens but keep it readable by screen
readers.
~~~
A very informative post. Thank you.
FWIW If a skip to main content is visible, I tend to use it to bring
the main article to the top of the window. Please make the link
available to sighted users as well...
Cordially,
David
--
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
Re: [WSG] Re: WSG Digest (Re: [WSG] skip links)
David Hucklesby さんは書きました:
ピエールランリ・ラヴィン wrote:
Actually is not enough. Accesskey is a good way about the
accessibility, but it's not completed.
I didn't check the latest WCAG and the latest version of screen
readers but:
* Keyboards shortcuts depend from the UA (the specifications didn't
define it)
* Users may define preferences keys
* Most of the screen readers set the priorities to the website, so if
you use a key not defined by the user but already defined by the
browsers (like 'd'), you can private them from native functionalities
* A few screen readers like IBM Home Page Reader set the priorities
to the user so some accesskeys may be ignored in case of conflicts
* Exotic keys like \ ] ( most unused ) may not work.
So primary:
* Set in the head of html a bunch of primary links as link tag (link
rel=start href=http://www.mysite.com; title=Home Page /link
rel=help ...)
* At least a skip to content link on TOP of your page (means top of
the HTML page, not after iframe or ads or anything, just after the body.
I don't remember the book (maybe Mr Zeldmann), citing
http://www.jimthatcher.com/ (good example with focus only).
* an additional block of skipping links at the top of the page too,
like those defined by BBC - http://www.bbc.co.uk, great example too
of skip nav
* Then a block of visible links like help, select a skin typically
ideal to introduce stuffs like style switcher, etc..
* Use correctly the titles h1, h2, h3, h4, h5, h6
* Use tabindex. you can play with tags like div - a, setting a
tabindex and a title attribute
* And of course write the 'help page' about how using your site
Accessibility depends from the country too, but I think in Europe
most the countries are using the following accesskeys:
Key 0: list of accesskeys , may be defined in the accessibility /
help page.
Key 1: home page (key not working with IBM Home Page Reader)
Key 2: news
Key 3: sitemap
Key 4: form, for example search form
Key 5: FAQ, glossary, etc...
Key 6: help about using the website
Key 7: email contact
Key 8: copyrights, license, ...
Key 9: guestbook, feedback
So accesskeys are great but only one of the way to enhance the
accessibility.
Great french article:
http://openweb.eu.org/articles/accesskey_essai_non_transforme.
One of the famous trick in css then is to use .off-left {
position:absolute; left:-9px; } for example instead of
display:none, to set content outside of the screens but keep it
readable by screen readers.
~~~
A very informative post. Thank you.
FWIW If a skip to main content is visible, I tend to use it to bring
the main article to the top of the window. Please make the link
available to sighted users as well...
Cordially,
David
--
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
Thanks :-)
It makes sense to set it visible too but it's not easy.
Even now, unfortunately, most of the websites doing this are people who
care about great accessibility and/or usability.
You will deal with any people (clients - marketing - design) saying for
example:
You don't understand me, the users of my website are teenagers who want
to subscribe for a plan and get a mobile,
Famous fact that 15-25 years old people don't really understand
interface, are all in good health, and 100% capabilities. (ironical)
What seems Killing the user experience for advanced users may not be
for the average people.
So I meant in the worst case, better to have hidden skip links that
nothing ;-) (From my point of view)
For your personal use, if you don't care about the design, there are
some fancy plugins like tidy read
http://www.tidyread.com/ which extracts the main article as text so you
won't need or complain about skip links ;-)
Available for Firefox and IE.
What is funny about link in the html head (
http://www.w3.org/TR/REC-html40/struct/links.html#h-12.3), i never found
how to use it natively with browsers. Can anyone provide informations
about that please ?
Regards
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
[WSG] [OT] Google search/index/webmaster help
Yes, I know it's off topic, but I really need a hand with a mystifying problem. I've tried the google forums, but have received no replies. If there are any listers who understand the free Google Custom Search Engine, webmaster tools, sitemaps and indexing problems, then I'd really appreciate you contacting me directly in regards to some problems I'm having. Just to give an idea of my quandary... http://maps.unimelb.edu.au/ http://maps.unimelb.edu.au/sitemap.xml (100+ URLs submitted 5 months ago) http://www.google.com/search?q=site:maps.unimelb.edu.au (34 results = pathetic!) http://go.unimelb.edu.au/6t6 (1 result = totally pathetic!) Hopefully, it's nothing completely bleeding obvious that will humiliate me in front of my peers ;-) -- Andrew Harris and...@woowoowoo.com http://www.woowoowoo.com ~~~ * ~~~ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] [OT] Google search/index/webmaster help
Craig, OK - that's a really interesting comment. I had, as far as I knew, used the right formatting, the sitemap validates as XML and Google's webmaster tools accepted it as a valid feed (after a few tweaks!) I followed this document, which I understand is the definitive source. http://www.sitemaps.org/protocol.php and my sitemap looks pretty much like that - apart from a couple of whitespace discrepancies. The fact that it worked for some of the URLs makes me think it's not a problem with the sitemap, but it's all interesting stuff. Thanks for taking the time to reply. On Fri, Oct 30, 2009 at 3:24 PM, Craig Jones cr...@designawebnoosa.com.auwrote: Hi Andrew, This is my firts time trying to help... It doesn't appear that your sitemap is written in xml The sitemap should look like this urlset xsi:schemaLocation=http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd; url locwww.unimelb.edu.au/campuses/maps.html/loc /url url locwww.unimelb.edu.au/campuses/maps2.html/loc /url /urlset then submit you new sitemap in google webmaster tools Goodluck Craig Andrew Harris wrote: Yes, I know it's off topic, but I really need a hand with a mystifying problem. I've tried the google forums, but have received no replies. If there are any listers who understand the free Google Custom Search Engine, webmaster tools, sitemaps and indexing problems, then I'd really appreciate you contacting me directly in regards to some problems I'm having. Just to give an idea of my quandary...http://maps.unimelb.edu.au/http://maps.unimelb.edu.au/sitemap.xml (100+ URLs submitted 5 months ago)http://www.google.com/search?q=site:maps.unimelb.edu.au (34 results = pathetic!)http://go.unimelb.edu.au/6t6 (1 result = totally pathetic!) Hopefully, it's nothing completely bleeding obvious that will humiliate me in front of my peers ;-) -- *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** -- Andrew Harris and...@woowoowoo.com http://www.woowoowoo.com ~~~ * ~~~ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] [OT] Google search/index/webmaster help
Bother! that last reply was supposed to be off list! Oh well, the discussion had got around to web standards by that point, so it's fair game. ...and it's a friday afternoon, cut me some slack!! Thanks to all those who have replied off list. By way of reporting back to the list, I'll say... 1) Sitemaps are not the magic fix I thought they were. 2) Inbound links and organic indexing are vital. 3) My map pages are pretty short on text - google likes text. One thing that no-one picked up on was that I still haven't inserted some common metadata tags - I know they say google doesn't look at the metadata tags, but it makes me wonder. Funny how asking your peers to check your work suddenly makes you aware of basic things you'd missed... yes, my pages weren't valid - but they are now!!! ;-p -- Andrew Harris and...@woowoowoo.com http://www.woowoowoo.com ~~~ * ~~~ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
