On Feb 24, 2011, at 9:57 PM, Thierry Koblentz wrote:
If you use anything other than buttons or links make sure to use tabindex=0
to make your elements focusable via keyboard, and attached role=button to
it.
As a side note, the challenge with collapsing panels is to let users
the redundant text and wonder why a regular
message box wasn't used.
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of tee
Sent: Wednesday, February 23, 2011 5:21 AM
To: wsg@webstandardsgroup.org
Subject: [WSG] screen reader friendly
On Sat, Feb 26, 2011 at 8:11 AM, Smith, Jamie jamie.sm...@dbs.fldoe.org wrote:
After the click me link is selected a person using speech read
Keyboard Accessible Popup
Click me - This is keyboard accessible, but will the empty link creates
redundant noise for screen reader?
Lorem ipsum
On Feb 25, 2011, at 2:21 PM, Andrew Boyd wrote:
Jamie,
this just proves to me that nobody really likes Lorem ipsum... :)
I used to use the first paragraph of Italo Calvino's If on a Winter's Night a
Traveler for such purpose. Someone wrote me off list (not from this list)
gently warned
Thierry,
Thanks for the suggestion! It got me think of a few things.
Structurally and semantically, do you find a distinctive difference between
Modal and Collapsible?
I wanted to make sure I am on the right track; when I think of the use of Modal
Window, I think of a block of content
On Feb 24, 2011, at 2:19 AM, tee wrote:
making sure the focus brought back to the original trigger is something that
needs to deal with - a Modal script I use, doesn't offered this feature, it
jumps back to the first link.
Maybe not!
http://jsbin.com/awidi4
But the browsers behave
With Collapsible, it's largely a UI/Design choice, structurally, the
content in it is part of the main content, it's just a simple show/hide
that makes good use of space, and apart from button that you
recommended, a heading can be served as a trigger too depending on the
content (for the
Please take a look at this example. The first example is keyboard accessible
however I am also concern with the empty link that may create extra noise for
screen reader, e.g if every single page has a popup, it will have two empty
links, one is the popup trigger and the other the close link.
[mailto:li...@webstandardsgroup.org] On
Behalf Of tee
Sent: 23 February 2011 10:21
To: wsg@webstandardsgroup.org
Subject: [WSG] screen reader friendly and keyboard accessible popup?
Please take a look at this example. The first example is keyboard accessible
however I am also concern
On 2/23/2011 9:20 PM, tee wrote:
Please take a look at this example. The first example is keyboard accessible
however I am also concern with the empty link that may create extra noise for
screen reader, e.g if every single page has a popup, it will have two empty
links, one is the popup
On 2/23/2011 10:37 PM, Foskett, Mike wrote:
Just a few thoughts.
It would be better if the keyboard link had an id reference in it.
a id=openPopup1 href=#popup1pop-up/a
And the associated div had an id:
div id=popup1...
The close link references the opening link:
a id=openPopup1 href=#popup1pop-up/a
And the associated div had an id:
div id=popup1...
The close link references the opening link:
a href=#openPopup1Close/a
Also shift the pop-up off-screen rather than display:none
#popup1 {position: absolute;
Hi Tee,
Please take a look at this example. The first example is keyboard
accessible however I am also concern with the empty link that may
create extra noise for screen reader, e.g if every single page has a
popup, it will have two empty links, one is the popup trigger and the
other the
13 matches
Mail list logo
