HTML5 Structural Elements and ARIA HTML5 introduces several new structural elements that will be very beneficial for accessibility: <nav> (for identifying navigational elements), <header> (a group of introductory or navigational aids), <article>, <aside> (tangentially related content, such as a sidebar), and <footer> provide meaning to major page structural areas. These can also be used to […]
Read Full Post »
ARIA Attributes and Element Styles ARIA attributes are often necessary for optimal accessibility of web applications. They can be used to present information and meaning that otherwise would only be presented visually. For example, a red border or red text might be used to identify errant form fields (such as a form field that was […]
Read Full Post »
ARIA Application Role ARIA role=”application” can be used to identify web applications or widgets within a page. When a screen reader is within an element with this role, it functions in forms mode, meaning that when keyboard keys are pressed, they are passed to the web page rather than handled by the screen reader itself. […]
Read Full Post »
ARIA Alert Roles ARIA role=”alert” can be used for very important messages that a screen reader should read immediately, even if keyboard focus is not set to that element. ARIA alerts are typically triggered with scripting, such as when a critical form error has been detected. Because ARIA alerts are very intrusive (they read immediately […]
Read Full Post »
ARIA Roles and Native Semantics ARIA roles enhance or change the semantics and meaning of page elements. Whenever possible, the proper native HTML elements should be used. For example, while role=”button” could be added to a scripted link that is used to submit a form, a native button element would provide this same functionality in […]
Read Full Post »
WCAG 2.0 and Text Sizes WCAG 2.0 does not specify a minimum text size—1 pixel font would be compliant, though obviously inaccessible to all sighted users. Font sizes should generally be at least 10 pixels. WCAG 2.0 Success Criterion 1.4.4 (Level AA) requires that content must remain readable and functional when text size or page […]
Read Full Post »
