When we complete a task independently and successfully, the exhilaration is boundless. Filling forms on websites and apps for people with disabilities and even for the non-disabled is such a task and the independence in that is exciting, even if it is simple. The other day, I was amazed when I encountered such a scenario […]
Continue reading Anatomy of Creating Accessible Forms: Practice the bestAnatomy of creating accessible forms: Is this field ‘Required?’
If anyone asks me to vote on a day of frustration, I would vote for the day when I tried to order for a cup cake on a new site and I utterly failed. Well, I selected my choice of cake; added it to cart;tried to fill my delivery address and there started the road […]
Continue reading Anatomy of creating accessible forms: Is this field ‘Required?’Anatomy of Accessible Forms! Placeholder is a Mirage
Oh! I am alright! No, wait! I forget things very easily. What do they call that? Short term memory loss? The other day, I was filling an online exam registration form. They asked me to write my office address, home address, work phone and home phone. I filled all the details, alright. But when I […]
Continue reading Anatomy of Accessible Forms! Placeholder is a MirageWCAG 2.1 is a W3C Recommendation
Web Content Accessibility Guidelines (WCAG) 2.1 is now a W3C Recommendation. This is an evolution of W3C’s accessibility guidance, including expansion of mobile, low vision, and cognitive and learning provisions. It maintains W3C’s accessibility guidance, while maintaining W3C’s standard of implementable, technology neutral, objectively testable and universally applicable accessibility guidance. Publication as a W3C Recommendation […]
Continue reading WCAG 2.1 is a W3C RecommendationUnderstanding SC 2.1.1 Keyboard
2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints. (Level A) Note 1: This exception relates to the underlying function, not the input […]
Continue reading Understanding SC 2.1.1 KeyboardUnderstanding SC 2.1.2 No Keyboard Trap
2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of […]
Continue reading Understanding SC 2.1.2 No Keyboard Trap