![]() ![]() form: A region of the document that represents a collection of form-associated elements, some of which can represent editable values that can be submitted to a server for processing.contentinfo: A region that contains information about the parent document such as copyrights and links to privacy statements.complementary: Any section of the document that supports the main content, yet is separate and meaningful on its own.banner: A region that contains the prime heading or internal title of a page.The value of the attribute is the name of the landmark. Landmarks are inserted into the page using the role attribute on an element that marks the section. Landmarks also can help sighted keyboard-only users navigate to sections of a page using a browser plugin. In another circumstance, a user who is blind may want to quickly find a navigation menu, and can do so by jumping to the navigation landmark. ![]() A blind user who may be familiar with a news site's menu, and is only interested in getting to the top story could easily navigate to the "main" landmark, and bypass dozens of menu links. (Refer to User Agent Notes above for specifics of AT support). This will save assistive technology users and keyboard users the trouble and time of tabbing through a large amount of content to find what they are really after, much like a traditional "skip links" mechanism. For instance, if there is a common navigation menu found on every page, landmark roles (or "landmarks") can be used to skip over it and navigate from section to section. They also provide an easy way for users of assistive technology to skip over blocks of content that are repeated on multiple pages and notify them of programmatic structure of a page. Landmarks help assistive technology (AT) users orient themselves to a page and help them navigate easily to various sections of a page. Landmark roles (or "landmarks") programmatically identify sections of a page. The purpose of this technique is to provide programmatic access to sections of a web page. ![]() Success Criterion 2.4.1 (Bypass Blocks).Success Criterion 1.3.1 (Info and Relationships).Window Eyes as of V.7 does not support ARIA landmarks.NVDA 2 supports all landmarks except it will not support navigation to “application”.VoiceOver V.3 and greater supports all landmarks except “form”.ChromeVox V.1 and greater has complete support.Jaws V.11 and greater has complete support.For non-AT users, there is no native browser support, although there is at least 1 plugin. Sufficient vs Advisory for 2.4.1? The arguments are very similar to those for using headings for 2.4.1. Techniques Task Force: ARIA techniques for 19 Sept 2013.WG survey 10 Sept 2013 survey, returned to TF.Techniques Task Force: ARIA techniques for. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |