Dan Tello

I noticed this as well. Here's a gif showing the bug: 

Similar issue when returning a portal. Simplified example: ```jsx const Dialog = (props) => { return ReactDOM.createPortal(, document.body); } Dialog.propTypes = { /** If only these docs could be detected......

I'm also having issues where the parser is thinking I'm using Flow when I'm using typescript. As a result, I get parsing errors because not all TypeScript is valid Flow...

I worked around this by looking at the [react-docgen demo code](https://github.com/reactjs/react-docgen/blob/master/website/src/components/App.js#L111-L118), and noticing that they were passing `parserOptions.plugins`, and manually specifying the language there: This ended up working for me:...

For `role="dialog"` I'm seeing different behavior. **description** _is_ output, but **label** _is not_. See comment here: https://github.com/FreedomScientific/VFO-standards-support/issues/541#issuecomment-1100201576

I'm having the opposite problem - I'm noticing Jaws *only* reading `aria-describedby` and ignoring `aria-labelledby`, including in the codepen you pasted above. "Dialog title" never gets read. Only the description....

:+1:

If you're using Jest, i generally create a second `*.touch.test.js` file where I mock `whatInput.ask` to return `touch`: ```js jest.mock("what-input", () => ({ ask: jest.fn(() => "touch") })); ```

Sure. I believe I've got a week to spend on open source coming up in the next month or so. I can put together some examples. The basic pattern is...

We 100% need to focus on marketing "Why Microcosm is better than Redux". Feels like 99% of shops and product teams are using Redux. Why would a technical manager at...