Provide accessible names for buttons, links, and menu items to improve screen reader users' understanding of their purpose. This enhances navigation and usability for users relying on assistive technologies.
Ensure sufficient contrast between text and background colors to improve readability, especially for users with visual impairments. This enhances overall accessibility of the page.
Use clear, unique, and focusable text (or alt text for image links) to improve navigation for screen reader users. This leads to better usability and reduced confusion.
Implement current ARIA roles to ensure proper processing by assistive technology and maintain full functionality.
Provide descriptive, non-redundant alt text for images to avoid confusion and enhance understanding for screen reader users
Use unique values for access keys to ensure proper keyboard navigation and avoid conflicts.
Provide clear accessible names for ARIA dialog and alertdialog elements to help screen reader users understand their purpose.
Assign clear accessible names to ARIA input fields to ensure screen readers announce them with meaningful, helpful names.
Provide descriptive accessible names for ARIA meter elements to ensure screen readers can properly convey their purpose and value.
Assign informative accessible names to ARIA progressbar elements for screen readers to accurately announce their purpose and status.
Ensure ARIA parent roles contain their required child roles to maintain correct functionality and improve accessibility.
Place ARIA child roles within their required parent roles to ensure proper functionality and provide accurate accessibility information.
Avoid placing focusable descendants within elements with role="text" to ensure all interactive elements are properly recognized by screen readers.
Provide descriptive accessible names for ARIA toggle fields to ensure screen readers can properly announce their purpose and state.
Assign clear accessible names to ARIA tooltip elements to ensure screen readers can accurately convey their content and purpose.
Provide informative accessible names for ARIA treeitem elements to help screen readers properly announce their content and role within the tree structure.
Include headings, skip links, or landmark regions to help users bypass repetitive content and navigate more efficiently.
Construct definition lists with properly-ordered <dt> and <dd> groups, along with allowed elements, to ensure accurate screen reader output.
Wrap definition list items (<dt> and <dd>) in a parent <dl> element for proper announcement by screen readers.
Use unique ARIA IDs within a page to prevent confusion and ensure proper functionality of assistive technologies.
Provide a single, clear label for each form field to ensure consistent and accurate announcements by screen readers.
Include informative titles for frame and iframe elements to help screen reader users understand their content and purpose.
Ensure the xml:lang attribute on the <html> element matches the lang attribute for consistent language interpretation by screen readers.
Provide clear, descriptive text for input buttons to help screen reader users understand their purpose and functionality.
Add informative alt text to <input type="image"> elements to provide screen reader users with clear information about the button's purpose.
Make links visually distinguishable from surrounding text without relying solely on color, improving accessibility for users with color vision deficiencies.
Avoid using <meta http-equiv="refresh"> and instead provide user-controlled methods for page updates, creating a better experience for all users, especially those using assistive technologies.
Include informative alternate text for <object> elements to convey their meaning to screen reader users who cannot access the embedded content directly.
Associate descriptive labels with select elements to ensure screen reader users can understand their purpose and interact with them effectively.
Provide distinct content for table summary attributes and <caption> elements, with the summary describing structure and the caption providing a title.
Ensure the headers attribute in table cells only refers to cells within the same table, improving navigation for screen reader users.
Create a proper relationship between table headers (th elements or those with appropriate ARIA roles) and their corresponding data cells to aid in table navigation for screen reader users.
Apply valid BCP 47 language codes in language attributes (lang) to ensure correct pronunciation by screen readers.
Include a <track> element with kind="captions" for video elements to provide accessible captions for deaf and hard-of-hearing users.