What fresh hell is THIS now? - Patrick Lauke
clip: rect(0, 0, 0, 0); position: absolute;
. Have there been other suggested syntaxes (for the future), like visibility: visually-hidden
?
clip
, that was a good one, until you had to build a site that had RTL content.
@media (screenreader: none)
now. Glad @stevefaulkner visited this years ago. I figured this was an old issue, but I was surprised I didn’t know the resolution, or if there was one, or if we’re still waiting.
@media (screenreader: none)
concept, it seems riddled with issues; firstly, it confuses me as to whether its styles are applied to the screen reader only or to the visual page when a screen reader is active. It seems like the later, and that would be a different use case than what I’m targeting. Also, it seems like yet another vector to track people.
[maya] Hello! Does anybody have recommendations for what font size we should set web pages to?
See this issue: 18F/frontend#118
[maya] It sounds clear that setting html to 100% is the most accessible, to deal with browser sizing defaults people have set themselves.
BUT a lot of developers like to set their pixels to 10px or 62.5% in order to get a 1rem = 10px.
font-size
, color
, or background-color
on html
or :root
, because I seem to remember him once saying that I should not do that. https://twitter.com/jon_neal/status/725751310889394176
.foo { font-size: 16px; font-size: 1rem; }
— works fine this way...
<label>
s)
Can anyone sanity check this for me?
marking up “program cards” which would be collection of the following bits of info: program title, host school, summary of progress (you’ve completed 2 out of 3 of the courses in this program”), followed by a link to the program home page. You may be enrolled in multiple “programs” so there would be multiple “cards” on the listing page. I’m trying to consider the proper markup for the card container. Wondering if this thinking is sound: div with role of group, labelled by the program name, describedby the progress summary. thoughts?
<dialog>
element in Angular, and I'm trying to ensure that it's properly accessible... I have very little experience with screen-readers, but what I'm hearing from VoiceOver doesn't sound all that helpful. Any recommendations for figuring out what I should be expecting as output from VoiceOver?
[karlgroves] at a high level: if it performs an action in the current context then it would be a button. If it changes context it is a link.
Silly questions are OK. Nobody here started off an accessibility expert