Skip to main content

Home/ Web Accessibility/ Group items tagged Web

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Sandra Earl

Better Website Development: Disability Discrimination Act Dda Amp Web Accessibility - 0 views

better-website-development.blogspot.com/...iscrimination-act-dda-amp.html

accessibility laws standards

shared by Sandra Earl on 12 Oct 10 - Cached
  • 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...
  • The law about accessible websites came into force on 1st October 1999 (http://www.drc-gb.org/open4all/law/code.asp) and the Code of Practice for this section of the Act was published on 27th May 2002 (http://www.hmso.gov.uk/si/si2002/20020720.htm). This means that the majority of websites are already in breach of the law.Can you be sued?Well, probably. The RNIB claim that they've considered taking up a number of legal cases against organisations with regard to their websites. When they raised the accessibility issues of the website under the DDA, companies have typically made the necessary changes, rather than facing the prospect of legal action.The DRC has now published their findings from their formal investigation into 1000 websites. (http://www.drc-gb.org/publicationsandreports/2.pdf). If your website was included then you will have to start thinking about making it accessible to all web users in the very near future.
  • What do you need to do to comply?It's widely believed that if, or perhaps more appropriately when, a case makes it to court that the W3C accessibility guidelines will be used to assess a website's accessibility and ultimately decide the outcome of the case. The W3C is the Internet governing body and its web accessibility guidelines can be found at http://www.w3.org/TR/WAI-WEBCONTENT/full-checklist.html.
Vernon Fowler

WebAIM: Using NVDA to Evaluate Web Accessibility - 0 views

webaim.org/nvda

accessibility testing NVDA

shared by Vernon Fowler on 02 Jun 17 - No Cached
  • Vernon Fowler on 02 Jun 17
     
    "This article is designed to help users who are new to NonVisual Desktop Access (NVDA) learn the basic controls for testing web content, and to serve as a reference for the occasional NVDA user. "
Vernon Fowler

Introduction to Understanding WCAG 2.0 | Understanding WCAG 2.0 - 0 views

www.w3.org/...intro.html

WCAG accessibility web content standards

shared by Vernon Fowler on 09 Mar 16 - No Cached
  • Perceivable - Information and user interface components must be presentable to users in ways they can perceive.This means that users must be able to perceive the information being presented (it can't be invisible to all of their senses)Operable - User interface components and navigation must be operable.This means that users must be able to operate the interface (the interface cannot require interaction that a user cannot perform)
  • users must be able to understand the information as well as the operation of the user interface
  • robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies
  • Vernon Fowler on 09 Mar 16
     
    "The guidelines and Success Criteria are organized around the following four principles, which lay the foundation necessary for anyone to access and use Web content."
Vernon Fowler

Command F5 Web Accessibility Project - 0 views

commandf5.com/index.html

accessibility inclusive empathy web

shared by Vernon Fowler on 12 Jan 17 - No Cached
  • Vernon Fowler on 12 Jan 17
     
    "Encouraging Accessible & Inclusive Design and Development"
Vernon Fowler

Inclusive Design: Accessible user experiences on the web « UX Australia 2010 - 0 views

www.uxaustralia.com.au/...inclusive-design

inclusive accessibility accessible user experience webdesign WCAG Design userResearch research workshop UX web

shared by Vernon Fowler on 07 Apr 17 - No Cached
  • Understanding how to incorporate accessible design practices within a project
  • Integrating accessible, inclusive design practices throughout traditional UX research and design practices
Vernon Fowler

Free Web Accessibility Software Suite | Deque FireEyes - 0 views

www.deque.com/deque-fireeyes

web free software firefox firebug accessibility

shared by Vernon Fowler on 23 May 12 - No Cached
  • FireEyes is offered free of charge from the makers of WorldSpace Sync, the most powerful accessibility software suite available. FireEyes is for individual, non-commercial use, and provides developers and QA testers the ability to check pages for accessibility issues, and provides help and support to solve the issues.
Vernon Fowler

WordPress › WP Accessibility Plugin « Make WordPress Accessible - 0 views

make.wordpress.org/...wp-accessibility-plugin

accessibility cms webdesign plugin WordPress checklist

shared by Vernon Fowler on 07 Jan 14 - No Cached
  • These title attributes have exactly the same value as the text of the link — if the text of the link is “Joe’s Blue Widgets”, then the title attribute is also “Joe’s Blue Widgets”. In the best case scenario, where a screen reader is set up to ignore title attributes, having this set makes little difference. In the worst case scenario, where a screen reader reads all attributes, it’s awful: the screen reader reads the title attribute and the link text, meaning that every link is, effectively, read twice.
  • Skiplinks provide a means to leap from the very top of a page to an alternate section of that page — one principle use being to leap over the main navigation to the main page content.
  • It does *not* remove it from other fields, because a common technique to grant keyboard focusability to normally non-focusable elements is to define a negative tabindex: this places the element into the focus sequence but does not force it into a particular place in that sequence.
  • ...5 more annotations...
  • Removing those attributes usually makes keyboard navigation much more linear and predictable. The intention behind tabindex was to create a logical tab sequence when it would otherwise have been unnatural; but in practice, that required absolutely insane degrees of maintenance to use in a real-life web site.
  • Links opened in new windows can break web site flow (creating a change of context) and disorient users who don’t realize they’ve moved to a new window. Also, it takes away the option of opening in the same window/tab
  • Remove title attribute from inserted post images/featured images
  • for accessibility, all links should make sense without requiring context, to grant screen readers the ability to scan the page and have information. This plug-in adds the title of the post into this pattern
  • Many designs do not provide a design for the view of links or other focusable fields when a keyboard user brings focus to that element. This makes it very difficult for visual users who are keyboard dependent to keep track of where they are. A common pattern for this is to change the appearance of the element on keyboard focus; and this item adds an outline.
Vernon Fowler

Akbar - 0 views

howlowck.github.io/Akbar

bookmarklet accessibility tools

shared by Vernon Fowler on 16 Feb 14 - No Cached
  • Vernon Fowler on 16 Feb 14
     
    "A bookmarklet that simulates various types user experiences. It is an education tool that will hopefully education people about web accessibility."
Sandra Earl

Web Axe - Practical Web Design Accessibility Tips - Podcast and Blog: Fieldsets, Legend... - 0 views

webaxe.blogspot.com/...egends-and-screen-readers.html

accessibility development legends fieldsets screen reader

shared by Sandra Earl on 12 Oct 10 - Cached
  • Some tips from the article include:Fieldset and Legend tags must be used together, never independently of each other.Keep the content of the Legend tag brief (the Legend may be read when each of the controls contained in a Fieldset receive focus.)In Windows Eyes, the option to read the Legend tag is off by default.Fieldsets may be nested.
« First ‹ Previous 41 - 60 of 154 Next › Last »
Showing 20▼ items per page