Home
Kazuhito Kidachi's Library tagged → View Popular, Search in Google
"So we have two problems so far with default settings. HTML5 validation is disabled and two labels are pointing to one input. The third problem is that the error message is being placed below the input."
"The roles “group” and “radiogroup” are well supported and may be used to group form controls in situations where one might use HTML’s fieldset – legend elements. It is advisable to include some visual cue via CSS to convey grouping too."
"All the screen readers I’ve tested only speak required once. Here aria-required is your fallback for browsers who do not support HTML5 like Internet Explorer."
"When the image has focus the screen reader user can press enter to activate the link, because a link action showlongdesc is exposed on the image, it uses the URL from the link referenced via aria-describedby."
"If you want to hide content from all users, use the HTML5 hidden attribute (along with CSS display:none for browsers that do not yet support hidden) There is no need to use aria-hidden."
"From an initial analysis the correct use of ARIA landmark roles is surprisingly high. "
"It is important to be aware of the different ways that one can access the mobile web using a screen reader: iOS Safari/VoiceOver, Android Ice Cream Sandwich (natively with AndroidVox and Chrome) or pre-Android 4.0 with Mobile Accessibility Web Browser and a D-Pad, trackball, or ARROW KEYS."
"A couple of people have asked me recently if it’s possible to nest ARIA roles. The answer: yes."
"WAI-ARIA doesn't do anything to dictate what type of object is created by the browser."
"WAI-ARIA defines a set of rules for mapping roles, states and properties to an accessibility API, and does not define any functionality other than this"
"for a better error message, I am using the non-standard x-moz-errormessage attribute"
"VoiceOver supports all landmarks except “form”."
"Recordings of screen readers using web page components that do and do not make use of WAI-ARIA can be a good educational resource for why ARIA is important to accessibility. Here are all the videos of such demos that I’ve found."
"Implementing ARIA for content does not make business sense for authoring tool vendors, because the non-technical content authors who buy our tools will find it far too complex to use, and because using ARIA for content does not produce better results tha
"When navigated to, role=application causes some screen readers to change modes. Therefore application role must only be used on interactive content for which the application mode is appropriate."
"VoiceOver now lets you use ARIA landmarks, if they are present, to navigate web pages. If Quick Nav is active you can use the w and W keys to navigate to the next or previous landmark."
"I’ve been concerned that there’s been a lot of talk around Mobile Safari supporting WAI ARIA but there’s little documentation out there confirming what is and isn’t supported so I thought I’d run a few basic tests with Mobile Safari on iPhone 4 and iPad
"WAI-ARIA should have defined a uniform processing model for them."
"HTML is one of the most important use cases and the PFWG is working closely with the HTML Working Group to provide full integration in a manner consistent with the HTML 5 design."
"In this article I will show you how to address such problems with WAI-ARIA, and add some further accessibility enhancements to the player, such as captions."
Selected Tags
Related Tags
Top Contributors
Groups interested in wai-aria
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo