react-a11y-dialog provides a thin (~600b) React component and hook for a11y-dialog relying on React portals to ease the use of accessible dialog windows in React applications.
Version compatibility:
react-a11y-dialog@2.0.0
.react-a11y-dialog@4.2.0
.Special thanks to Moritz Kröger (@morkro), Mayank (@mayank99) and EJ Mason (@mxmason) for their kind help in making that library better.
npm install --save react-a11y-dialog
Name | Type | Required | Default | Description |
---|---|---|---|---|
id | string | true | — | <details><summary>Expand</summary>The HTML id attribute of the dialog element, internally used by a11y-dialog to manipulate the dialog.</details> |
title | node | true | — | <details><summary>Expand</summary>The title of the dialog, mandatory in the document to provide context to assistive technology. Could be hidden with CSS (while remaining accessible).</details> |
dialogRoot | Element | string | false | document.body | <details><summary>Expand</summary>The container for the dialog to be rendered into (React portal’s root).</details> |
dialogRef | function | false | () => {} | <details><summary>Expand</summary> A function called when the component has mounted, receiving the instance of A11yDialog so that it can be programmatically accessed later on.</details> |
titleId | string | false | ${props.id}-title | <details><summary>Expand</summary>The HTML id attribute of the dialog’s title element, used by assistive technologies to provide context and meaning to the dialog window.</details> |
closeButtonLabel | string | false | Close this dialog window | <details><summary>Expand</summary>The HTML aria-label attribute of the close button, used by assistive technologies to provide extra meaning to the usual cross-mark.</details> |
closeButtonContent | node | false | \u00D7 (×) | <details><summary>Expand</summary>The string that is the inner HTML of the close button.</details> |
closeButtonPosition | string | false | first | <details><summary>Expand</summary>Whether to render the close button as first element, last element or not at all. Options are: first , last and none . ⚠️ Caution! Setting it to none without providing a close button manually will be a critical accessibility issue.</details> |
classNames | object | false | {} | <details><summary>Expand</summary>Object of classes for each HTML element of the dialog element. Keys are: container , overlay , dialog , title , closeButton . See a11y-dialog docs for reference.</details> |
role | string | false | dialog | <details><summary>Expand</summary>The role attribute of the dialog element, either dialog (default) or alertdialog to make it a modal (preventing closing on click outside of <kbd>ESC</kbd> key).</details> |
The library exports both A11yDialog
, a React component rendering a dialog while performing the a11y-dialog
bindings under the hood, and a useA11yDialog
hook providing only the binding logic without any markup.
Using the hook can be handy when building your own dialog. Beware though, it is an advanced feature. Make sure to stick to the expected markup.
import { useA11yDialog } from 'react-a11y-dialog' const MyCustomDialog = props => { // `instance` is the `a11y-dialog` instance. // `attr` is an object with the following keys: // - `container`: the dialog container // - `overlay`: the dialog overlay (sometimes called backdrop) // - `dialog`: the actual dialog box // - `title`: the dialog mandatory title // - `closeButton`: the dialog close button const [instance, attr] = useA11yDialog({ // The required HTML `id` attribute of the dialog element, internally used // a11y-dialog to manipulate the dialog. id: 'my-dialog', // The optional `role` attribute of the dialog element, either `dialog` // (default) or `alertdialog` to make it a modal (preventing closing on // click outside of ESC key). role: 'dialog', }) const dialog = ReactDOM.createPortal( <div {...attr.container} className='dialog-container'> <div {...attr.overlay} className='dialog-overlay' /> <div {...attr.dialog} className='dialog-content'> <p {...attr.title} className='dialog-title'> Your dialog title </p> <p>Your dialog content</p> <button {...attr.closeButton} className='dialog-close'> Close dialog </button> </div> </div>, document.body ) return ( <> <button type='button' onClick={() => instance.show()}> Open dialog </button> {dialog} </> ) }
The A11yDialog
React component does not render anything on the server, and waits for client-side JavaScript to kick in to render the dialog through the React portal.
When you’re using react-a11y-dialog
in your unit tests, it might be necessary to mock React Portals and inject them to the root DOM before your tests are running. To accomplish that, create helper functions that attach all portals before a test and remove them afterwards.
const ROOT_PORTAL_IDS = ['dialog-root'] export const addPortalRoots = () => { for (const id of ROOT_PORTAL_IDS) { if (!global.document.querySelector('#' + id)) { const rootNode = global.document.createElement('div') rootNode.setAttribute('id', id) global.document.body.appendChild(rootNode) } } } export const removePortalRoots = () => { for (const id of rootPortalIds) { global.document.querySelector('#' + id)?.remove() } }
And then use them in your tests.
describe('Testing MyComponent', () => { beforeAll(() => addPortalRoots()) afterAll(() => removePortalRoots()) })
The following example is a minimal setup of react-a11y-dialog
. Additionally, you will need to add the required styles as per the recommendations from the a11y-dialog
styling docs. How you integrate these styles is left to your discretion and depends on the styling layer you’ve chosen for your project (classes, inline styles, CSS Modules, CSS-in-JS…). For anything but inline styles, styles will typically need to be passed via the classNames
object prop, and as such will end up being applied to the elements rendered by React.
import { A11yDialog } from 'react-a11y-dialog' const App = props => { const dialog = React.useRef() return ( <div> <button type='button' onClick={() => dialog.current.show()}> Open the dialog </button> <A11yDialog id='my-accessible-dialog' dialogRef={instance => (dialog.current = instance)} title='The dialog title' > <p>Some content for the dialog.</p> </A11yDialog> </div> ) } ReactDOM.render(<App />, document.querySelector('#root'))
Version 7 now relies on a11y-dialog@8.0.0. It should be largely backward compatible with version 6 though.
AI小说写作助手,一站式润色、改写、扩写
蛙蛙写作—国内先进的AI写作平台,涵盖小说、学术、社交媒体等多场景。提供续写、改写、润色等功能,助力创作者高效优化写作流程。界面简洁,功能全面,适合各类写作者提升内容品质和工作效率。
字节跳动发布的AI编程神器IDE
Trae是一种自适应的集成开发环境(IDE),通过自动化和多元协作改变开发流程。利用Trae,团队能够更快速、精确地编写和部署代码,从而提高编程效率和项目交付速度。Trae具备上下文感知和代码自动完成功能,是提升开发效率的理想工具。
全能AI智能助手,随时解答生活与工作的多样问题
问小白,由元石科技研发的AI智能助手,快速准确地解答各种生活和工作问题,包括但不限于搜索、规划和社交互动,帮助用户在日常生活中提高效率,轻松管理个人事务。
实时语音翻译/同声传译工具
Transly是一个多场景的AI大语言模型驱动的同声传译、专业翻译助手,它拥有超精准的音频识别翻译能力,几乎零延迟的使用体验和支持多国语言可以让你带它走遍全球,无论你是留学生、商务人士、韩剧美剧爱好者,还是出国游玩、多国会议、跨国追星等等,都可以满足你所有需要同传的场景需求,线上线下通用,扫除语言障碍,让全世界的语言交流不再有国界。
一键生成PPT和Word,让学习生活更轻松
讯飞智文是一个利用 AI 技术的项目,能够帮助用户生成 PPT 以及各类文档。无论是商业领域的市场分析报告、年度目标制定,还是学生群体的职业生涯规划、实习避坑指南,亦或是活动策划、旅游攻略等内容,它都能提供支持,帮助用户精准表达,轻松呈现各种信息。
深度推理能力全新升级,全面对标OpenAI o1
科大讯飞的星火大模型,支持语言理解、知识问答和文本创作等多功能,适用于多种文件和业务场景,提升办公和日常生活的效率。讯飞星火是一个提供丰富智能服务的平台,涵盖科技资讯、图像创作、写作辅助、编程解答、科研文献解读等功能,能为不同需求的用户提供便捷高效的帮助,助力用户轻松获取信息、解决问题,满足多样化使用场景。
一种基于大语言模型的高效单流解耦语音令牌文本到语音合成模型
Spark-TTS 是一个基于 PyTorch 的开源文本到语音合成项目,由多个知名机构联合参与。该项目提供了高效的 LLM(大语言模型)驱动的语音合成方案,支持语音克隆和语音创建功能,可通过命令行界面(CLI)和 Web UI 两种方式使用。用户可以根据 需求调整语音的性别、音高、速度等参数,生成高质量的语音。该项目适用于多种场景,如有声读物制作、智能语音助手开发等。
AI助力,做PPT更简单!
咔片是一款轻量化在线演示设计工具,借助 AI 技术,实现从内容生成到智能设计的一站式 PPT 制作服务。支持多种文档格式导入生成 PPT,提供海量模板、智能美化、素材替换等功能,适用于销售、教师、学生等各类人群,能高效制作出高品质 PPT,满足不同场景演示需求。
选题、配图、成文,一站式创作,让内容运营更高效
讯飞绘文,一个AI集成平台,支持写作、选题、配图、排版和发布。高效生成适用于各类媒体的定制内容,加速品牌传播,提升内容营销效果。
专业的AI公文写作平台,公文写作神器
AI 材料星,专业的 AI 公文写作辅助平台,为体制内工作人员提供高效的公文写作解决方案。拥有海量公文文库、9 大核心 AI 功能,支持 30 + 文稿类型生成,助力快速完成领导讲话、工作总结、述职报告等材料,提升办公效率,是体制打工人的得力写作神器。
最新AI工具、AI资讯
独家AI 资源、AI项目落地
微信扫一扫关注公众号