Global Accessibility Awareness Day (GAAD) is always special, but GAAD 2020 is more significant as this is truly global and virtual, all because of the pandemic Covid 2019! We from HelloA11Yare more excited to announce GAAD 2020 as a virtual event! We do have interesting topics on accessibility and renowned speakers to make the event […]Continue reading HelloA11y Celebrates GAAD 2020
Success Criterion 1.4.13 Content on Hover or Focus (Level 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 […]Continue reading Understanding SC 1.4.13: Content on Hover or Focus
We’re proud to announce A Future Date, a conference on accessibility and inclusive design! The program will begin on April 21st through 23rd at: * 11am-5pm Eastern time * 8am-2pm Pacific time * 6pm-midnight GMT About the program We’re starting with a bang: the keynote session on Monday will be Lainey Feingold and Tim Elder […]Continue reading Introducing A Future Date!
Success Criterion 1.4.10 Reflow (Level AA): Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require two-dimensional […]Continue reading Understanding SC 1.4.10 Reflow
Success Criterion 1.4.12 Text Spacing (Level 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 […]Continue reading Understanding SC 1.4.12 Text Spacing
Success Criterion 1.3.5 Identify Input Purpose (Level AA): The purpose of each input field collecting information about the user can be programmatically determined when: The input field serves a purpose identified in the Input Purposes for User Interface Components section; and The content is implemented using technologies with support for identifying the expected meaning for […]Continue reading Understanding SC 1.3.5 Identify Input Purpose