any user accessing the Accessibility API
Group items tagged
HTML5 Accessibility: aria-hidden and role="presentation" | Unrepentant - 0 views
-
-
aria-hidden=”true” + role=”presentation”
-
Use both attributes for cases where browser/OS/screen-reader combinations don't support WAI-ARIA.
-
How do you figure? | scottohara.me - 0 views
-
A figure can be used with or without a figcaption. However, without a caption, or an alternate means of providing an accessible name (e.g. aria-label) a figure may not provide much value in conveying its semantics alone. In some cases, it may not convey any semantics at all if its given no accessible name.
WebAIM: Keyboard Accessibility - 0 views
-
Long lists of links or other navigable items may pose a burden for keyboard-only users.
-
The following best practices can facilitate efficient keyboard navigation: Provide a "skip to main content" link on the page. Use a proper heading structure. Provide ARIA landmarks or HTML5 structural elements (<main>, <nav>, etc.)
-
"when testing with a keyboard, you are not just trying to interact with the page successfully, you also want to ensure all interactions are predictable. This requires an understanding of common keyboard interactions."
Don't Rely on Default Browser Error Messages - Intopia - 0 views
-
Another issue is that the messages are temporary. As soon as you put focus on the input with mouse, keyboard or touch, the message disappears. People with cognitive impairments will find it difficult to use these, and I think anyone trying to fill in the form while they’re distracted will have trouble as well. People who rely on the keyboard for navigation (which includes both sighted users and screen reader users) will also lose these messages as they move around the form.
-
If you’re confident of your error messages, you can remove the browser validation by adding the novalidate attribute to the wrapping form element, like this: <form novalidate>...</form>
-
You can style this with CSS, using the :valid and :invalid pseudo-classes
- ...2 more annotations...
-
"When I found out the major browsers were beginning to include error validation into their support for forms, I was pretty excited. Form validation is always a fiddly part of accessibility, so I'm always looking out for ways to make it easier for developers to do properly. I read MDN's form data validation tutorial and a CSS Tricks article on client-side form validation and immediately made some test forms. Sadly, I was disappointed with the results. The default error validation in browsers is almost completely inaccessible. I was hoping we'd get default "you've forgotten to fill this in" messages that could be customised. I might have been a bit too optimistic! Validation at the browser level has many of the same issues we find at the website level."
‹ Previous
21 - 30 of 30
Showing 20▼ items per page