Should typically have a title attribute value that describes the content/functionality of the inline frame, unless the iframe's presence is visually transparent to the user (use role="presentation" in this case). Nests other-page content (often external videos or feeds) within the page. Identified as a region/landmark.ĭo not confuse with headings (, etc.). A page should typically have one and should not skip heading levels (e.g., followed by )Ĭontains header content, navigational links, logo, search, etc. Typically one per page.ĭescribes a section of content and define the structural level of that content.Įnsure the heading accurately describes the content that follows. Should typically have a that describes the set of fields.Ĭontains an image, illustration, code snippet, etc., that is referenced in the main flow of a document.Īn alt attribute should typically be provided for images within a figure, with a that provides a caption or legend for the content.Ĭontains footer content, such as copyright data or related links. Semantically and visually groups a set of related inputs, such as a group of radio buttons or checkboxes. Not typically read differently by screen readers. Use sparingly–it can negatively impact the readability of long sections of text. Use when text needs emphasis (otherwise use or styles). Marks text as emphasized and displays the text as italicized. Can be given semantics using ARIA roles when HTML is not sufficient. Use, , or a form input for interactive elements. ![]() Use another semantic element if the content presents semantics. Ensure keyboard focus remains within modal dialogs and that focus is set to a logical location when the dialog is closed.Ī generic container that does not have any semantics. ![]() The ESC key should typically close the dialog. If the dialog is dismissible, ensure keyboard users can close the dialog. Ĭreates a disclosure widget in which information is visible only when the widget is toggled into an "open" state.Įnsure a is present that describes or summarizes the disclosure content.Ĭontains a dialog box or other interactive component.Įnsure focus is set to the dialog when it appears. If a has text that describes it, associate that text to the table with. Use instead if the element directs the user to another page or another location within the same page. Must contain content that describes the function of the button. Use only for tangential or sidebar information, such as links related to the main content.ĭefines an interactive element for submitting a form or performing a function.Įnsure the button remains keyboard navigable and has a visible focus indicator. Content in these should typically begin with a heading ( - ).Ĭontains sidebar or call-out content indirectly related to. Use these primarily for visual styling and content parsing. These have no useful semantics unless given an ARIA label (which is not typically recommended). Must have an alt attribute value that describes the content/function of the hotspot. ĭefines a hotspot within an image map (defined with ). The attribute value is presented to assistive technology.īest practice is to spell out acronyms and abbreviations in text at their first occurrence instead of using. Should typically be underlined within body content. ![]() Must contain content that describes the function of the link. ![]() Ensure the link can be navigated and activated with a keyboard and has a visible focus indicator. Elementĭefines a link if a non-empty href attribute is present.Įnsure the element functions as a link-it takes the user to another page/file or another location within the page. The following table lists the most common and useful HTML elements that have an impact on accessibility for users with disabilities. This resource is designed to be printed as a PDF file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |