Skip to main content

Home/ Web Accessibility/ Group items tagged navigation

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Vernon Fowler

Responsive Design is Too Responsive? - 0 views

www.visionaustralia.org/...sive-design-is-too-responsive-

design responsive design responsive webdesign accessibility css3 media queries mediaqueries

shared by Vernon Fowler on 07 Apr 13 - No Cached
  • When you use browser zoom in Webkit browsers (Chrome and Safari), all elements on the page increase in size and start overlapping content. This is because WebKit browsers zoom to make the content bigger but the width of the browser remains unaffected, which means it doesn’t trigger responsive style sheet elements or address layout issues.
  • This is an accessibility issue as users with vision deficiencies use browser zoom to navigate websites. If they use Google Chrome they will have a lot of issues accessing content.
Vernon Fowler

Bruce Lawson's personal site  : Should you use HTML5 header and footer? - 0 views

www.brucelawson.co.uk/...ou-use-html5-header-and-footer

html5 accessibility markup semantic DIG252

shared by Vernon Fowler on 22 Jun 14 - No Cached
  • Use <header>, <footer> as often as your content requires – only the main header and footer carry implicit banner and contentinfo roles. At a minimum, use them once (assuming you have a page header and footer, that is). Always use <nav> for the primary navigation. Use <main>, but only once per page.
Sandra Earl

Web Content Accessibility and Mobile Web - 0 views

www.w3.org/mobile

accessibility mobile resources reading standards W3C

shared by Sandra Earl on 12 Oct 10 - Cached
  • 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.
Sandra Earl

Designing and Developing mobile web sites in the real world, part 2 - Opera Developer C... - 0 views

dev.opera.com/...d-developing-mobile-web-site-1

accessibility mobile opera best practices reading

shared by Sandra Earl on 12 Oct 10 - Cached
  • 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...
  • e chose not to try and replicate the entire Icelandair website, but rather to cleave from it four or five of its most crucial elements.
  • This page contains the only form on the mobile site. In general, forms should be avoided because form input via a mobile device can be a tricky endeavor. However, there are certain coding practices that can simplify form input. For example, if your form field should only accept numeric input, then you should make use of the -wap-input-format property of WAP CSS. The Apple iPhone will automatically set the input to numeric if the name of the input element is set to certain values - phone or zip for example.
  • Mobile users only need to be shown news items that have some inherent urgency.
  • Much like your desktop browser recognizes a mailto: link as an email address, mobile devices recognize tel: links and phone numbers.
  • Do not assume that just because the UA string is not in your enumerated list of “Accepted strings”, it is not possible to view the site.
  • This is where you build in progressive enhancements to the website experience.
  • WURFL is an open source list of known phones and their capabilities. This can be put into a database and when a mobile device visits the your site you can sniff the UA, look-up the capabilities of that device (including screen-dimensions, default browser, etc) and serve them the best possible experience.
  • The RDF vocabulary is a standard across many mobile devices. Vendors that use this approach allow mobile sites to keep up-to-date with any new devices, without having to keep their own database of device types.
  • ou can find more details about standards support in Opera Mini/Mobile 4 here: Designing with Opera Mini 4 in mind JavaScript support in Opera Mini 4
  • There are a few basic coding items to avoid in the mobile web space. Chief among these, at least for now (now being 10/2007), is client-side scripting.
  • While it's tempting to try and port that elegant bit of AJAX from your conventional web to your mobile web, you will only create headaches for yourself.
  • ome browsers do support various levels of JavaScript, but as a developer you should not expect it to work across all devices.
  • retty heavy processor hog, so continuous scripting can drain a battery fast
  • mobile browser support for stylesheets varies greatly.
  • keep things simple.
  • most mobile devices default to their own font sizes and families regardless of styling. Thus, when working on the Siminn project we made no attempt to influence font size or family. In cases where we wanted a larger font, we simply relied on the generic XHTML heading elements.
  • he inclusion of font-size=smaller in the body tag worked as a kind of global reset for font sizes in every device we tested. With this little bit of code we were able to sufficiently reduce the default font size and thus more faithfully reproduce the design that we had been tasked with coding.
  • XHTML-MP - the mobile web subset of XHTML - is fully supported on most modern devices.
  • You can't read 2 books and several articles about mobile web development and cover everything. Much of the effort is trial and error. When starting out, emulators are a good way to get a rough idea of how the site will work. It gives you some feel for the navigation, architecture and flow of the site, but the look and feel varies from the emulator to the real device. The best thing you can do is get a few real phones to test on. I'm sure between yourself, co-workers and a few friends, you can manage to test your site on a good cross-section of the phones out there. Finally, there is some help. The W3C mobile web initiative does have a checklist to see how well your site is doing and so does dev.mobi - if you take heed of these two lists, your site should give a quality experience to most customers.
Sandra Earl

How did you get into Web accessibility? | 456 Berea Street - 0 views

www.456bereastreet.com/...you_get_into_web_accessibility

accessibility reflection testimonial

shared by Sandra Earl on 12 Oct 10 - Cached
  • 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.
Sandra Earl

Designing for Dyslexics: Part 3 of 3 - Accessites.org - 0 views

accessites.org/...ning-for-dyslexics-part-3-of-3

accessibility cognitive learning disabilities dyslexia

shared by Sandra Earl on 12 Oct 10 - Cached
  • Shorter line lengths and narrower text columns make reading easier.
  • Consider setting a percentage width for text areas and set the margins to “0 auto” via CSS. The page side margins will then increase proportionately on wider screens.
  • Most browsers have a default line-height of around 1em. This normally results in closely packed lines of text. Increasing the line-height to around 1.3em immediately makes longer lines of text easier to read. Likewise, ensure that paragraphs are visibly separated. Don’t be afraid of white space. Use it to enhance readability.
  • ...16 more annotations...
  • percentages or ems.
  • If possible, use a sans-serif font. The decorative “hooks” on the main strokes of serif letters may create additional problems for dyslexic users.
  • If you have to use a corporate serif font, consider reducing the letter-spacing slightly so that the letters within a word lie closer together but increasing the word-spacing to create a slightly larger distance between individual words.
  • uneven word spacing disrupts that pattern recognition.
  • Unjustified text, although less attractive at first glance. is far easier to read.
  • When italic fonts are used on a web page, the individual letters can have a slightly jagged line compared to a non-italic font. This “pixelation,” coupled with their “lean to the left” makes them hard for a dyslexic person to read. The effect is compounded if the text is also small.
  • Use italics sparingly and consider bold text for important words. They’ll be far easier to read.
  • Photographs, charts and icons can convey a great deal of information regarding the topic of a page. Graphics can break the page up into smaller chunks. They can also provide visual memory aids and support comprehension for dyslexics.
  • Dyslexics often have poor organisational skills. Lists can help them by organising information into small, logical chunks.
  • Dyslexics tend to have poor information processing skills. So it is relatively easy to overload them by literally providing too much information on one page.
  • Within a page, use headings to sub-divide the page logically and visually. Adding coloured heading backgrounds or borders will act as further support.
  • Consider breaking complex pages down into two or three smaller pages.
  • Keep site navigation simple and logical. Make sure that the Home page is easily reachable from any part of the site. Try not to “hide” this important link in a logo.
  • break long sentences down into two or more shorter sentences
  • Many designers do not realise that some screen reader users can see perfectly well. It is not uncommon for dyslexics to use screen readers to support their reading. This may create problems where text has been positioned off screen.
  • If you do make use of off screen positioning, try to do so sympathetically. Consider the viewpoint of those who can both hear the screen reader and see the page. Ask yourself if you’re potentially creating confusion.
Sandra Earl

Designing for Dyslexics: Part 1 of 3 - Accessites.org - 0 views

accessites.org/...ning-for-dyslexics-part-1-of-3

accessibility cognitive learning disabilities dyslexia FUSION09

shared by Sandra Earl on 12 Oct 10 - Cached
  • The specific needs of dyslexics tend to be overshadowed by the more widely understood needs of the visually impaired. Unfortunately, design decisions that benefit the latter group tend create problems for the former. This is never more evident than in so-called “accessible” text only pages with their emphasis on high contrast and complete lack of images and colour.
  • What is Dyslexia?
  • The word “dyslexia” can be broken down into two parts: “Dys” meaning poor and “lexia” meaning language. Thus dyslexics have difficulties with words. Current theories suggest that
  • ...10 more annotations...
  • it is not a visual problem but a word decoding, or recognition deficit.
  • Our ability to recognise words is thought to be based upon two slightly different “memory skills” — phonetic memory and lexical memory. Dyslexics may have a good phonetic memory — as evidenced by their tendency to spell many words phonetically — but a very poor lexical memory.
  • No two dyslexics demonstrate their disorder in the same manner. It can affect boys and girls equally, across all socioeconomic classes worldwide.
  • “A combination of abilities and difficulties that affect the learning process in one or more of reading, spelling and writing.
  • Accompanying weaknesses may be identified in areas of speed of processing, short-term memory, sequencing and organisation, auditory and/or visual perception, spoken language and motor skills. It is particularly related to mastering and using written language, which may include alphabetic, numeric and musical notation.”
  • the more complex the written language is, the greater the likely percentage of people who will have difficulty reading it.
  • As many as 1 in 10 people in the UK are dyslexic.
  • Worldwide, it is likely that the number of dyslexics is likely to be equal to, if not significantly larger than, the number of visually impaired people.
  • poor short-term memory and organisational skills will mean that site navigation and page organisation become more important.
  • high contrast text difficult or impossible to read. The phrases I’ve heard most often are “the text keeps moving” or “the words seem to dance on the page.”
Sandra Earl

Web Axe - Practical Web Design Accessibility Tips - Podcast and Blog: Paul Boag wears r... - 0 views

webaxe.blogspot.com/...wears-reading-glasses-and.html

accessibility general elderly FUSION09

shared by Sandra Earl on 12 Oct 10 - Cached
  • In Boagworld podcast episode 130, I discovered that in order to help test web accessibility, Paul Boag wears glasses (that he doesn't need) and gloves and attempts to navigate through a site. Excellent idea!In order to better understand [the elderly's] experience I have bought a pair to ski gloves and some reading glasses (I don't need reading glasses). Every now and again, I surf the site I am designing wearing both the glasses and gloves. The glasses make the screen hard to read while the gloves hamper my use of the mouse and the keyboard. There is nothing more frustrating than trying to select something from a drop down menu wearing ski gloves!
Sandra Earl

Web 2.0: Understanding Web Accessibility - 0 views

infosysblogs.com/...standing_web_accessibilit.html

accessibility general FUSION09

shared by Sandra Earl on 12 Oct 10 - Cached
  • 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.
Vernon Fowler

Bruce Lawson's personal site  : The practical value of semantic HTML - 0 views

www.brucelawson.co.uk/...actical-value-of-semantic-html

accessibility html mobile navigation

shared by Vernon Fowler on 25 Feb 19 - No Cached
  • styles each header element differently depending on the value of its itemprop attribute. Using itemprop, we’re able to ensure that the author, publication date, title, and subheading are prominently featured.
  • If you plan to put things into microdata, please note that Apple, being Apple, go their own way, and don’t use a schema.org vocabulary here. Le sigh. See my article Content needs a publication date! for more. Or view source on this page to see how I’m using microdata on this article.
  • Apple WatchOS also optimises display of items wrapped in <figure> elements
  • ...4 more annotations...
  • First, choose the appropriate type attribute and element tag for your form controls. WebKit supports a variety of form control types including passwords, numeric and telephone fields, date, time, and select menus. Choosing the most relevant type attribute allows WebKit to present the most appropriate interface to handle user input.
  • unlike iOS and macOS, input methods on watchOS require full-screen interaction. Label your form controls or specify aria label or placeholder attributes to provide additional context in the status bar when a full-screen input view is presented.
  • By choosing the right semantics now, a machine that I don’t know about yet can understand my content and display it in the best way for its users.
  • Semantic HTML will give usability benefits to many users, help to future-proof your work, potentially boost your search engine results, and help people with disabilities use your site.
Vernon Fowler

Don't Rely on Default Browser Error Messages - Intopia - 0 views

intopia.digital/...default-browser-error-messages

accessibility forms validation HTML5

shared by Vernon Fowler on 06 Feb 19 - No Cached
  • 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...
  • Only the first error is noted with a message.
  • The rest rely on a change of border colour, which is, again, not evident to screen reader users.
  • Vernon Fowler on 06 Feb 19
     
    "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."
Vernon Fowler

Validation messages - 0 views

www.accessibility-developer-guide.com/...validation-messages

forms accessibility validation

shared by Vernon Fowler on 09 Feb 19 - No Cached
  • If there are any validation messages, the focus is set to the first invalid input: this way, a screen reader will immediately announce the associated message, so the user knows that there is at least one invalid input to be fixed.
  • For multiple radio buttons or checkboxes, the message is associated to the surrounding <fieldset>.
  • In addition to this, each invalid input is associated to its message using aria-describedby. This is important, as it makes sure that screen readers also announce the messages when navigating through the inputs using the Tab key.
  • Vernon Fowler on 09 Feb 19
     
    "Data submitted in a form is usually validated in some way. And if there is any unacceptable data, the form is traditionally re-displayed, together with validation messages. In such a case, it is important to immediately inform screen reader users, so they know that they have to look at their data and submit again. "
Vernon Fowler

WebAIM: Links and Hypertext - Link Text and Appearance - 0 views

webaim.org/...link_text

links hypertext link text accessibility usability UX webdesign

shared by Vernon Fowler on 26 Mar 14 - No Cached
  • links are more useful when they make sense out of context
  • In most cases, it is better to use human-readable text instead of the URL.
  • The alternative text should convey the content of the image and the function of the link. In most cases, the content of the image and function of the link are the same, so this text can be very succinct (e.g, alt="Products").
  • ...6 more annotations...
  • When images are used as links, the alternative text performs the function of link text.
  • on both mouse hover and keyboard focus
  • they are also accustomed to seeing tabs and main navigational features (oftentimes created as graphics rather than text) without underlining. In these cases, the linked items should be designed so it is apparent that the user can click on them to perform an action.
  • Authors should avoid non-informative link phrases such as: click here here more read more link to [some link destination] info
  • adjacent links should have adequate whitespace (such as link CSS margins) between them to minimize users inadvertently clicking the wrong link
  • an alphabetical index may use each individual letter of the alphabet as a link
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."
‹ Previous 21 - 37 of 37
Showing 20▼ items per page