w3c/a11ySlackers

Slackers unite

zakim-robot

@zakim-robot

[Jay] aria-multiselectable listbox.mp4

zakim-robot

@zakim-robot

[Alex Umstead] Is there a way to set up the Google accessibility scanner so that it doesn’t make an extremely loud shutter noise whenever taking a snapshot of an app? This happens even when my device is muted and all volume sliders are turned down. Running on Android 10.

zakim-robot

@zakim-robot

[kirabug] And I’m back. Now we’re having a pretty lively debate over whether “thing that opens a menu” should be a link or a button. It’s a link in our global navigation, it’s a button in other locations. One line of thought is that accordions and tabs are links because they hide or display content, therefore the menu content should be displayed via a link. Another line of thought is that a button does a thing (display a menu) and therefore it should be a button. Level Access seemed to align with that thought, as they recommended our in-page navigation links that opened menus should have a role of “button”. Is that the consensus?

zakim-robot

@zakim-robot

[jamesn] To be honest. I don’t care which it is as long as it is consistent.

[jamesn] But then again I’m not a purist on the link vs button debate.

zakim-robot

@zakim-robot

[anevins] I recently attended a talk by Alastair Somerville on the accessibility of VR that was being suggested as an alternative to the very inaccessible MailRail underground system (it's very cool! A system to deliver mail underneath London in the 1900s) . In the end I learnt that VR headsets are not very accessible! If you'd like to read about it, Alastair has kindly put slides up with a YT video (though at a weird angle):
• Slides: https://www.dropbox.com/s/jx36vx7ljl5bpej/Being%20Human%20Together%20-%20the%20limits%20of%20accessible%20VR%202020%20Bristol.pdf?dl=0
• Video: https://www.youtube.com/watch?v=Ke2_y-Noa88&t=17s

zakim-robot

@zakim-robot

[claudio] @anevins you should look at the accessibility pages for Magic Leap... I would not conclude that headsets are inaccessible per se, but that there’s a lot that could be done to make the experience accessible that isn’t.

zakim-robot

@zakim-robot

[Alyssa Rudnitskas] Help Requested: Accessible Meetup Spaces in Philadelphia
The Philly Accessibility Meetup is dedicated to hosting events in spaces that are as accessible and inclusive as possible. They are looking for help with selecting future Philadelphia venues, not just for the meet up but for anyone who could benefit from such a list of spaces. Please fill out and share: https://chzs.tk/a11yphlspaces

zakim-robot

@zakim-robot

[techa11y] In a modal dialog pattern, I’ve made content outside the dialog aria-hidden=“true” and have trapped focus in the dialog. However, some of the content outside the dialog are focusable elements. The testing tool I’m using is flagging this as an error, saying that I shouldn’t use aria-hidden=“true” on focusable elements. Do I need to add tabindex=“-1” on these or something similar, or is it sufficient that I’m trapping focus in the dialog? As it is, keyboard users shouldn’t ever be able to get to these elements, so it seems redundant. Thoughts?

zakim-robot

@zakim-robot

[Matt Geckley] Can anyone recommend a resource to get familiar with aria best practices?

zakim-robot

@zakim-robot

[heidi] hello! Looking for an example of accessing search terms within a single page.

zakim-robot

@zakim-robot

[JimKIely] I have a main menu navigation with submenus that is working with a keyboard but when I run on any screen reader the submenus do not work. I can tab through but the "enter" and "spacebar" click events do not work.

[unknown] Getting an issue flagged that my <article> does not support aria-labelledby. Is this true? I totally thought it was.

zakim-robot

@zakim-robot

[ghanek] @ Tool? OS? Browser? That's not a great deal of info to investigate or replicate. And what happens if you use aria-label instead?

[unknown] Aria-label is fine, which is what I have switched it too. Browser is firefox, OS is mac, and tool is ARC toolkit

[autosponge] You can't aria-label a generic container with consistent results

[unknown] It could be that there was two h2's with the same ID, one was just displayed none and the other was visible. Had to have the two headings because of responsive breakpoints.

[ghanek] Yes, software often reacts poorly to multiple IDs.

zakim-robot

@zakim-robot

[unknown] Totally thought it wouldn’t since I was displaying them none properly, but no worries. Don’t need the ID anymore anyway.

[ccwilcox] <article> elements are not generic, they have role="article" by default, right?

[unknown] They do yep

zakim-robot

@zakim-robot

[scott again] filed a but on ARC

zakim-robot

@zakim-robot

[unknown] Thanks @scott again!

zakim-robot

@zakim-robot

[Stacy] Is anyone aware of a bug that excludes label text nested in a <strong> element from the input's accessible name? At first glance, this seems to be a Chrome issue.

I have a <label> that reads: "I do <strong>not</strong> want a forbearance to be applied," and what is announced by NVDA (and shown by the Accessibility tree in the dev tools) is "I do want a forbearance to be applied," which is a very critical difference.

zakim-robot

@zakim-robot

[unknown] I'd love to know how many UK based people use this slack channel. If you're UK based can you wave :wave: or add a hi to the thread? Maybe we need a channel too...

[Stacy] Codepen with example: https://cdpn.io/stacycarston/debug/XWbedyr/RBMOJXxyeEJk

Also, if anyone has advice about the best way to report this, I'd appreciate it. A bolded "not" is a very common pattern.

zakim-robot

@zakim-robot

[aleventhal] @techa11y interesting point. seems like the testing tool has no way of knowing you’re doing the right thing unless you use tabindex=-1 on those

[aleventhal] @techa11y you could turn off that rule maybe? it’s a good default rule tho, imo … i see a lot of pages that mess that up and then the user has no chance to access the content

zakim-robot

@zakim-robot

[kaylee (they/them)] does anyone have recs for a tool that shows the heading structure of the current web page? preference for low barrier to entry - i’m retrofitting my company’s site and am about to start enforcing correct heading structure on all my fellow developers. the easier the tool is to use/learn the more likely i’ll be successful! i could have sworn the firefox dev tools used to have a way to just see the headings but i can’t find it now in the accessibility features. (I use ANDI for this, but I’d prefer something in browser dev tools or something that can be installed and then “just works”. we’ve also already got react-axe flagging when something is wrong with the heading structure, but it doesn’t give you a way to see the structure as a whole which makes it harder to fix)

zakim-robot

@zakim-robot

[unknown] Got laid off yesterday, and thinking of picking an open source project to contribute to while I’m looking for work. Would love to contribute to an accessible component library. I’ve heard Reach and Chakra are good — does anyone have experience contributing to either, or have thoughts/tips/suggestions?
Thank you!

P.S. And if you have any mid/junior front end or full stack roles up your sleeve, please let me know! Most of my experience is React+Typescript but I’m flexible and curious

zakim-robot

@zakim-robot

[davidakennedy] Does anyone know what ruleset(s) the Axe browser extensions use? I can’t find it in the docs, and trying to make our automated testing match up.

[Adam Page] Hi all, hoping for a consult on how to responsibly mark up introductory instructions in a form. Thread to follow...

zakim-robot

@zakim-robot

[williebike] I didn't know that there's IMG ALT available for Instagram.

[williebike] Screen Shot 2020-03-05 at 2.39.31 PM.png

[Sarah] The “Image may contain” is the generated by instagram by looking at the image

zakim-robot

@zakim-robot

[unknown] Anyone on here involved in tech strategy decisions or framework decisions ? Given the implication of an organisation's choice of JS framework, DevOps tooling etc I'm trying to understand what others do and if any accessibility input it given elsewhere?

jaunitaflessas

@jaunitaflessas

Hi everyone!

Shawn Thompson

@shawnthompson

Hello all!

Christopher Joel

@cdata

Hello, is this a good room to ask for a11y advice regarding issues in specific browser/screen reader combinations?

tanisha03

@tanisha03

Hey people, what do you think are some CSS properties which breaks the source order for the screen readers like floats and absolute positioning, grids and flexboxes

Paceaux

@paceaux

Howdy all. I have a small accessibility question. I'm in an unfortunate situation where a design agency is long gone, but I'm left delivering what they've done.

so they've left me a contact form where a "message" field doesn't look like a message at all. So I'm wondering if there is any impact to folks using screenreaders, assistive devices if I use input rather than textarea

Michael Milette

@michael-milette

Hi all, my first time here and happy to find this community. I was wondering if anyone had any thoughts regarding the practice of doing something like <img alt="Alternative text" title="Alternative text">. Is this compliant with WCAG 2.0/2.1? I was taught that it could potentially cause a stutter however I cannot find any reference to such an issue.

Jookia

@Jookia

Hi, I'm a sighted noob that's just been spending time being angry at inaccessible apps and developers not fixing them. I don't have anything to add except to wish everyone a good day

Stephen Sylvia

@ssylvia_gitlab

If I have an anchor tag with a click handler (in react) do I need to add role="link" to anchor tag?

<a href="https://example.com" onClick={function} role="link" />

2 replies

Meg M

@vanderbeam

Hey all! So happy I could find this place! While I hope to become a frequent a11y Slacker, I'm here with a purpose today. My company has been having a discussion lately about accessibility interfaces and we'd love some input. I mean those little plugins or modals you can add to a site to increase font sizes or invert colours. Ultimately, we're of the opinion that they shouldn't be necessary because a site should be built accessible. However, in cases a client absolutely insists on a script font or a baby blue on white, I can see their benefits. I also see their benefits in terms of compensating for the smaller, unpredictable margins of error (like a really abstract or rare condition we didn't take into account, hard though we try). Our small staff can have all of our opinions, but ultimately none of us have a condition that would require an accessible interface so at the end of the day it's all just theorizing. So our ultimate question is... "Accessibility Interface Add-Ons: Yay or Nay?" I'd love to hear your input.

Jookia

@Jookia

could be cool. i've thought of having accessibility add-ons to toggle verbose link text

Meg M

@vanderbeam

I only see them working 50% of the time, unfortunately. I've been on website where you could click that "Increase Font Size" button until the season changed and the fonts would all remain the same.

Jookia

@Jookia

yikes. another idea is to just offer multiple themes, like dark/light mode too. or high contrast mode

there's a lot of utility you could probably get out of effectively a themer

Where communities thrive

People

Repo info

Activity