Do headings introduced to meet SC 2.4.10 (AAA) need to be marked up With an h<n> tag too? On this page, HTML heading markup h<n> tags are used for the titles of each scenario I / Ii / III and for each of the two ARIA1 and ARIA2 techniques. This is good enough to comply with SC 1.3.1 (A) for the three scenarios illustrated below.… Continue Reading Accessible HTML Heading Markup
This illustrates why accessibility support in terms of differences in navigation techniques and HTML / ARIA behavior on a mobile device needs to be taken into account during design. Continue Reading How Accessibility Impacts Responsive Design
Sometimes, the visible anchor text as mandated by the user interface design is not very meaningful to vision impaired users. One could use aria-label or the title attribute or even off-screen text on text links. But what's the best practice based on current assistive technology support? Continue Reading Text Links: Best Practices for Screen Readers
Aria-invalid=true Setting aria-invalid to "true" is a quick and easy method for indicating that a field has failed validation. Yet, its usefulness from an accessibility standpoint is limited to a situation where: The identity of the failed field is so obvious visually, and No explicit description of the error is really necessary. Examples include fields whose label / instructional text expressly indicate: Data format for… Continue Reading Using Aria-invalid for Error Indication
Because the attribute "aria-required" is supported by commonly used browser-assistive technology combinations, many consider its use as the easiest and most optimal method for indicating that input is required for a field. Yet, recommending its use may not be so straightforward from a strict WCAG 2 compliance viewpoint. Conveying in an accessible manner that input for a field is required is necessary only when there… Continue Reading Aria-required=true: WCAG 2 Compliance versus Best Practice
"Techniques for Labeling Standard HTML Form Controls" is an advanced accessibility technique post by Deque Principal Consultant Sailesh Panchang. In this post, Sailesh gives detailed information about how to code standard HTML form controls, making sure they are correctly labelled for accessibility.