A List Apart: Articles: Now You See Me - 0 views
-
visibility: hidden; Element is hidden from view, but is not removed from the normal flow (i.e., it still takes up the space it normally would) Content is ignored by screen readers display: none; Element is removed from the normal flow and hidden; the space it occupied is collapsed Content is ignored by screen readers height: 0; width: 0; overflow: hidden; Element is collapsed and contents are hidden Content is ignored by screen readers
-
if you want to ensure users have access to content (even if it isn’t displayed visually in the current interface), the final option (positioning content offscreen) is really the way to go.
-
Screen readers have access to the content
- ...6 more annotations...
A11yBuzz - 0 views
WebAIM: Creating Accessible Tables - Data Tables - 0 views
-
Another way to associate data cells and headers is to use the headers and id attributes. This method is NOT generally recommended because scope is usually sufficient for most tables, even if if the table is complex with multiple levels of headers.
Using WAI-ARIA in HTML - 0 views
How Can I Validate (X)HTML + ARIA? | The Paciello Group BlogThe Paciello Group Blog - 0 views
-
The DTD I have used is the HTML 4.01 loose DTD with ARIA attributes added
-
A way I have developed to do this is by creating a bookmarklet that takes the innerHTML of a document (without the DOCTYPE) and adds the custom DOCTYPE to it and then sends it to the W3C validator: HTML4.01-loose+ARIA Checker (add as a favorite to try it out)
Web Content Accessibility and Mobile Web - 0 views
-
Users of mobile devices and people with disabilities experience similar barriers when interacting with Web content. For example, mobile phone users will have a hard time if a Web site's navigation requires the use of a mouse because they typically only have an alphanumeric keypad. Similarly, desktop computer users with a motor disability will have a hard time using a Web site if they can't use a mouse.
HTML Accessibility Task Force - 0 views
Designing and Developing mobile web sites in the real world, part 2 - Opera Developer C... - 0 views
-
In tandem with the launch of their 3G mobile website, Siminn also launched a slightly lighter version of the same site - a 2G-optimized mobile presence to serve less powerful phones. Both sites are anchored to the same reservoir of information, but the 3G site makes less-restricted use of CSS, images, and other coding ornamentations.
-
The only distinction Siminn makes concerning the dimensionality of the user-experience is whether the device is 2G or 3G enabled. As stated before, 2G devices are sent to a slightly lighter version of the 3G site
-
This is exactly what Siminn are doing. By detecting the type of phone, they are presenting the customer with the most appropriate version of the page – either the 3G enhanced or the more basic design.
- ...19 more annotations...
Digital Web Magazine - Understanding Disabilities when Designing a Website - 0 views
-
In the UK In the US 2m people have a vision impairment3 10m people have a vision impairment4 8.2m people have mild to moderate deafness5, 688,000 people have severe to profound deafness6 28m people have a hearing impairment7 3.4m people have a physical disability8 8m people have a physical disability9 1.5m people have a learning disability10 6.8m people have a learning disability11 6m people have dyslexia12 25m people have dyslexia13
-
Most people who are blind will rely on screen reading software such as
-
JAWS or Windows-Eyes
- ...41 more annotations...
How did you get into Web accessibility? | 456 Berea Street - 0 views
-
Personally I have several reasons for advocating Web accessibility. First of all an idealistic one: I want everybody to be able to use the Web. I am not disabled (yet), so I can (and am often forced to) muddle through sites that are badly built, but a person with a disability may not be able to. Since it is possible to build sites that almost everybody can use, I don’t see why we shouldn’t. Then a few reasons that some may call selfish: I do not have any problems related to motor skills, but I have a really hard time using dropdown and flyout menus, especially hierarchical ones, as well as phony Flash or JavaScript scrollbar imitations. Accessible sites in general either do not contain such obstacles or provide ways around them. Despite having no substantial eyesight problems, I find reading tiny text (below 11px is tiny to me), low contrast text, and reading any size high contrast, light-on-dark text to be very straining. A website designed with accessibility in mind is less likely to cause legibility problems for me. I like being able to use my keyboard to navigate websites. Accessible sites are keyboard friendly since they do not force people to use a mouse.
Unobtrusive and keyboard accessible connected select boxes | 456 Berea Street - 0 views
-
Any web developer who has created a reasonably complex form is probably aware of the concept of multiple select elements that are connected – choosing something from one select box either makes a new select box appear or changes the options of one that is already visible. There are usually two problems with this approach. One is that most implementations are completely dependent on JavaScript being available. Often there either is no submit button at all, or there is a submit button but without JavaScript there is no way to access the options that appear only as a result of changing the first select box. The other problem is that in some browsers, using the cursor keys to change the selected option triggers the onchange event immediately, so you can never get past the first option unless you know how to use your keyboard to display all options. I normally work around these problems by requiring users to submit the form to get the next set of options from the server. Obviously that isn’t an ideal solution either. So what other options do we have? One option that looks promising is described by Christian Heilmann in Unobtrusive connected select boxes - yet another solution approach. It involves using optgroup elements to create a two-level select box, which is then split into two separate select boxes if JavaScript is available. Neat. The solution Chris describes solves (or at least mitigates) the keyboard access problem since it doesn’t reload the page when the onchange event is triggered. And if JavaScript is unavailable, there is a single select box with option groups. The catch is that nested optgroup elements are not allowed in current versions of HTML, so this will not work when more than two connected select boxes are needed. Nested optgroup elements are allowed in the current Web Forms 2.0 Working Draft, so I guess there is a reasonable chance of that change making it into HTML 5.
Introducing WysiHat: An eventually better open source WYSIWYG editor - (37signals) - 0 views
-
WysiHat is a WYSIWYG JavaScript framework that provides an extensible foundation to design your own rich text editor. WysiHat stays out of your way and leaves the UI design to you. Although WysiHat lets you get up and running with a few lines of code, the focus is on letting you customize it. We are giving developers early access to the project while we continue to work out the remaining issues. Note: It’s extremely early. Contributors are welcome so please check out the project on GitHub and send us your feedback.
Better Website Development: Disability Discrimination Act Dda Amp Web Accessibility - 0 views
-
There's been widespread speculation about the new legislation being introduced under the DDA (Disability Discrimination Act), which will ensure that websites are accessible to blind and disabled users. Try to find specific information about it on the Internet and chances are you'll come up empty handed.The RNIB (Royal National Institute for the Blind) and the DRC (Disability Rights Commission), two of the most renowned advocates for the DDA (Disability Discrimination Act) and accessible websites, have no specific information about the laws and what websites specifically need to do in order to meet the legal requirements.
-
2.2 (p7): "The Act makes it unlawful for a service provider to discriminate against a disabled person by refusing to provide any service which it provides to members of the public."
-
4.7 (p39): "From 1st October 1999 a service provider has to take reasonable steps to change a practice which makes it unreasonably difficult for disabled people to make use of its services."
- ...2 more annotations...
Web 2.0: Understanding Web Accessibility - 0 views
-
As stated by renowned accessibility expert Shawn Lawton Hewitt, Web Accessibility simply means that people with disabilities can use the Web. More specifically, Web Accessibility means that people with disabilities can perceive, understand, navigate and interact with the Web.
-
It is important to understand one aspect that most experts agree on – an individual web site can never be perfectly accessible to everybody. This has to do with the sheer diversity of disabilities as well as the potential overlap of multiple disabilities. But a systematic approach like implementing the WCAG guidelines can go long way in accommodating a very large number of people.
Tim Anderson's ITWriting - Tech writing blog » Adobe AIR: 10 reasons to love ... - 0 views
-
3. Easy conversion of existing Flex or HTML applications. It’s the same basic runtime. In the case of HTML, AIR apps rely on WebKit, the core component in Apple’s Safari web browser.
-
7. Rich design and multimedia. This is Flash, so ideal for highly customized UIs, animation, sound and video. Adobe is proving the point by creating a media player built with AIR. Existing Flash developers can easily use their skills to build AIR applications.
-
4. Proprietary technology. AIR applications depend on Adobe’s runtime.
- ...3 more annotations...
Readable - another way of improving readability on the Web | 456 Berea Street - 0 views
‹ Previous
21 - 40 of 49
Next ›
Showing 20▼ items per page