On 5 Aug 2015, at 13:25, Tom Livingston wrote:
> IMHO, with regards to the original question, if you are going to use
> the .visuallyhidden rule, you'll probably need to over ride all of
> that, so your "off" rule is needed (as always, it's based on each use
> case). There isn't a 'master off-swi
IMHO, with regards to the original question, if you are going to use
the .visuallyhidden rule, you'll probably need to over ride all of
that, so your "off" rule is needed (as always, it's based on each use
case). There isn't a 'master off-switch' - although, it would be nice
wouldn't it? ;-)
Other
On 4 Aug 2015, at 13:23, Philippe Wittenbergh wrote:
> Nope, Marco is right (and Jim). If you hide something, hide it for everybody.
> Use the whole machinery provided by aria-* attributes to clarify & improve
> the experience for AT users. That might require using bits of JS to toggle
> attri
> On Aug 4, 2015, at 19:03, Rick Lecoat wrote:
>
> Jim Thatcher (who, it might be supposed, knows a thing or two about
> accessibility) is of the view that there is almost no reason to make hidden
> content available to screenreaders:
> http://alistapart.com/comments/now-you-see-me#330917
>
On 4 Aug 2015, at 10:17, Philippe Wittenbergh wrote:
> Browser support for clip-path is pretty weak, atm. Safari 8, yes, Firefox no,
> IE no (but Edge?), Chrome unknown.
> Deprecated doesn’t mean that browsers will drop support for a
> feature/property/value soon, if ever.
So, maybe:
.visuall
On 4 Aug 2015, at 09:56, Philippe Wittenbergh wrote:
> Fwiw, I use those (complicated) hide-from-sighted-users-but-not-from-AT {}
> less and less these days, in favour of aria-label="". In the example you
> give, you can omit the `label` from the search form, and just use type="search" aria-la
> On Aug 4, 2015, at 18:02, Rick Lecoat wrote:
>
> And I've just discovered now that clip is deprecated, so I should probably
> use clip-path instead (with clip as a browser fallback?).
Browser support for clip-path is pretty weak, atm. Safari 8, yes, Firefox no,
IE no (but Edge?), Chrome unk
With regard to my rather (overly-)complicated .visuallyhidden rule:
> /* hidden but available to speaking browsers */
> .visuallyhidden {
>overflow : hidden;
>position : absolute;
>clip : rect(0 0 0 0);
>height : 1px;
>width : 1px !important;
>margin : -1px;
>paddin
> On Aug 4, 2015, at 17:29, Rick Lecoat wrote:
>
> It is, unless you want to hide content from sighted users whilst still making
> it available to assistive technologies. Examples: a 'Search' label beside a
> search field, or 'skip to main content' links.
Fwiw, I use those (complicated) hide-
On 4 Aug 2015, at 02:04, John D wrote:
> .mystyle {
> display: none;
> }
>
> Will hide the block which has a class called "mystyle" . when you want to
> unhide it, you just need to comment it out like this:
>
> .mystyle {
> /* display: none; */
> }
(For clarity, I've updated the above-quo
-Original Message-
From: Tom Livingston
Sent: Tuesday, August 04, 2015 2:07 AM
To: John D
Cc: Rick Lecoat ; CSS-D list
Subject: Re: [css-d] Rules for making content hidden and visually hidden
I believe you mean display:none;
Oh yes. Old age creeping up and late night here in
For what it's worth, display:none; will render the page as if the element
doesn't exist.
visibility:hidden; will render the page with the element still taking up
space on the page, but not visible.
I have not ever used elaborate methods of hiding elements, not that they
don't have a use. Display:
;mystyle" . when you want to
> unhide it, you just need to comment it out like this:
>
> .mystyle {
> /* display: hidden; */
> }
>
>
>
>
> -Original Message- From: Rick Lecoat
> Sent: Monday, August 03, 2015 9:14 AM
> To: CSS-D list
> Subject: [cs
ay: hidden; */
}
-Original Message-
From: Rick Lecoat
Sent: Monday, August 03, 2015 9:14 AM
To: CSS-D list
Subject: [css-d] Rules for making content hidden and visually hidden
For the last few years I've been using a bunch of content visibility rules,
which I think I originally extr
For the last few years I've been using a bunch of content visibility rules,
which I think I originally extracted from Andy Clarke's 320-and-up framework.
I'm wondering if the methods that they use are still considered best practice
for achieving the desired goals, and whether anyone has better r
15 matches
Mail list logo
