Accessibility (often abbreviated to A11y — as in “a” then 11 characters then “y”) in Web development means enabling as many people as possible to use Web sites, even when those people’s abilities are limited in some way.
Explore our resources:
1.4.11 Non-Text Contrast (AA): The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by…
1.4.12 Text Spacing (AA): In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: Line height (line spacing) to at least 1.5 times the font size; Spacing following paragraphs to at least…
1.4.13 Content on Hover or Focus (AA): Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: Dismissible: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error…
Simplified and easy to use guide on using WCAG-Web Content Accessibility Guidelines in your day-to-day projects. Each article has design guidance for Web, IOS and Android along with links to resources. WCAG Principle 1: Perceivable Information and user interface components must be presentable to users in ways they can perceive. Guideline 1.1: Text Alternatives Provide…
1.3.5 Identify Input Purpose (AA): The purpose of each input field collecting information about the user can be programmatically determined when: (Level AA) The input field serves a purpose identified in the Input Purposes for User Interface Components section The content is implemented using technologies with support for identifying the expected meaning for form input…
1.3.4 Orientation (A): Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. (Level AA) Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality…
1.3.3 Sensory Characteristics (A): Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A) Requirements Do not use shape, size, colour or visual location to communicate instructions. Why is it important? This ensures that instructions can be understood…
1.3.2 Meaningful Sequence (A): When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A) Requirements Requirements for both native and web When users navigate the page using a keyboard’s ‘tab’ key, or cursor arrows (when a screen reader is on), elements receive the keyboard…
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A) Requirements Requirements for both native and web Web only requirements Why is it important? This ensures that the structure of the content that’s conveyed visually by the designs is also available to screen…
1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media. (Level AA) Requirements Video that includes important visual information has audio description. Why is it important? This ensures that information communicated visually in the video is available to people who cannot see it. Summary For videos that are pre-recorded,…
Sign up with your email address to receive our weekly news