WebAIM: Keyboard Accessibility - Tabindex - 0 views
-
tabindex="0" and tabindex="-1" have special meaning and provide distinct functionality in HTML. A value of 0 indicates that the element should be placed in the default navigation order. This allows elements that are not natively focusable (such as <div>, <span>, and <p>) to receive keyboard focus. Of course one should generally use links and form controls for all interactive elements, but this does allow other elements to be focusable and trigger interaction.
-
A value of 0 indicates that the element should be placed in the default navigation order. This allows elements that are not natively focusable (such as <div>, <span>, and <p>) to receive keyboard focus.
-
A tabindex="-1" value removes the element from the default navigation flow (i.e., a user cannot tab to it), but it allows it to receive programmatic focus, meaning focus can be set to it from a link or with scripting. This can be very useful for elements that should not be tabbed to, but that may need to have focus set to them. A good example is a modal dialog window - when opened, focus should be set to the dialog so a screen reader will begin reading and the keyboard will begin navigating within the dialog. Because the dialog (probably just a <div> element) is not focusable by default, assigning it tabindex="-1" allows focus to be set to it with scripting when it is presented.
- ...1 more annotation...
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.
Digital transformation - 3 views
Digital transformation can be a complex process, but Docufree has been an invaluable partner in my organization's journey. It has to be noted that docufree customer service team https://www.pissedc...
Hiding Content for Accessibility - Snook.ca - 0 views
-
This clip technique is also what's provided in the .visuallyhidden helper class in HTML5 Boilerplate.
-
We've only begun using and testing this technique, so even this may not be perfect. Any feedback and suggestions are quite welcome.
Command F5 Web Accessibility Project - 0 views
Top 10 Mistakes in Web Design (Jakob Nielsen's Alertbox) - 0 views
-
A good grasp of past navigation helps you understand your current location, since it's the culmination of your journey. Knowing your past and present locations in turn makes it easier to decide where to go next. Links are a key factor in this navigation process. Users can exclude links that proved fruitless in their earlier visits. Conversely, they might revisit links they found helpful in the past.
WebAIM: Creating Accessible Tables - Data Tables - 0 views
-
The summary attribute of the <table> tag may be used to provide a summary of a data table structure (not content). Support for summary varies, but in general, it is screen reader specific (it's not accessible to anyone else) and is not well supported. Additionally, the summary attribute is not part of the HTML5 specification. In general, if a table is so complex that it needs an explanation of how it is structured, it probably is not very accessible and should probably be simplified. For these reasons, we do not recommend the use of summary. If it is used, it must never be used for layout tables.
CSS Techniques | Techniques for WCAG 2.0 - 0 views
Accessible forms using WCAG 2.0 | Web Usability - 0 views
-
The label element is not used for the following because labels for these elements are provided via the value attribute
-
This technique inserts new content into the DOM immediately following the element that was activated to trigger the script. The triggering element must be a link or a button, and the script must be called from its onclick event. These elements are natively focusable, and their onclick event is device independent. Focus remains on the activated element and the new content, inserted after it, becomes the next thing in both the tab order and screen-reader reading order. Note that this technique works for synchronous updates. For asynchronous updates (sometimes called AJAX), an additional technique is needed to inform the assistive technology that the asynchronous content has been inserted.
Bootstrap accessibility plugin - 0 views
Resources - The Accessibility Project - 0 views
html - What is sr-only in Bootstrap 3? - Stack Overflow - 0 views
-
.sr-only { position: absolute; width: 1px; height: 1px; padding: 0; margin: -1px; overflow: hidden; clip: rect(0,0,0,0); border: 0; }
Creating an Accessible Infographic | Access Matters Blog - 0 views
-
Screen readers are very literal and, as such, tend to read out numbers in a list with no particle words or punctuation.
-
Using a CSS technique to position text off the screen, it’s simple to add some particle words (such as “from” or “to”) for screen reader users. In the case of a range of numbers, the dashes can be presented using graphics and not part of the text content of the page. For example, in the second data point shown in the image below, instead of a screen reader announcing “twenty-six percent fifty-five sixty-four” it would be “twenty six percent fifty-five to sixty-four.”
-
Another example is implied headings. Sighted users can understand quickly from images that a data set title should be “gender” but if the heading doesn’t appear in the design, it should be added and visually hidden using CSS.
« First
‹ Previous
41 - 60 of 122
Next ›
Last »
Showing 20▼ items per page